Business email migration: prepare your team before changing providers

Inventory more than email addresses

Start with the actual users and company addresses. Separate independent mailboxes from aliases, forwarding rules, shared addresses and distribution lists. Record used storage and identify who needs access to each mailbox.

Include applications that send email for the business: website forms, business software, scanners and booking systems. They may need different settings from an employee's desktop or phone. Updating only personal devices leaves these other sending paths unverified.

Agree which data will move

IMAP synchronisation mainly concerns email messages and mailbox folders. Contacts, calendars, server-side rules and local email archives may need separate migration steps. Check whether important messages exist only on a particular workstation rather than on the current server.

Choose a representative mailbox for an initial trial and record what should appear at the destination. Message totals are useful, but also sample folders, attachments and dates. Different systems may present special folders differently, so document any mapping before running the full migration.

Prepare the change window

Create destination accounts and verify access before changing mail routing. Where supported, an initial copy reduces the amount of data remaining for the final phase. Agree when DNS will change and when the last synchronisation will run.

Schedule any TTL reduction early enough for already cached records to expire. DNS caches are not refreshed simultaneously everywhere. Monitor both sides during the transition and explicitly agree which destination is authoritative after cutover. Keep the people responsible for DNS, the source service and the new service available during the agreed window.

Test incoming and outgoing paths separately

After migration, test a real incoming and outgoing path using controlled mailboxes. Check that the message appears at the destination and inspect its authentication results. Acceptance by an SMTP server alone does not establish that a message appeared in the recipient's inbox.

• Do users, aliases and shared addresses work?
• Do SPF, DKIM and DMARC match the actual sending systems?
• Can website forms and company applications still send?
• Have the desktops and phones used by your team been checked?

Keep a defined recovery window

Retain the old service for the agreed verification period. Immediate deletion can remove a useful comparison or recovery source. Record the final synchronisation time and who accepted the outcome for the business. Make sure users know where to report missing folders or device problems during this period.

For an initial FastVPS migration proposal, provide the domain, mailbox count, approximate total storage and current provider. Mention calendars and shared data as well. The final procedure and migration scope are confirmed before execution. Our existing technical migration checklist provides additional implementation details for the administrator coordinating the change.