A SaaS team can move employee mail to Microsoft 365 and still have password resets sending through the old provider. This email provider migration checklist separates mailbox work from application email work, so you can plan the right tests, protect sender reputation, and cut over without leaving templates or suppressions behind.
To move email between providers, first identify whether you are moving hosted mailboxes, application sending, or both. Inventory the data and integrations, confirm access and destination readiness, prepare DNS, and pilot the transfer. Cut over in stages, monitor both mail flow and application sends, and keep the old service available until the checks pass.
First, define what you’re migrating
“Email migration” can mean moving mailbox hosting or changing the infrastructure that sends an application’s messages. Mailbox hosting covers accounts and stored messages, often with calendars and contacts; sending infrastructure covers transactional email, campaigns, and automated workflows. Moving Exchange mailboxes to Microsoft 365 is not the same project as changing the provider that sends password resets.
Mark every task mailbox, sending, or both. If you are changing both, run connected but distinct workstreams: mailbox tools move mailbox data, while application teams must plan for credentials, templates, contact records, suppressions, and automations. We combine transactional email, campaigns, and automations on one API, but that sending infrastructure is not mailbox hosting software.
Before migration: inventory and plan
Build an inventory that captures both user data and application email assets. For mailbox moves, list accounts, mailbox sizes, shared mailboxes, distribution groups, and any calendars or archives in scope. For sending moves, record domains, monthly volume, integrations, templates, contact data, suppression records, event-triggered workflows, and current costs.
Name an owner for each workstream—for example, the Microsoft 365 administrator for Exchange accounts and the application engineer for credentials and templates. Set a freeze point or final synchronization plan, a cutover window, and a rollback trigger. A useful trigger is a failed password-reset flow or a missing mailbox folder; document who can restore the previous routing or credentials and how.
Include tool licensing and the destination service in the budget, but compare like with like. MigrationWiz Mailbox is $14 per user for up to 50 GB; its $3.50 add-on adds archives, OneDrive, Teams chat, and unlimited data. The User Migration Bundle is $17.50 per user and includes mailbox, archive, documents, Teams private chat, and unlimited data. For 100 users, the Mailbox license plus add-on is (14 + 3.50) × 100 = $1,750; the User Migration Bundle is 17.50 × 100 = $1,750. The matching totals do not mean the bundles cover identical workloads. BitTitan’s pricing page lists the included items and limits.
For the sending platform, compare monthly volume and domain needs as well as migration work. Volanea offers 1,000 free emails per month, Starter at $5/month for 7,500 emails, and Growth at $20/month for 50,000 emails. Plans differ by monthly volume and domain count; every feature is available on every plan. At the monthly sending limit, sending pauses rather than incurring overage billing.
Check access, compatibility, and data handling
Confirm that source credentials can read the data and destination permissions can write it. For MigrationWiz mailbox projects, BitTitan says administrative credentials are required and, in most scenarios, the administrator needs full access to source mailboxes. Its Microsoft 365 Exchange Online guidance recommends API permissions over delegated permissions. Permissions vary by source and destination, so map them to the actual pairing before the migration window.
IMAP is a possible path for compatible mailbox systems, but it moves email rather than every kind of account data. Check explicitly for calendars, contacts, tasks, rules, archives, and shared mailbox behavior. MigrationWiz lists Exchange, Microsoft 365, IMAP, and POP endpoints; it also lists Hotmail, MSN, Windows Live, and other POP systems as sources and destinations. VMware Zimbra Server 6+ is listed as source-only. Confirm that the direction and data types you need are supported, not just that a product name appears in a tool’s endpoint list.
For application email, make a separate transfer map for templates, contact fields, consent status, suppressions, and automation rules. Do not assume that a mailbox export includes these assets. Decide which records must be retained and who needs access after cutover, then test the export and import with a small sample before treating it as complete.
Prepare domains, DNS, and deliverability
Keep inbound mailbox routing distinct from outbound sender authentication. MX records route incoming mail to a mailbox provider. SPF, DKIM, and DMARC help authenticate messages sent using your domain. A Microsoft 365 mailbox move may require MX changes; an application-sending move typically requires sender-domain changes too. Changing one set does not configure the other.
Record current DNS before editing it. Add and verify the destination’s SPF authorization and DKIM records before sending production traffic. If a domain already has an SPF record, edit that record rather than publishing a second one. Keep the old provider’s records while it still sends; remove them only after its traffic has stopped. Review DMARC reports during the transition to identify legitimate senders that are failing alignment.
We require domain verification before sending to real recipients, but a Volanea sending account does not require an Amazon SES production-access request. Every email we send goes over Amazon SES, on shared infrastructure; we do not offer dedicated IPs. Verify the domain and the DNS records before switching application traffic, and account for shared sending infrastructure in your provider comparison.
Test the destination before switching
Run a pilot before moving every mailbox or changing every application credential. For mailbox hosting, compare folders and message counts for a few representative accounts, then test sending and receiving. Include a shared mailbox and a distribution group if they are in scope; one successful individual inbox does not prove those paths work.
For application email, test every integration path the code actually uses: API, SMTP, or both. Send representative transactional messages and campaigns. Check rendered content, links, event tracking, bounce handling, and whether a previously unsubscribed or bounced contact remains suppressed. Confirm that application logs identify the message and recipient well enough to investigate failures.
A practical Volanea pilot is to verify a sending domain, configure a test API key, send a test message, and review the rendered output and logs before changing production credentials. Keys beginning with sk_test_ render and log messages but never deliver them. The from field accepts either a bare address or a formatted value such as Name <address>; test the format your application uses. Our templates support test sends and version rollback, so keep the pilot focused on the templates your application will use first.
Cut over with minimal disruption
Use a staged cutover rather than switching every account or service at once. Tell mailbox users and application owners when the change begins, who is affected, and where to report problems. Choose a window that suits your actual traffic and staffing; there is no universal low-traffic hour for every SaaS product or mailbox environment.
- Capture final changes. For mailbox moves, run a final synchronization or pause account changes if practical. For sending moves, record changes to templates, contact records, suppressions, and automation rules since the pilot.
- Switch a limited scope. Move one mailbox group or one application flow first. Change mailbox routing for hosting moves; update API keys or SMTP credentials for application sends. Confirm the application is using the intended project and sender domain.
- Monitor before expanding. Check mailbox access, send and receive tests, application errors, bounces, and complaints. If a critical path fails, stop the next batch and restore the previous configuration for the affected traffic.
For example, a SaaS team moving transactional email to Volanea can verify its domain, replace the application’s old credentials with the new project credentials, send a test message, then switch one password-reset flow before changing receipts and alerts. Keep the former provider active during the transition so the team can restore its prior credentials if a production check fails.
After migration: verify, monitor, and clean up
For mailbox work, compare folder and message counts, check users can send and receive, and confirm shared mailboxes, distribution groups, and Outlook access. For application email, inspect API or SMTP errors and confirm that password resets, receipts, and other critical messages arrive as expected. Check sender authentication, bounce and complaint signals, suppression behavior, and every event-triggered workflow in scope.
Retain the source data and access until the checks pass for each migrated batch and the team has reviewed the records needed for its retention policy. There is no single retention duration that fits every organization; base it on contractual, operational, and legal requirements. Once the destination is confirmed, revoke old credentials, remove obsolete settings, and cancel the old service only when it is no longer needed for recovery or record access.
We recommend treating suppressions and credentials as production data, not incidental settings. A test that confirms a message arrives is incomplete if an opted-out contact can now receive a campaign, or if an old API key remains active in a deployed service. Our email deliverability and sending guides cover ongoing checks after the cutover.
Choose migration tools—and know when you need one
Mailbox migration tools address mailbox and collaboration data, not every application-email asset. MigrationWiz offers mailbox, bundle, and public-folder licensing; its Public Folders option costs $114 per 10GB and includes emails, calendars, contacts, and files, with shared mailbox targets supported. CloudM Migrate licenses include a 12-month migration license and support 20+ source platforms. Its environment scan helps estimate scope and identify permission issues before migration.
CloudM prices Microsoft 365 mail-only and full-user migration per user, while its Google Workspace Shared Drives and public folders are priced per 10GB and include Shared Drives, permissions, and folder structures. The CloudM pricing page does not publish exact license prices. CloudM supports hosted or self-hosted deployment and offers migration paths for mailbox and shared-workspace data; check the compatibility matrix for the exact source, destination, and entities in scope.
Use a tool when the project needs bulk mailbox transfer, repeatable synchronization, or preservation of data such as calendars and shared folders. For an Exchange to Microsoft 365 migration, compare supported endpoints, admin permissions, data coverage, license units, and recovery options. MigrationWiz and CloudM Migrate serve mailbox projects; neither replaces a plan for application credentials, sending domains, templates, contacts, or automations. For a sending move, compare the operational workload and monthly send volume alongside the email platform’s own pricing rather than adding mailbox licenses that do not apply.
FAQ
Can you change email providers and keep the same email address?
Yes, if you control the domain and create the same mailbox address at the destination. After the destination is ready, change MX routing and test inbound and outbound mail. If only your application’s sending provider changes, the address can remain the same, but the sender domain must be authenticated and the application must use the new credentials.
How do I transfer emails from one hosting provider to another?
Create destination mailboxes, confirm administrative access to the source and destination, then use a supported migration path such as IMAP or a tool like MigrationWiz. Pilot a few accounts first and compare folders and message counts. Schedule a final synchronization for messages received during the initial copy, then change routing after the destination works.
What should I do if the new provider fails during cutover?
Pause the next migration batch and identify whether the failure affects mailbox access, inbound routing, or application sends. Restore the previous routing or credentials for the affected service using the rollback plan, while preserving the destination state and logs. Resume only after the cause is understood and a repeat test passes.
How much does an email migration cost?
The total depends on the number of users, data types, and tools required, plus the destination service. A mailbox license may not cover shared folders or archives, and a mailbox tool does not move an application’s sending setup. For a sending-platform move, compare monthly sending volume and included features with migration labor and any needed data-transfer work.
For a sending-platform move, start with a pilot before committing production traffic. Start free with 1,000 emails a month.