GUIDE · MIGRATIONS

Migrating email and collaboration to a new platform: steps and pitfalls

After this guide you will know how to organise the migration of email, calendars, contacts and shared files to a new platform without losing messages or interrupting communications. You will see which data must be moved, how to manage the period in which two systems coexist, which configuration records to check and how to confirm that the switch is complete.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. Why email is the most sensitive move

Email is the system everyone uses and nobody wants to see go down. A file server outage is noticed after a few hours; an email problem is noticed immediately, because customers, suppliers and colleagues keep writing without knowing that anything has changed. Email also involves security and retention: messages contain personal data, confidential attachments and communications that may need to be retained. A badly executed switch can leave orphaned mailboxes, active delegations and forwarding rules pointing to addresses that nobody checks any more.

2. Prerequisites before you start

Before you touch the configuration you need a precise inventory and some agreements. You must know how many mailboxes exist, which are shared, which aliases and distribution lists are in use and who has delegated access to other people's mailboxes. The new provider must state in writing its retention policies, whether its staff can access messages, and how deletion works, before signing and not after the first problem.

  • Inventory of mailboxes, groups, aliases, distribution lists and shared mailboxes.
  • Administrative access to the domain and DNS records, with a documented change procedure.
  • Agreement with the new provider on retention, access to messages and deletion.
  • Communication plan for users, with switchover dates and instructions for each device.
  • Archive copy of current messages, verified with a restore test.

3. What to move: messages, calendars, contacts and files

Messages are the most visible part, but not the only one. Calendars contain recurring meetings and invitations involving external people, and if copied badly you lose invitations and availability. Contacts often pass through exchange formats that lose custom fields, groups or notes. Verify each type of data separately, with a real example for each, and do not assume the result is complete.

Shared files need particular attention. Moving documents does not automatically carry their permissions with it, and a working group may find folders readable by everyone or by no one. Check permissions after the transfer. The same goes for forwarding rules and personal filters, which are often not migrated and stop working without anyone noticing.

4. The coexistence period

In most cases the two systems coexist for a period, during which some mailboxes are already on the new environment and others are not. Coexistence requires deciding how mail is routed: which messages reach the old system, which reach the new one, and how to prevent a message from bouncing back and forth between the two. A wrong configuration produces messages that bounce or sit waiting without anyone noticing. Also check which environment receives system alerts.

During coexistence keep the old environment read-only and monitor the mail queues of both. Mailboxes already migrated must be watched to confirm they receive what they should. The period ends when all mailboxes are on the new environment, messages in transit have been synchronised and no residual rule routes mail to the old system. Record the date on which that rule is removed.

5. Operational steps

The following sequence assumes the record change takes place at an agreed moment, with the mailboxes already prepared and verified. Do not change the records before testing at least one pilot mailbox, because the domain's records control where mail arrives and an error there spreads to every user within minutes. Each step has an exit check to be recorded: if the check fails, stop and resolve it before going further.

  1. In the days beforehand, reduce the TTL of the mail domain's DNS records, following the provider's guidance.
  2. Create the domain and the mailboxes on the new environment, with the same aliases, groups and distribution lists.
  3. Configure domain authentication with SPF, DKIM and DMARC records, and verify their validity before changing traffic.
  4. Migrate a pilot mailbox and verify messages, folders, calendar, contacts and attachments.
  5. Synchronise, in several passes, the messages that arrived during the initial copy.
  6. Change the MX records at the agreed moment, after verifying that the change has propagated.
  7. Reconnect mobile devices and clients, with precise instructions for each user.
  8. Keep the old environment read-only for the defined period, then decommission it according to the plan.

6. Common pitfalls

Some pitfalls recur in almost every mail migration. They almost always stem from items that nobody had included in the inventory, because they were configured years earlier and worked without attention. Finding them before the switch costs little; finding them afterwards costs a great deal, because the user notices the problem when an important message has already gone missing. The most frequent are listed below, to be checked one by one during the pilot phase, with a user who actually uses them.

  • Messages that arrive at the old system after the record change and remain unread.
  • Forwarding rules and personal filters that were not migrated and stop working.
  • Permissions on shared folders and calendars that no longer match current users.
  • Forgotten aliases and distribution lists, with messages bouncing for no visible reason.
  • Signatures, certificates and clients configured by hand with settings that no longer exist.

7. How to verify that the switch is complete

The final verification must be carried out from outside and from inside. Send test messages from an external address and reply from a migrated mailbox, then check that the whole path succeeded. Verify that calendar invitations arrive with the correct responses and that shared files are accessible only to the intended people. Also check that outgoing mail has the correct domain authentication, because an error here sends messages to recipients' spam folders. Compare message counts per mailbox on a sample basis with those of the old environment, and collect user reports in an orderly way during the first days.

8. How to start

This week, prepare the inventory of mailboxes, aliases and distribution lists, and ask a representative group of users which forwarding rules and shared folders they use. This information is the basis of the plan and often reveals dependencies nobody had considered. Then ask the new platform provider for the switchover procedure in writing, including the coexistence plan and rollback: if it cannot explain how to go back, the switch is not yet ready.

Frequently Asked Questions

Can I migrate email without interrupting the service?

In most cases yes, with a coexistence period in which messages arrive correctly in both environments. The real downtime depends on the record-change strategy and on preparation. The interruptions that remain are usually those of out-of-date clients or DNS propagation times, and they should be communicated to users in advance.

Do I have to migrate the entire mail history?

Not necessarily. Many companies bring a recent period into the new environment and keep the rest in an accessible archive that meets retention obligations. The decision should be taken with management and, if needed, the legal adviser, considering both operational needs and document retention requirements.

How do I protect email after the switch?

Check that domain authentication is configured correctly, enable strong authentication for users and review forwarding rules to external addresses. The switch is also an opportunity to remove delegations and access that are no longer needed, which often survive the old systems without anyone actually using them.

Can I carry out the migration in-house with the provider's tools?

For a small organisation with few mailboxes and no complex integrations, an in-house switch may be sufficient if there is time for testing. With many mailboxes, integrations or sensitive data, external support reduces the risk of data loss and configuration errors. Assess the provider's experience with cases similar to yours.

What happens to messages sent during the switch?

It depends on timing and configuration. During coexistence, messages should be delivered to the correct environment thanks to the record change and forwarding rules. To avoid losses, synchronise the latest messages before closing the old environment and check that the mail queues contain no stuck messages.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →