Some SCCM workloads can move to Intune today. Others need rework. The trick is knowing which ones go first, what the dependency chain looks like, and how to build rollback into every step.
Compliance policies, Windows Update rings, Microsoft 365 Apps deployment, Edge and Teams. These have direct Intune equivalents, require minimal rework, and build team confidence. Move the co-management slider for these workloads first.
Win32 application deployments, configuration profiles, PowerShell scripts, device configuration baselines. These need packaging or conversion but have well-documented Intune paths. Run parallel deployment testing before switching.
OS deployment (OSD to Autopilot), complex task sequences, custom LOB apps with dependencies, server management workloads. These require significant rework or alternative approaches. Budget extra testing time.
Once all workloads are migrated and validated, begin SCCM infrastructure decommission. Remove distribution points, site servers, and database. Retain configuration documentation for reference.
Last updated:
The right pilot group is small enough to limit blast radius but diverse enough to surface real-world issues before they affect the whole organization.
Your IT team should be the very first pilot group. They can troubleshoot issues, provide detailed feedback, and understand the context of what changed. They're also forgiving when things break.
Include laptops, desktops, VMs, and different manufacturers. What works on a Dell Latitude might fail on a Lenovo ThinkPad due to driver differences or firmware versions.
One or two users from each department ensures you catch app-specific issues. Sales uses different tools than Engineering. HR has different compliance needs than Finance.
5% pilot, then 15%, then 30%, then full rollout. Each stage validates the previous one. If problems appear at 15%, you fix them before they affect 30%. Never skip stages.
Start with workloads that have direct Intune equivalents and low risk: compliance policies, Windows Update rings, and simple app deployments (Microsoft 365 Apps, Edge, Teams). These give quick wins, build confidence, and let you validate co-management before tackling complex workloads like OSD task sequences or custom scripts.
Ideal pilot groups include IT staff (who can troubleshoot), a mix of hardware types (laptops, desktops, VMs), representatives from key business units, and users who are willing early adopters. Avoid executives for initial pilots -- they need the most stable experience. We typically recommend 5-10% of your device fleet for the first pilot wave.
Every migration batch includes a rollback plan. For co-management workloads, rolling back means switching the workload slider back to SCCM. For full migrations, we take system snapshots before changes, maintain SCCM infrastructure during transition, and have documented procedures to re-enroll devices if needed. Rollback is tested before production migration begins.
Most migrations take 3-9 months depending on environment complexity. A 500-device environment with standard applications might be 6-8 weeks. A 5,000-device environment with custom task sequences, complex app dependencies, and OSD requirements could be 6-9 months. The readiness assessment gives you an accurate timeline based on your specific environment.
Yes, this is co-management and it is the recommended approach. Co-management lets you move workloads to Intune one at a time while SCCM continues managing the rest. You can run both indefinitely, which eliminates the big-bang risk. Most organizations spend 3-6 months in co-management before fully decommissioning SCCM.
Our readiness assessment identifies what moves first, what needs rework, and what can be decommissioned. Fixed fee, read-only access, no obligation.