Mail, files, or a tenant has to move off a host being retired, out of an acquired company, or off a server that left support.
Move mail, files, or a tenant on a scheduled cutover, with the destination reconciled against the source.
Straightforward Migration
The agreed cutover is completed, mail flow and data are validated, and exceptions are reconciled against the source.
Price
$4,000 to $18,000
Delivery window
2 to 6 weeks, fixed after scoping
An all-in band covering planning, execution, validation and handover. Your figure is fixed inside it after scoping.
No tenant access, credentials, or sensitive files are requested through this website.
What happened
Something has to move: off a host that is being retired, out of a company that was acquired, or off a server that left support. The destination is known and the shape of the move is understood. What is not settled is who owns each part of it — the data, the permissions, the identities, the DNS, and the decision to stop and roll back if the cutover goes wrong at two in the morning.
The source, the destination and the volume are known, but no item-by-item count exists yet: how many mailboxes, sites and Teams are actually in scope, where each one lands on the destination, and which of them carry permissions or sharing that has to arrive with them. The DNS records and mail-flow paths still pointing at the source have not been listed with their current TTLs, and the conditions that would stop a wave, along with the person who calls it, have not been agreed in writing.
What happens if it is left as it is
- An item that was not counted before the source is switched off can be retrieved only by keeping the source running, and paid for, past the date it was meant to be gone.
- Without written criteria naming what stops a cutover, the decision to continue or go back is made in the moment by whoever is on the call, and the business learns afterwards what was decided on its behalf.
- Mail that keeps arriving at the old host after the DNS change lands where nobody is watching, and the gap gets found by a customer who did not get a reply.
- Where source and destination go unreconciled item by item, a missing mailbox or a dropped compliance hold appears weeks later, once the source has been released and the exception has no owner left to chase.
What changes in production
Not findings. These are the things that are different afterwards.
- 1Everything in scope is counted before anything moves, and each item gets a named destination.
- 2The dependency map is built, including the DNS records and mail-flow paths the old system quietly owns.
- 3Rollback criteria are agreed in writing, naming the conditions that stop the cutover rather than describing an intention to be careful.
- 4The move runs on a dated schedule, in waves, with each wave reconciled before the next one starts.
- 5The destination is reconciled item by item against the source, and every exception is closed or given an owner.
Definition of done
The engagement ends when all of these are true and demonstrable.
- Every mailbox, site and Team in the inventory has arrived at its destination
- Mail flow is validated on the new path
- The reconciliation sheet shows source and destination match, with every exception closed or owned
What you provide
Named up front, because these are the things that stall an engagement when nobody owns them.
- Approve the cutover window
- Own end-user communications and support during the move
- Provide administrative access to source and destination
What moves the price
The figure comes from what is actually in the environment. Headcount is one input among several, and rarely the one that matters most.
- Seats and total data volume
- Source platform and whether coexistence is required
- Public folders, compliance holds, journaling or a third-party archive
- Whether the cutover has to run outside business hours
Standard scope
Meet all of these and the move is priced directly from a scoping call. Miss one and the environment is complex, which means a fixed implementation price would be guesswork — those start with a separate planning engagement, billed separately and not credited against the move.
- The source, destination, volume, dependencies and risks can be confirmed on a short scoping call
- No full technical review required before a fixed price can be given
- A move meeting all of the above is standard scope, which is what allows the price to be set from a conversation rather than from a paid review
Not included
Stated so the scope means the same thing to both parties on the last day as it did on the first.
- Migration licensing
- Source-system remediation
- Data cleanup before the move
- Help desk and end-user support
How change is staged and reversed
Production work carries risk. This is the method, not a reassurance.
- Waves are dated and sequential: a wave is not started until the previous one reconciles.
- Rollback criteria are agreed before the first item moves, and they name conditions rather than intentions.
- DNS changes are staged with reduced TTLs set in advance, so a reversal takes minutes rather than a propagation cycle.
Evidence and handover
Yours to keep whatever happens next, including handing it to your own team or another provider. The documents are what prove the work happened; they are not the thing being bought.
- The counted inventory of everything that moved
- The dated wave and cutover schedule, as run
- The dependency map, including what the old system quietly owned
- The agreed rollback criteria
- The reconciliation sheet proving source and destination match
Is this another report, with the real work quoted afterwards?
It may sound like a consultant will inspect the environment, hand over a document, and then quote a second project. That is not the default here. Where the outcome can be scoped safely from a short working call, the implementation is sold directly, as this page does. Separate paid planning is used only where genuine complexity prevents a responsible fixed price, and where it is used the page says so plainly.
Talk Through the Move
Describe what is happening, what has to be working differently, and any deadline behind it. 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 Move →