SCCM to Intune is not a migration you do in a weekend. It's a migration you do in quarters. Ninety days is the aggressive-but-realistic window for a medium-size fleet.

The 90-day phasing

  • Days 1–14 — Intune tenant prep, co-management enabled, Autopilot pilot with 10 users.
  • Days 15–45 — Compliance workload moves to Intune. SCCM still handles apps.
  • Days 46–75 — Windows Update and resource access move. App packaging catches up.
  • Days 76–90 — Device configuration workload moves. SCCM becomes read-only for reporting.

The scripts that bridge the gap

App packaging is the slowest part. A PowerShell wrapper that takes an MSI/MSIX and spits out an .intunewin with a detection method saves me two hours per app. Use the Microsoft-Win32-Content-Prep-Tool with a config file, not the interactive mode.

Co-management knobs, in order

Move workloads one at a time. Wait a week between moves. Watch for compliance drift during each transition — a device that was compliant under SCCM might be non-compliant under Intune because the compliance definitions differ. Align the definitions before moving the workload, not after.

What "done" looks like

At day 90, SCCM is still running, but no workloads point at it. Keep it for another quarter as a reporting and forensic resource. After that, decommission. The SCCM-to-nothing transition is the one that breaks — intermediate co-management is the safe path.