Migration Center · Migration · assessment
Know what moves before anything moves
Proposed interface concept Not released. A design for discussion, drawn in HTML and CSS; not a screenshot of working software.
The Migration Center starts with a read-only assessment of the source tenant: what was found, readiness per workload, which items migrate directly, which need conversion or validation and which are not supported, the issues that block a wave, proposed waves and an estimate of the infrastructure needed. The figures shown are example data.
Proposed interface concept Not released · example data · subject to change
Read access to directory, mail, calendars, files and Teams metadata. The assessment changes nothing in the source.
| Workload | Found | Status | Complexity |
|---|---|---|---|
| MailStandard mailboxes; 2 over 50 GB go in their own batch | 412 GB | Ready | Low |
| Calendars and contactsRoom mailboxes map to bookable rooms | 48 · 6,214 | Ready | Low |
| OneDrive1,140 paths over 400 characters to shorten first | 286 GB | Ready | Medium |
| SharePoint sitesLists and custom pages become tables and wiki pages | 640 GB | Needs conversion | High |
| Teams channelsChannel history export to be verified | 41 | Needs validation | Medium |
| AutomationPower Automate flows must be rebuilt by hand | 7 flows | Not supported | High |
Complexity reflects how much needs converting, rebuilding or checking by hand. It is not a duration: timing depends on bandwidth, source throttling and the waves you choose.
- Migrates directly24Mailboxes and folders · calendars · contacts · OneDrive files (current versions) · groups
- Needs conversion6Mail flow rules (review each) · SharePoint lists to tables · distribution lists to groups
- Needs validation5Teams chat history · archive mailboxes · file version history · OneNote notebooks
- Not supported3Power Automate flows (7) · Power Apps (2) · Forms surveys
- Mail flow rule “Client confidential” uses a sensitivity labelDecide on an equivalent before Wave 2
- 7 flows send client remindersRebuild or replace before cutover
- DNS is managed by a third partyAccess needed for MX, SPF and autodiscover
- 1Pilot: IT and partners6 users · 38 GB
- 2Finance14 users · 140 GB
- 3Audit and tax28 users · 520 GB
- 4Shared mailboxes, sites, Teams5 sites · 9 teams · 640 GB
- Mail and calendar4 vCPU · 16 GB RAM · 1 TB
- Files and documents8 vCPU · 32 GB RAM · 2 TB
- Chat, meetings, identity4 vCPU · 16 GB RAM · 200 GB
Proxmox VE · discovered volume plus 30% growth. Validate before ordering hardware.
Shape this before it is built
This screen is a proposal. MSP design partners review concepts like this one against how they actually run customers, and say what is missing.