Provider migration operations
How to switch email provider and keep the same address
Move mailboxes, DNS and devices without changing the address customers know.
An email address belongs to the domain, not to the company currently hosting its mailbox. If you control the domain and its DNS, you can keep sales@example.com while moving storage and delivery. The hard part is sequencing account creation, data copy, DNS cutover and device changes so no message disappears between systems.
Preflight inventory
- Every mailbox and its current storage use
- Aliases, groups, shared addresses and catch-all rules
- Forwarders, automatic replies and blocked senders
- Desktop and mobile clients using IMAP, POP or Exchange
- Website forms, scanners and apps that send as the domain
- Contacts and calendars, which IMAP does not carry
Migration sequence
- 1
Create destinations
Provision every required address at the new provider. Set recovery access and test login before changing mail flow.
- 2
Run the first copy
Copy folders over IMAP or a supported migration API while the old system remains live. Record message counts and exceptions.
- 3
Prepare authentication
Add the new sender's DKIM and update SPF carefully. Keep old authorization until old-system sending has stopped.
- 4
Cutover MX
Change the domain's MX records during a staffed window. New deliveries will progressively move as cached DNS answers expire.
- 5
Run a delta copy
Copy messages that arrived at the old host during DNS propagation, then test from multiple outside providers.
| Phase | Evidence to capture | Stop condition |
|---|---|---|
| Preflight | Account list, DNS snapshot, message counts | Unknown addresses or no admin access |
| Copy | Folder totals and error log | Repeated authentication or quota failures |
| DNS cutover | Old and new MX values with timestamps | Destination cannot receive and reply |
| Post-cutover | Header authentication and external probes | Unexpected rejections or missing mail |
Rollback is a planned route, not a panic button
Keep the old service active and do not delete mailboxes immediately. If the new receiver fails, restore the saved MX records, confirm the old host accepts delivery, fix the destination, and schedule another cutover. A rollback changes where new mail lands; it does not undo already copied or delivered messages, so retain both logs.
Post-cutover verification
- Inbound mail works from at least two unrelated providers
- Replies show the intended From address
- SPF, DKIM and DMARC align
- Aliases and shared addresses reach the right people
- Phones and desktop clients use new settings
- A final delta copy completed
- Users know the support and password-reset path
Ready for the next practical step?
Use Venmail when its mailbox, migration and administration model fits—and keep your domain under your control.
Start a secure email migrationRelated practical guides
Cloudflare Email Routing vs email hosting: what businesses actually need
Choose forwarding or a real mailbox without confusing DNS management with email hosting.
Read the guideMove cPanel email to a new host without losing mail
Inventory web-host mailboxes, copy by IMAP and cut over with a tested rollback.
Read the guideSources and review method
Venmail publishes this guide and may be one of the products discussed. We compare providers on consistent dimensions, link to primary documentation and state non-fit cases. Product limits and pricing should be rechecked before purchase.
- Cloudflare: Set up email records (accessed 2026-08-15)
- Google: Migrate email with the data migration service (accessed 2026-08-15)
- Microsoft: Ways to migrate multiple email accounts to Microsoft 365 (accessed 2026-08-15)