Provider transition / Keep work moving
Change IT providers without making employees carry the handover.
A transition is not just credential transfer. It is the controlled movement of knowledge, access, vendor relationships, and everyday support responsibility.
Lire cette page en françaisStart before notice
Inventory ownership, not secrets.
Begin with categories: who controls domains, Microsoft 365 administration, device management, backups, internet accounts, business applications, and purchasing. Record where evidence exists and who can authorize a transfer. Do not place passwords, recovery codes, or private keys in an assessment form or ordinary email.
Transition workstream
Four handovers that have to meet.
| Workstream | What to establish | Decision evidence |
|---|---|---|
| Employee support | New intake path, language, urgent-use guidance, and communications | A launch note employees can understand |
| Administrative access | Authorized owners, transfer method, recovery custody, and access review | A responsibility register without exposed credentials |
| Devices and systems | Inventory sources, management state, critical applications, and exceptions | A known/unknown list with owners |
| Vendors and renewals | Account holder, billing owner, renewal dates, escalation paths | A vendor contact and decision schedule |
Sequence
- 01
Define the transition boundary
Agree which services are changing hands, which remain with internal staff or another supplier, and who can approve access changes.
- 02
Capture knowns and unknowns
Unknown documentation is a transition fact, not something to disguise. Assign a person and next action to each material gap.
- 03
Move custody safely
Use approved secure channels and reset or reissue access where appropriate. Never use the public website for secret transfer.
- 04
Stabilize the first rhythm
Confirm employee intake, active incidents, upcoming changes, renewals, maintenance items, and leadership decisions for the first operating cycle.
Decision criteria
Ask a prospective provider to explain the handover.
- How will you distinguish missing documentation from completed transfer?
- How will employees know where to ask for help?
- How will you record shared responsibilities and third-party dependencies?
- What work is transition scope versus a separately approved project?
- What does the first recurring review actually cover?
Next step
Turn your IT context into a clear scope.
An introduction covers your team, Microsoft 365, devices, vendors, and responsibilities to transfer. You leave with the scope questions that need answers—without sharing secrets.
Prepare an introduction