Migrations & legacy exits
Plan the migration date, protect access and check what arrived.
Moving from Google Workspace, GoDaddy or an on-premises Exchange server? Plan the mail, sign-in and application changes together. Agree the cutover window, recovery steps and checks before the move.
What the evidence looks like
Illustrative sample · constructed example
A mailbox can move while its mail flow is still unresolved.
Pilot wave · accounts mailbox
Selected check
Can the accounts application send through the agreed replacement route?
Mailbox comparison recorded. This does not test the accounts application.
No recorded application send test on the replacement route.
Wave held: the application still needs its own send test.
| Dependency | What has to be established | Sample review |
|---|---|---|
| Mailbox contents | Compare agreed mail, calendar and delegated access. | Comparison recorded |
| Application relay | Send an application message through the replacement route. | Send test missing |
| Exceptions | Resolve or explicitly accept differences for the affected mailboxes. | Review still required |
| Wave approval | Keep the change owner, stop conditions and fallback in the plan. | Await remaining checks |
A mailbox move and an application mail-flow test answer different questions.
- Evidence
- Mailbox comparison complete; application send test missing.
- Decision
- Hold this wave
- Next action
- Application owner supplies the sending configuration and a test window.
Illustrative sample. Each agreed mailbox is checked; unresolved differences stay in the acceptance record.
The relevant scope
Start with a defined piece of work
The scope, the price, and how you will know it is finished are agreed in writing before anyone is given access. Review the engagement below for its deliverables, responsibilities and acceptance criteria.
The engagement
Email Migration
The move itself: everything counted first, the switch run in a scheduled window with written rules for stopping, mail tested on the new path, and a check sheet showing old and new match before the old system is released. Files and whole-tenant moves are their own pages.
Often paired with
Complex Migration and Cutover Plan
For moves with too many dependencies to price from a call. The route decision, the dependency map, a sequenced wave plan with rollback criteria, and a fixed quote for the implementation; no mailbox or file moves during the plan, and the move runs as its own project against it.
Not sure this is the one?
Describe what happened, in a paragraph. We’ll review your request and follow up about scope and next steps.
Discuss the scope and quoteWhat happens next
- 1Describe what happenedA few short fields: company size, environment, and what is going wrong.
- 2We’ll review your request and follow up about scope and next steps.The most direct next step, or a clear answer that AZ Innovations is not the right fit.
- 3A fixed-fee proposalNamed scope, price, and how you will know it is finished. No obligation.