Migrate domain email without losing history
A safe migration is a checklist, not a single button. You verify the new host, move or preserve history, then cut MX when you are ready. Unbox hosts new mail once DNS points at us; a full self-serve history import from every old provider is not a finished customer product yet.
What to decide first
- Keep the old provider readable (export or IMAP) until you confirm the new inbox.
- List every mailbox and shared address you must recreate.
- Pick a cutover window when a short delay is acceptable.
Recommended sequence
1) Create the Unbox account and add the domain. 2) Create mailboxes and shared queues to match production. 3) Publish SPF/DKIM (and related records) for Unbox while MX still points at the old host if you need a dual-preparation window. 4) Lower TTLs ahead of time. 5) Switch MX to Unbox when ready. 6) Keep the old archive available until you no longer need it.
History and Unbox today
Operator tools for IMAP import exist internally for specific migrations; they are not a polished in-app importer for every customer yet. Plan on retaining access to the previous host or an export (MBOX/PST) if you must search years of mail on day one.
Do not delay MX cutover forever “waiting for import.” New mail should land in the system you intend to operate.
After cutover
Watch the Unbox DNS checks, send a few test messages both ways, and update any devices or apps that still use the old IMAP/SMTP servers.
Common questions
- Will customers notice the migration?
- Addresses stay the same if the domain does. They may see a short delay around DNS TTL. Warn internal teammates more than external customers.
- Can I migrate only one domain of several?
- Yes. Move domains one at a time on Unbox; keep others on the old host until you are ready.
Related guides
Start the new side of the migration
Add your first domain free, recreate mailboxes, then cut MX when checks pass.
Add your first domain free