Contents of this article
Moving your mail out of Microsoft 365 or Exchange yourself is perfectly doable, as long as you work in the right order. Here is that order, plus what is Exchange-specific and therefore won't come along.
Step 1: take stock before you touch anything
Make a list first; without it, you'll discover halfway through that there was something else.
- Which mailboxes there are and which of them need to move.
- How big each mailbox is: that determines how long it takes and how much space you need.
- Which shared mailboxes there are and who has access. In Exchange, that is a separate kind of object, not an ordinary mailbox.
- All aliases per mailbox. An address you forget no longer exists after the move.
- Which systems send mail on behalf of your domain. This is the point almost everyone forgets.
For that last one, think of your accounting package, the contact form, a newsletter service and the copier that emails scans. Those senders are in your SPF record. If one is missing when you set that record up again, your ordinary mail works but your invoice mail lands in spam. See Setting up SPF, DKIM and DMARC.
Step 2: copy from IMAP to IMAP, with both environments active
Microsoft 365 speaks IMAP, and so does your new email hosting. That lets you copy mailbox by mailbox, using a migration tool or a mail program in which you set up both accounts side by side and drag the folders across.
That is the safe route: you don't move anything, you duplicate it, so until you cancel the old subscription everything exists in two places. Meanwhile your staff keep working in the old environment, because the MX records haven't been switched yet.
Copy one mailbox completely and check it before you do the rest.
Step 3: lower the TTL of your MX records in advance
The TTL (time to live) is the number of seconds other DNS servers may remember your record. If it is high, mail servers keep sending to the old environment for hours after your change. So set it low a day or two in advance, for example 300 seconds, and wait at least as long as the old TTL before you switch the MX records. Once everything is stable, set the TTL back.
What is Exchange-specific and won't come along
IMAP copies messages and folders. Whatever else Exchange offers, you either set up again or it disappears.
Shared mailboxes
These don't exist in that form outside Exchange. You copy the contents over IMAP as an ordinary mailbox; you set up access again, as a mailbox with its own password or as a distribution list.
Resource calendars
Meeting rooms that accept or decline invitations by themselves are an Exchange feature. You can share a CalDAV calendar, but that automatic response doesn't come along.
Delegation and "send on behalf of"
The distinction between sending on behalf of someone and sending as someone is specific to Exchange. Elsewhere it comes down to one thing: someone gets the right to send from an address. Who actually sent the message is then something you agree on rather than configure.
Transport rules
Rules that apply centrally to all mail, such as adding a disclaimer, blocking attachments or redirecting mail, live in the Exchange organisation. What you get back of these depends on your new environment. Write them down before you cancel: afterwards you can no longer look them up.
Retention policies and archive
Policies that move or delete messages after a period don't come along. You copy the online archive mailbox separately; many tools don't pick it up automatically. If you have a legal retention obligation, first sort out where that mail will go.
Calendar and contacts
These don't go over IMAP. For each user, export the calendar and contacts and import them into the new environment. The most fragile part is recurring appointments with an exception, like the weekly meeting that was an hour later just once. These can shift during export and import or fall back to their usual time; check them over the coming months.
Check afterwards, and only then cancel
- For each mailbox, compare the number of messages per folder, old against new. If a folder differs, copy it again.
- After switching the MX records, collect the last mail from the old environment.
- Test sending and receiving from every mailbox, and the systems from your inventory: send a test invoice and fill in your contact form.
- Cancel Microsoft 365 last. As long as that subscription runs, you can still retrieve things. Once it's gone, it's gone.
What this doesn't solve
This guide covers mail, calendar and contacts. SharePoint, OneDrive, Teams and signing in through Entra ID are separate from this. Teams chat history isn't in your mailbox and can't be moved: export it yourself before you cancel.
If the way you work mostly depends on those parts, moving just the mail may not be the improvement you're looking for. Better to realise that now than halfway through.
If you'd rather not do this yourself, we can do it for you with our email migration service (in Dutch).
Further reading
Was this article helpful?
Thank you for your feedback.
Thank you. What were you missing? Let us know at support@hostage.nl and we will add it to the article.
Related articles
- Set up an out-of-office reply in webmail Set up an automatic reply that starts and stops on the days you choose.
- Using webmail: logging in and finding your way Logging in to webmail and finding your way around folders, messages and settings.
- Change the webmail language and time zone Change the language and time zone of webmail in the preferences.
- Forward email automatically from webmail Forward mail from a mailbox to another address automatically using webmail.
Still stuck?
Send us a message. We will help you, usually within one working day.