Documentation
SCCM Migration
Migrate existing SCCM application portfolios into IntuneGet in four phases: import, matching, preview, and execution.
Workflow
- Export SCCM apps using
/scripts/Export-SCCMApps.ps1. - Create a migration and import CSV/JSON from
/dashboard/sccm/new. - Run automatic matching in
/dashboard/sccm/[migrationId]. - Review unmatched apps and apply manual mapping/exclusions.
- Open migration preview and execute from
/dashboard/sccm/[migrationId]/migrate.
API Endpoints
| Method | Path | Purpose |
|---|---|---|
POST | /api/sccm/import | Import SCCM app data |
GET | /api/sccm/migrations | List migrations, single migration, or stats |
POST/PATCH/DELETE | /api/sccm/migrations | Create/update/delete migrations |
GET/POST/PATCH | /api/sccm/match | Read, run, and adjust matching state |
POST/PATCH | /api/sccm/migrate | Preview/execute migration and update per-app settings |
Status Model
- Migration statuses include
importing,matching,migrating, andready. - Match statuses include
pending,matched,partial,unmatched, andexcluded. - Migration result statuses include
queuedandfailedfor app-level outcomes.
Execution Prerequisites
Preview/execution depends on curated app and installer metadata. Missing package metadata can block migration.