SCCM to Intune migrations are notoriously messy. That’s not great news if you are planning a migration project or in the middle of one. But messy they are.

And the bigger your IT and app estate, the messier they become. Sprawling spreadsheets with fragmented data are usually all that is available for controlling the project. For IT teams managing SCCM to Intune migrations, that means lots of guesswork, stalled progress, and a lack of visibility.

There is a better way. It’s time to Shift.

The Spreadsheet Purgatory of SCCM to Intune Migrations

One of the most common causes of SCCM to Intune migration headaches is a lack of clarity. Clarity of apps in the estate. Clarity on dependencies. Clarity on the migration progress. Clarity on challenges. Clarity on next steps.

Spreadsheets are often spun up to help support the migration, and they do work, but only up to a point. The problem is they are instantly out-of-date, quickly become difficult to manage, and contain data that is best described as fragmented.

This puts IT teams in a state of spreadsheet purgatory.

This lack of clarity isn’t just an inconvenience, either, as not knowing and understanding your IT estate creates real business risk in SCCM to Intune projects:

  • Missed or unknown dependencies
  • Stalled progress and missed deadlines
  • Scope creep
  • The evolution of a “shadow IT” in your estate comprising apps that are missed in the migration
  • Wasted resource time

The positive is that it is spreadsheet purgatory, not eternal damnation, i.e., there is a way out.

For your SCCM to Intune migration, it is time to shift to Shift.

What SCCM to Intune Migration Clarity Looks Like

When we say Shift, we mean Capture Shift, our new automation product built specifically for SCCM to Intune migrations. Clarity is one of the key principles of Shift.

For a start, Capture Shift connects to your IT infrastructure via a proven API. This connection enables Shift to pull your entire application estate from SCCM.

No exports, no imports, and no guessing. Just your entire application estate pulled in one go.

And the data gets pulled into one place, one pane of glass for managing the migration. That dashboard gives you complete visibility of app-by-app migration readiness. As for dependencies, they are all there, surfaced automatically.

When we say clarity, we mean clarity in the fullest sense of the word.

Capture Shift — Before & After
Before — Spreadsheet chaos After — Capture Shift clarity
Capture Shift Applications view
SCCM_Migration_Tracker_v23_FINAL_v2_USE_THIS_ONE.xlsx — Excel
Home
Insert
Page Layout
Formulas
Data
Review
F7
fx
=IF(E7="???","UNKNOWN",IF(D7="Unknown","CHECK OWNER","OK"))
⚠ Last saved 94 days ago by D.Brown — some data may be out of date
 
A — Application Name
B — Owner
C — Version
D — Dependencies
E — Status
F — Notes
1
Application Name
Owner
Version
Dependencies
Status
Notes
2
Adobe Acrobat DC
J.Smith
21.0
VC++ 2019
Ready
See Wave 2 tab?
3
AutoCAD 2022
Unknown
2022.1
???
Unconfirmed
4
SAP GUI 7.7
L.Patel
7.70
SAP Router, MDMP
BLOCKED
5
Chrome Enterprise
IT Dept
118.0
None
Done ✓
See Wave 2 tab?
6
Visio Pro 2019
M.Jones
16.0
Office 365
Check deps
7
SQL Server Mgmt
D.Brown
18.0
SQL 2012 (?)
DO NOT MOVE
Check with team
8
Slack Desktop
IT Dept
4.35
None
Ready
See Wave 2 tab?
9
Legacy ERP v3
R.Singh
3.1.4
Unknown — see note
BLOCKED
10
Zoom Client
IT Dept
5.16
None
Done ✓
11
FileZilla Pro
Unknown
???
???
No owner!
See Wave 2 tab?
12
MS Project 2019
C.White
16.0
Office 365
Pending
Check with team
13
Citrix Workspace
N.Khan
23.9
Citrix VDA
Complex
14
Power BI Desktop
Analytics
2.122
.NET 4.8
Test first
See Wave 2 tab?
15
Oracle Forms 12c
Finance
12.2
Java 8, DB client
BLOCKED
16
Teams (Classic)
IT Dept
OLD
???
End of life!!
17
Bluebeam Revu
Eng Team
21.0
VC++ 2015-2019
Verify
See Wave 2 tab?
❓ Ask Dave which version is correct — he's on holiday until the 3rd
⚠️ Finance apps have deps on SQL 2012 — DO NOT migrate yet!!
⚠ STALE DATA — VERIFY BEFORE USE
‹›

Drag the handle to compare

The Power of Clarity in SCCM to Intune Migrations

It’s such a simple word, but in SCCM to Intune migrations, clarity is the key enabler of project success. With clarity, your team will have the full picture of what needs to be done, how to do it, and the migration progress you have made.

They will be able to plan migration jobs based on accurate data, confidently answer stakeholder questions, and ensure mid-project surprises are kept to a minimum.

The result is accelerated progress without the usual delays, missteps, and mistakes.

From Guesswork to Data-Driven Decision-Making and Control

In SCCM to Intune migration projects, clarity isn’t just a nice-to-have feature. If you want your migration project to be finished on time, efficiently, and completely (without missed or unaccounted for applications), clarity is a foundational element.

SCCM to Intune migration clarity is what you get with Capture Shift. Register now for early access.