Hundreds of packages, task sequences, collections, and distribution points -- and nobody has a complete picture of what's active versus legacy cruft. Before you migrate to Intune, you need to know exactly what you're dealing with.
SCCM environments grow over years -- sometimes decades. Every admin adds their own packages, collections, and task sequences. Nobody removes anything. The result is an environment where the true scope of migration is hidden under layers of legacy objects.
Ask five people on your team how many applications SCCM manages and you'll get five different answers. That's because SCCM's console shows everything that was ever created, not what's actively in use. A "500 application" environment might have 150 that actually deploy to devices and 350 that are orphaned, superseded, or broken.
This matters because every object you count inflates your migration estimate. If you quote a migration based on 500 apps, you're paying for 350 that don't need to migrate at all. The first step in any SCCM-to-Intune migration is figuring out what's real.
Last updated:
Total device count, OS versions, compliance state, last check-in date, Intune co-management status, and hardware readiness. Stale devices (no check-in in 90+ days) identified separately.
Win32 apps, MSI packages, script-based deployments, task sequence application steps. Each classified as active, orphaned, superseded, or broken. Deployment type and detection method cataloged.
OSD sequences, post-deployment sequences, custom automation. Step-by-step dependency mapping, referenced packages, scripts, and drivers identified. Complexity scored per sequence.
Device collections, user collections, membership rules (query-based vs direct). Overlapping collections identified, empty collections flagged, deployment targets mapped.
Configuration items, compliance baselines, remediation scripts. Each baseline assessed for Intune equivalent availability. Custom CI scripts cataloged for conversion effort estimation.
Distribution points, boundary groups, site servers, management points. Network topology dependencies that affect migration sequencing and post-migration content delivery.
If you estimate migration based on raw SCCM object counts, you'll overpay by 30-50%. Half those objects are dead weight. Accurate inventory right-sizes your budget and timeline.
That "simple" app package might depend on a task sequence step, a custom script, and a specific distribution point. Miss one dependency and the migration stalls or fails silently.
Teams sometimes refuse to migrate because "we have 400 applications." After proper inventory, it's 120 active apps. Suddenly the migration goes from impossible to manageable.
Leadership wants a scope, a timeline, and a budget. "We don't know" isn't an answer. An accurate inventory gives you the data to build a credible business case.
SCCM environments accumulate years of legacy objects. Packages created by admins who left years ago, collections that overlap, task sequences nobody understands, and distribution points that may or may not still be in use. The console shows you what exists, but not what's actually active or necessary. Most organizations find that 30-50% of their SCCM objects are orphaned or redundant.
We typically see environments ranging from 500 to 50,000 devices. But device count alone doesn't determine complexity. A 500-device environment with 200 custom applications and complex task sequences can be harder to migrate than a 5,000-device environment with standard software. That's why inventory quality matters more than raw numbers.
A complete inventory covers: devices and their compliance state, applications and packages (Win32, MSI, Script-based), task sequences and their dependencies, device collections and membership rules, compliance baselines and configuration items, distribution points and boundary groups, client settings and custom policies, software update groups, and any custom scripts or extensions.
SCCM's built-in reports are helpful but insufficient for migration planning. They tell you what's deployed but not what's actually working, what's redundant, or what has an Intune equivalent. Our assessment goes beyond reporting to classify each object's migration readiness, identify dependencies, and flag blockers that standard reports miss entirely.
On average, 60-70% of SCCM workloads have direct Intune equivalents or close alternatives. Another 15-20% need rework (repackaging apps, converting scripts, rebuilding policies). The remaining 10-15% either have no Intune equivalent and need a workaround, or can be eliminated because they're legacy configurations no longer needed.
Our readiness assessment catalogs every active SCCM object, scores migration complexity, and gives you real numbers for your business case. Fixed fee, read-only access.