“Who’s making sure everyone can actually work the Monday after cutover?”
A Microsoft 365 migration or tenant move is a scoped project with its own specialist. The desk’s role stays deliberately bounded: getting mailboxes, files, and people ready before cutover, and steady again once the new tenant is live—named plainly instead of waved off as someone else’s problem.
Who owns what
| Piece of work | Usual owner | What the desk contributes |
|---|---|---|
| Move design and execution | Migration specialist or vendor | Context from the everyday support pattern, not the technical move itself. |
| Per-person readiness checklist | Shared: business names people and access, desk helps build the list | A practical checklist tied to the same everyday access and device support it already provides. |
| Licensing and data decisions | Business or tenant owner | Describes the current everyday impact; does not decide licensing strategy. |
| Day-one and post-migration support | M365 Desk, Essential or Plus | The familiar everyday lane, once the new tenant is the working environment. |
Common questions
No. Moving mailboxes, files, and configuration between tenants is specialist project work. The desk’s role is the readiness checklist before cutover and everyday support once the new tenant is live.
The planned cutover date, who your migration specialist or vendor is, and roughly how many people and mailboxes are involved.
Yes. A per-person access and device list is close to work the desk already does for onboarding—useful input for whoever runs the technical move.