How to move business email without missing important messages
Business email hosting
The short answer
Moving business email requires two coordinated jobs: directing new messages to the new service and preserving the messages already stored. Inventory addresses, folders, storage, apps and local archives; prepare destination mailboxes; agree a supported copy or archive approach; then change routing and test both services. Keep the old service active until late arrivals and historical records have been checked, with time to resolve any exceptions before cancellation.
The same business address can often continue at a new email service. Keeping the address is only one part of the move: people also need their history, working apps and a clear place to look for new messages.
Inventory what needs to move and what needs to remain accessible
List every active mailbox and published address, including role addresses used on the website or invoices. Record routing arrangements, approximate storage, important folders and who uses each account. Identify website forms, scanners or business apps that send mail using the domain.
Also check local folders and archives on computers. Mail visible in an app may not all exist on the server. Mozilla's POP-to-IMAP guidance highlights preserving local messages and checking the new account before removing the old one. Contacts, calendars, rules and signatures need their own inventory; do not assume a message-copy method transfers every account feature.
Check destination capacity before planning a transfer
Compare each mailbox's actual use with the proposed destination. Our business email service starts at $5 per mailbox per month with 5 GB each, with webmail, compatible apps and filtering. It is optional alongside websites or other business services.
For example, an existing 7 GB mailbox does not fit unchanged into a 5 GB allowance. Decide what history must stay available and discuss a supported destination or archive arrangement before switching. Do not delete business records simply to make the numbers fit. We review existing messages, folders, storage and apps, then agree the transfer approach. Moving saved mail is separate from directing new messages.
Prepare the destination and preserve the source
Create and verify the agreed destination mailboxes before changing incoming routing. Establish authorized access through an appropriate secure process. Save the existing DNS configuration and record the current account settings. Keep a recoverable copy or export of important messages where the source service and your retention requirements allow it.
Use a supported transfer method and verify a sample before a larger copy. Prefer copying over destructive moves during preparation. Mozilla explains that IMAP synchronizes mailbox changes, including deletions. A synchronized app view is therefore not automatically an independent backup. Check complete message bodies and attachments, not just a list of subject lines.
Plan routing changes and a period of overlap
MX records direct new incoming mail. Changing them does not copy old folders. DNS answers can be cached for their time-to-live interval, described in RFC 1035's record format, so different senders may use different cached information during a change. Reducing a TTL now does not erase answers already cached under the previous value.
Agree who makes the change, who is available to test and how messages arriving at the old service will be checked. Update sending settings and authentication for the intended senders. Do not add old and new MX records as an improvised way to copy mail to both: routing preference is not a mailbox synchronization plan.
Illustrative plan for a small team changing mail services
- Prepare: A fictional team lists two mailboxes, their folders and the apps used on three devices.
- Preserve: It agrees the transfer method and checks recoverable copies of important history.
- Trial: It verifies a sample folder and attachments at the destination.
- Connect: The authorized administrator applies the agreed routing and sending settings.
- Check: The team tests each address externally and inspects both services for arrivals.
- Close out: It checks remaining history and late messages before approving retirement of the old service.
This illustrative sequence has no fixed completion time. The amount of mail, access, copy method and exceptions determine the actual schedule.
Test new delivery and old history as separate checklists
For new delivery, send from an external address to every mailbox. Reply, start a new outgoing conversation and check the visible sender. Test each agreed webmail, phone and desktop route. Verify notifications from the website and other business systems separately.
For history, compare folder coverage, date ranges and representative messages. Open attachments and check sent mail, archives and subfolders. Explain count differences such as duplicates or excluded folders rather than assuming equal totals prove a perfect transfer. Record the exceptions and who resolves them. Staff should know which account is the live working destination and where any retained archive can be found.
Retire the old service only after an agreed final check
Before cancellation, check late arrivals, remaining folders, sending tools and business recovery addresses. Confirm that removing the old subscription will not also remove DNS hosting, domain renewal or another service you still need. Keep the setup record and the agreed archive accessible to the authorized business owner.
If a test fails, pause the retirement decision and investigate the specific failure. Reverting DNS alone will not merge messages that have already arrived in two places. We can discuss the mailbox setup and transfer approach with you before changes, including what needs checking and who handles each step. The website can remain with its current host throughout an email-only project.
A few follow-up questions
Can we keep the same business email addresses?
Often yes, if you control the domain and the new service supports the required setup. Recreate the needed addresses and routing before changing delivery, and confirm any special arrangements separately.
How long should the old service stay active?
Agree that from the routing change, observed arrivals, transfer checks and subscription terms. Do not choose cancellation solely from a generic propagation estimate or one successful message.
Does business email hosting automatically include migration?
Our mailbox service and an existing-message transfer are separate parts of the discussion. We review your mail, folders, storage and apps, then agree the transfer approach and responsibilities before switching.
Sources and further reading
Plan the move before changing delivery
Tell us your domain, addresses, current mailbox sizes and apps, plus which history you need to keep. We can discuss a setup and transfer approach before switching.
Discuss an email changeover See what our business email hosting service includes