Email Migration: Move Mailboxes Without Losing Mail

Your email holds years of business history. Quotes, contracts, client threads, and the one attachment you will need again next month all sit inside it.

So the idea of moving it all to a new system is enough to make any owner nervous. What if messages vanish halfway through? What if the team cannot send mail on Monday morning?

This guide explains how a planned move takes everything across intact, why the cutover is the part that trips businesses up, and how to switch systems without losing a single message. It is written for owners and managers weighing up the move, not for the technical team running it.

The good news is that thousands of businesses make this move every year without drama. The ones that hit trouble almost always skipped the planning, not the technology. Get the sequence right and the switch is quiet enough that most staff never notice it happened.

What Is Email Migration?

Email migration is moving mailboxes from an old email platform to a new one while keeping all the mail, contacts, and calendars intact. It also covers the switch itself, so staff can keep sending and receiving throughout.

Most businesses do this when they move to Microsoft 365 from an older hosted service, an on-site Exchange server, or a basic mailbox included with a web-hosting plan. The trigger is usually a wider platform decision rather than email on its own.

It often runs alongside a broader move of servers and files into the cloud, but it is a distinct project with its own risks. Moving files or servers is not the same as moving live mailboxes that people rely on every hour of the working day.

What Actually Moves During a Migration?

A proper migration moves far more than the messages in the inbox. It carries across the full contents of each account so nothing is lost in the switch.

That includes emails and the folder structure staff have built up over years, contacts and address books, calendars and recurring meetings, shared and group mailboxes, and the mail rules and signatures people rely on. Skip any of these and staff notice the gap within days.

Shared mailboxes are a frequent blind spot. An accounts@ or info@ address that several people monitor is easy to overlook in planning, yet losing it can mean missed invoices or customer enquiries. The same goes for mailboxes belonging to staff who have left but whose accounts still catch the occasional important message.

How Is It Different From Cloud Migration?

A wider cloud migration moves servers, files, and applications into a cloud platform. An email move is narrower and, in some ways, more delicate, because mailboxes are live and in constant use.

You cannot pause email the way you might pause a file server over a weekend. People send and receive throughout the working day, and a customer expects a reply whether or not your systems are mid-move. That is why a mailbox migration has to be planned around the live mail flow, not just the data sitting in storage.

Why Do Businesses Migrate Their Email?

Most businesses migrate email when the current system starts costing them: an outage that halts a day’s trade, a licence bill that keeps climbing, or a setup too old to secure. The move usually pays for itself in reliability and features alone.

Ageing or Unsupported Systems

Old on-site mail servers reach a point where they cost more to maintain than they return. Hardware fails, updates stop, and a single outage can knock out mail for a whole day. When mail goes down, so does a good part of the business: quotes stall, customers cannot reach you, and staff sit idle waiting for it to come back.

Moving to a hosted platform hands that reliability problem to a provider with far deeper resources than any single business could build in-house. Uptime, patching, and capacity all become someone else’s responsibility, backed by infrastructure no small business could justify on its own.

Better Collaboration and Value

Many businesses move specifically to unlock a wider toolset. Once mail sits in Microsoft 365, it connects to shared calendars, Teams, file storage, and mobile access from the same login.

That platform can also replace separate systems entirely. A business already on it can, for example, run Microsoft Teams Phone for calling, folding another line item into a subscription it already pays for.

Security and Compliance

Older mailboxes often lack modern protections. A move to a current platform brings multi-factor authentication, threat filtering, and audit logging that a basic hosted account simply does not offer.

For businesses handling client or personal information, that matters. Stronger controls on where mail lives and who can reach it make it far easier to meet privacy obligations and satisfy the growing expectations of cyber insurers.

Consolidation and Cost Control

Some businesses end up with mail scattered across leftover hosting plans, a mix of personal-style accounts, and an old server nobody wants to touch. Consolidating everything onto one platform cuts duplicate costs and gives a single place to manage users, licences, and security.

It also simplifies the day a staff member joins or leaves. One console, one process, rather than chasing logins across several disconnected services.

How Does an Email Migration Work?

An email migration works in four stages: plan and audit, set up the new mailboxes, copy the data across, then switch the mail flow over. Each stage has a clear finish line before the next begins.

Rushing straight to the copy step is the most common mistake. The audit and preparation stages keep the final switch safe, so the mail flow moves cleanly on the day.

Stage One: Plan and Audit

First, list every mailbox, its size, and who owns it. This surfaces the shared accounts, the ex-staff mailboxes still receiving mail, and the giant archives that will take longest to copy.

The audit also records the current DNS and mail settings, the amount of data to move, and any quirks such as forwarding rules or distribution lists. These are the details that cause surprises later if nobody has written them down.

This is also when you set the switch date and tell staff what to expect. A short heads-up about the change, and a note on who to contact if something looks wrong afterwards, prevents a flood of confused messages on go-live day. Most migrations that lose mail lost it because this stage was skipped.

Stage Two: Set Up the New Mailboxes

Next, the new platform is configured and each account is created before any data moves. Licences are assigned, security settings applied, and shared mailboxes recreated to match the old setup.

Signatures, distribution lists, and mail rules are prepared here too, so users land in a familiar environment rather than a blank one. Doing this ahead of time means the copy stage has somewhere ready to land, rather than being built under time pressure on the day.

Stage Three: Migrate the Data

With the destination ready, mail is copied from the old system to the new one. This often runs in the background over several days while people keep using their existing mail as normal.

Large archives take time, so starting early avoids a last-minute crunch. A first pass copies the bulk of the mail, and a later sync catches anything that arrived while the copy was running, so the two systems stay closely matched right up to the switch.

Nothing is deleted from the old system at this point, which keeps a safety net in place. If anything looks wrong, the original mailboxes are still there, untouched.

Stage Four: DNS Cutover and Go-Live

Finally, the mail flow is pointed at the new system by updating the domain records. This is the moment new mail starts arriving in the new mailboxes instead of the old ones, and it is the step that needs the most care. The next section explains why.

What Is the DNS Cutover and Why Does It Matter?

The DNS cutover is the step that redirects incoming mail from the old system to the new one by changing the domain’s MX records. It is the one point in the whole move where mail can slip through the gap, so it needs the most care.

MX records tell the internet where to deliver mail for your domain. Until they are changed, every message keeps going to the old platform no matter how much data has already been copied across.

The catch is that DNS changes take time to spread across the internet, so for a short window some mail may still reach the old system. A good migration plans for this overlap rather than hoping it away: both systems stay live and monitored, and anything still arriving on the old platform is swept across so nothing is stranded.

The cutover is also timed for a quiet period, such as overnight or over a weekend, so the switch happens while few people are sending mail. Do it this way and staff sign in on Monday to find their mail waiting. Rush it, and messages can end up stranded on the old system where nobody thinks to look.

What Does a Well-Run Migration Look Like?

A well-run email migration keeps the business trading the whole way through, moves every mailbox across in full, and leaves staff with the same mail, contacts, and calendars they had before. The example below shows how that plays out from an owner’s point of view.

Picture a Christchurch business with fifteen staff, an ageing mail server, and a couple of shared inboxes for accounts and sales. The audit finds two mailboxes belonging to former staff that still receive supplier mail, plus one enormous archive going back a decade. All three are the sort of thing an unplanned move would miss.

New accounts are built in Microsoft 365 over a week, data copies across in the background while staff keep working, and the cutover runs on a Friday night. By Monday, staff sign in, see their full history, and the shared inboxes work exactly as before. The old server is kept running for another fortnight as a safety net, then retired once everyone confirms nothing is missing.

How to Migrate Email Without Losing Mail

To migrate email without losing mail, keep the old system running until the new one is fully verified, take a backup before you start, and only switch the old system off once every mailbox, folder, and calendar is confirmed present. A written email migration plan that lists these checks keeps the move on track.

Before the switch, confirm a backup of the old mailboxes exists as a fallback. A migration is not a backup, and keeping email security best practices in place on the new platform protects the mail once it has moved.

Checks Before You Decommission

After the cutover, verify that recent mail is arriving, that folders and archives came across in full, and that shared mailboxes and calendars work for the people who use them.

It helps to have a short checklist that a few staff run through: send a test message in and out, open an old archived folder, check a recurring calendar entry, and confirm the shared mailboxes still receive mail. A handful of real checks catches far more than a single technical tick.

Only when the team confirms everything is present should the old system be shut down. Skip that final check and you risk finding out weeks later that an archived thread never came across, when it is too late to go back for it.

Keep a Backup on the New Platform

A common misunderstanding is that moving to a hosted platform means backups are handled automatically. The platform keeps your mail available, but it is not a substitute for a proper backup that can recover a deleted or corrupted mailbox weeks later.

Setting up backup on the new system is part of finishing the job properly, not an optional extra. It is far easier to arrange during the move than to bolt on after an incident.

Common Pitfalls to Avoid

The usual failures are turning off the old system too early, forgetting shared or ex-staff mailboxes, ignoring calendar and contact data, and skipping the post-move verification. Each one is avoidable with a structured plan and a clear checklist.

Another quiet trap is leaving old forwarding rules in place, so mail keeps bouncing to an account nobody watches anymore. Reviewing rules and forwards during the audit stops that before it becomes a problem.

Should You Handle Email Migration In-House or Get Help?

Small, simple migrations can be handled in-house, but any move involving multiple mailboxes, shared accounts, or a live domain benefits from experienced help. The cost of lost mail almost always outweighs the saving.

The risk is rarely the copying itself. It is the cutover timing, the accounts nobody remembered, and the pressure of doing an email migration once, correctly, while the business keeps running.

An experienced provider has run the process many times and knows where mail goes missing. They plan the switch, run it out of hours, and stay on hand through go-live to catch any issue before staff feel it.

There is also a hidden cost to the do-it-yourself route: the hours your own people spend learning the process, plus the disruption if it goes wrong. For most businesses, the value of the team’s time and the certainty of a clean move make outside help the cheaper option overall.

What to Ask a Provider

Before handing the job over, ask how they protect against lost mail, when the cutover will run, and how long both systems stay live. Ask what they migrate beyond the inbox, and whether backup on the new platform is included.

Clear answers to those questions are a good sign. A provider who talks only about copying data, and not about the cutover and verification, has not thought through the part that actually causes problems.

Get an email migration right and there is nothing to show for it: no lost messages, no missed enquiries, no lost days. The businesses that reach that point are the ones that treated the move as a proper project and gave the cutover the attention it needs.

Move Your Email With Confidence

Exodesk plans and runs email migrations for businesses across Christchurch, Dunedin, and the wider South Island, moving every mailbox to Microsoft 365 without downtime or lost mail.

Our Cloud Solutions team handles the audit, the copy, and the cutover, so your team keeps working while the move happens quietly in the background.

Contact us today to discuss how we can help your business or connect with us on LinkedIn to stay updated with more insights.

Frequently Asked Questions

What is email migration?

It means transferring your mailboxes to a different platform, often Microsoft 365, so that all your saved messages, address books, and calendar entries carry across in full. The mail flow is redirected too, letting staff keep sending and receiving with no gap. When it is done properly, nothing disappears and there is no interruption to work.

How long does an email migration take?

A small business with a handful of mailboxes can migrate in a few days, while larger organisations with big archives may take a week or more. Most of the time is spent copying data in the background, which does not interrupt daily work. The actual cutover is usually done out of hours in a single window.

Will we lose any emails during the migration?

A properly planned email migration does not lose any mail. The old system is kept running until the new one is fully verified, so there is always a fallback. Messages are only at risk when the source system is switched off too early or the cutover is rushed.

What is a DNS cutover in email migration?

A DNS cutover is the step that redirects incoming mail to the new system by changing the domain’s MX records. It is the point at which new mail starts arriving in the new mailboxes. Because DNS changes take time to spread, both systems are usually kept live briefly to catch any mail still reaching the old platform.

Can we keep using email while we migrate?

Yes. In most migrations, staff keep using their existing mail as normal while data copies across in the background. There is only a brief transition around the cutover, and with good planning most people notice no interruption at all.

Do contacts and calendars move too?

Yes. A full email migration moves contacts, address books, calendars, recurring meetings, shared mailboxes, mail rules, and signatures, not just the inbox. Missing any of these is a common sign of a rushed migration, so it is worth confirming they are included before you start.

Is it better to migrate email to Microsoft 365?

For most businesses it makes sense to migrate email to Microsoft 365, because it combines reliable email with shared calendars, Teams, file storage, and mobile access under one login. It offers better reliability and value than an ageing on-site server or a basic hosted mailbox. The right choice still depends on how your team works.

Do we need a backup before migrating email?

Yes. You should confirm a backup of the old mailboxes exists before the migration begins, as a safety net if anything is missed. A migration is not a backup, so keeping a proper backup in place on the new platform afterwards is just as important.

Can we do an email migration ourselves?

A very small, simple migration can be done in-house, but moves involving multiple mailboxes, shared accounts, or a live business domain are safer with experienced help. The tricky parts are the cutover timing and the accounts nobody remembers, which is where lost mail usually happens.

How much does an email migration cost?

Cost depends on the number of mailboxes, the volume of data, and the complexity of the switch, so it is usually quoted per project after a short audit. For most small and medium businesses the cost is modest compared with the disruption of a migration gone wrong. A provider can give a fixed scope once they know your setup.