What has to move, what can break, and who owns the cutover?
Complete migrations, platform exits, and consolidations without losing control.
Migrations & Exits
Something has to move: mail off a server that left support, a tenant out of a reseller’s control, files off a dying platform, or two companies onto one system. The move itself is understood. What is not is what quietly depends on the old system, and what happens on Monday if a mailbox or a permission does not arrive.
What gets delivered
The move is planned against a counted inventory, executed on an agreed schedule with written rollback rules, and reconciled afterwards against the source so nothing is assumed to have arrived.
What made you look today?
Common reasons this becomes urgent
Exchange Server 2016 or 2019 is still running mail after end of support
Mail is moved to Exchange Online or the approved Subscription Edition state, validated, and the old server is decommissioned in the right order.
Microsoft 365 was bought through GoDaddy and control or licensing is blocked
The tenant is defederated, direct billing is established, sign-in and mail are validated, and every mailbox and domain is reconciled.
A merger, acquisition, or divestiture changes who owns the tenant
Identity and the selected workloads are moved between tenants with dependencies handled, and the reconciliation sheet closes with every exception resolved or owned.
How the work runs
Everything that has to move is counted, the dependencies and mail flow are mapped, and the route, waves, rollback rules and reconciliation method are agreed. Then: The move runs on the agreed schedule, the rollback rules are held, and the destination is reconciled against the source with exceptions closed or owned.
Where this is priced
Each engagement below carries its own fixed scope. The price is agreed before any work begins, and the fixed proposal contains the delivery calendar and the completion date.
Implementation engagements
Bounded production work with a completion test.
Exchange Server Exit & Cutover
Mailboxes are moved to Exchange Online, or the supported Subscription Edition route is completed, with mail flow, DNS, coexistence and rollback handled and the destination reconciled against the source.
GoDaddy Microsoft 365 Exit
The tenant is defederated from GoDaddy, direct Microsoft billing is established, mail flow is validated, and exceptions are reconciled.
Straightforward Migration
The agreed cutover is completed, mail flow and data are validated, and exceptions are reconciled against the source.
Decision work
The paid outcome is a decision. No production settings are changed.
Also delivered in this area, as custom projects
Work in this list is deliberately not packaged: the scope varies too much for one honest price. The route, the risks, the completion test and the fixed price are agreed before anything begins.
- Hosted Email to Microsoft 365 Migration
- Google Workspace to Microsoft 365 Migration
- Microsoft 365 Tenant-to-Tenant Migration
- Files to SharePoint & OneDrive Migration
- Slack to Microsoft Teams Migration
- Migration Rescue & Reconciliation
- Exchange Public Folder Migration
Delivered in this area
A stalled file-server migration, rescued and reconciled
Root causes diagnosed, the missing files surfaced by a reconciliation script, the move completed, and a runbook handed to the team to run the rest themselves.
See the delivered record →The finished state
What is true when it is done
In-scope users sign in on Monday to the new system with mail, files and permissions reconciled, the old platform is retired or handed back, and the reconciliation sheet shows source and destination match with every exception closed or owned.
What you keep
Everything below is yours to keep whatever happens next, including handing it to your own team or another vendor.
- The counted inventory of everything that moved
- The dated wave and cutover schedule as run
- The dependency map, including the DNS records the old system quietly owned
- The rollback rules, agreed before the move started
- The reconciliation sheet, with every exception closed or owned
For the full commercial shape of work in this area — scope, price treatment, definition of done — see a representative engagement: GoDaddy Microsoft 365 Exit.
What moves the price
The fee is set by what is actually in the environment; headcount is only one of the inputs.
- Seats and total data volume
- Source platform and whether coexistence is required
- Public folders, compliance holds, journaling or a third-party archive
- Number of tenants and domains involved
- Whether the cutover has to run outside business hours
Describe what happened
A reply comes within one business day with the most direct next step, or a clear answer that AZ Innovations is not the right fit.
Talk Through the Problem →