Migrations rarely fail for technical reasons. They fail because the steps happened in the wrong order. Here is the order — and the rollback that makes it safe.
Almost never because the new system is bad. Nearly always because of one of these five, and every one of them is preventable with a checklist.
Mail is redirected to the new server while the historical mailbox is still copying. Now there are two live mailboxes and no single complete one.
A 24-hour TTL means some senders keep using the old MX record for a full day after the switch. Mail lands somewhere nobody is watching.
The new server sends, the old SPF record does not list it, and every outbound message is suddenly unauthenticated. This is the "why is our mail in spam" call, three days late.
Mailboxes copy cleanly. Distribution lists, shared calendars, room bookings and catch-all aliases are the ones that get discovered by their absence.
Phones keep polling the old server and appear to work, so nobody reports a problem until the old account is shut off.
If the plan has no defined way back, then a problem at 4pm on a weekday becomes an outage instead of an inconvenience.
Nine steps, in this order. The order is the method — most of the failures above are step-ordering mistakes, not technical ones.
| Service | Scope | Price (CAD) |
|---|---|---|
| Domain & DNS setup | Domain, MX, SPF, DKIM, DMARC configured and verified | $150 |
| Standard migration | Up to 10 mailboxes, full sequence above | $450 |
| Extended migration | 11–50 mailboxes | $1,200 |
| Team onboarding session | 90 minutes, device setup and orientation | $250 |
Prices are approximate, quoted in Canadian dollars and exclusive of applicable GST/HST, which is calculated at checkout from your billing address. Migration is included with the Complete plan. Above 50 mailboxes the work is quoted individually rather than priced from a table.
For a team of ten, typically one week end to end: two days of inventory and preparation, an overnight seed copy, a cutover that takes under an hour, and then several days of monitoring. The visible disruption to your team is measured in minutes, not days.
No, if the sequence is followed. Mail keeps arriving at the old server right up to the cutover, and the old mailbox stays reachable read-only for 30 days afterwards. The risk is not lost mail — it is mail arriving somewhere nobody is watching, which is what step 2 prevents.
Yes, and it is often the right call for a team that lives in email. What we avoid is a Friday-afternoon cutover with nobody available until Monday, which is the worst of both.
Yes. Historical mail, folder structure, contacts and calendars are copied across. Message counts are compared per mailbox afterwards so the copy is verified rather than assumed.
No. We give you the exact records to publish, or work alongside you in the registrar's dashboard on a call. We do not ask for and do not want standing credentials to your domain.
Before the MX cutover there is nothing to undo — the old system is still authoritative. After it, reverting the MX record restores the previous state within the DNS TTL we lowered in advance. That rollback is written down before the migration starts, not improvised during it.
Tell us how many mailboxes you have and what you are on today, and we will tell you honestly how long it will take — including when the answer is that you should stay where you are.