Email Archive Migration: How to Plan and Run It Without Losing a Message

An email archive is the place old mail went to die quietly: a Veritas Enterprise Vault server in the basement, a Mimecast or Proofpoint cloud contract, a Google Vault retention rule, a Barracuda appliance. Then the contract ends, the server reaches end of life, a company is bought or a legal team needs everything in one place, and years of mail have to move. This guide is the plan. It covers what each platform hands you when you export and what the common targets will accept. Then it walks the six steps that get every message across with its folders, dates and attachments intact.

What Email Archive Migration Means and When It Happens

Email archive migration is the move of archived mail from one archive system to another, or into a live mail platform, with folders, dates, attachments and metadata preserved. It is not a mailbox migration. A mailbox migration copies live mailboxes between servers. An archive migration starts from an export that is often years deep and often belongs to people who no longer work at the company. It carries compliance duties with it.

Four triggers start most projects. A cloud archive contract is ending and the price to renew is not worth paying. An on-premises archive server such as Enterprise Vault or SourceOne has reached end of life. A merger means two or three archives must be consolidated into one. Or a regulator, an audit or a court case needs every custodian's mail in a single searchable place. Firms under SEC, FINRA, HIPAA or GDPR rules also have to prove the migration itself did not lose or alter anything, which is why chain of custody runs through every step below.

Before You Plan an Email Archive Migration

• Time2 to 12 weeks
• DifficultyMedium to hard
• CostExport + tools
• Runs onAdmin console + Windows

Three starting points cover most projects. Pick yours and the card takes you to the right section.

The Email Archive Migration Map

Every archive migration is the same shape. A source platform produces an export in one or more formats. A target accepts one or two formats under a size rule. When the two do not match, a conversion step sits in the middle. Read your project left to right on this map and you have the outline of the plan.

Two things on the map decide most of the effort. First, whether your source exports PST at all. If it does, and your target is Microsoft 365, Mimecast or Outlook, you may not need the middle column. Second, size. Microsoft wants PST files under 20 GB and Mimecast recommends 5 to 10 GB. A ten year journal store is neither. Splitting is a conversion task even when the format already matches.

Email Archive Migration in 6 Steps

The steps below are the order that avoids rework. Skipping the pilot is the most expensive shortcut in this list.

1Step 1Inventory the archive before anything moves

Write down every store: platform, size, number of mailboxes, date range and whether it holds per-user data, journal data or both. Ask the archive admin console for its own totals, because folder sizes on disk lie when stores are compressed or single-instanced. Mark which custodians sit under legal hold. This sheet becomes your batch tracker in Step 5.

You should havea sheet with one row per store and a total that the project sponsor has seen. Surprises later usually trace back to a store missed here.

2Step 2Choose the export format each source offers

Open the export screen of each platform and list the formats. Pick PST where it exists and the target takes PST. Where the only options are EML, MSG, MBOX or an EDRM package, take the richest one that keeps attachments and headers. Then plan a conversion. Section 4 lists the formats platform by platform. Whatever you pick, unzip one export and look at the folder before you order the rest.

3Step 3Pilot the archive migration with one mailbox and one journal slice

Vendors call this the proof of concept (PoC). Export one real user with a large mailbox and one month of journal data. Run them through the whole path: export, convert if needed, import, open in the target. Count messages at each stage and compare. Open the oldest message, one with a large attachment and one with non-English text. If the counts and the three messages survive, the path works. If not, you have found the problem on one mailbox instead of five hundred.

4Step 4Convert the archive export into what the target accepts

Skip this step only when the export format and size already match the target. Otherwise, open the export folder in Univik Email Archive Converter. The tool reads EML, MSG, MBOX and EDRM folders and preserves the metadata that matters in an email archive migration: folder structure, RFC 5322 headers, sent and received dates, Message-ID and attachments. It writes one PST per mailbox, split at the size you set (see how to split a large PST file for the size rules). For loose message files the sister guides on EML to PST and MSG to PST go deeper. Keep journal exports as their own PST or zipped EML set so the target can treat them as compliance data. The per-email log it writes is part of your chain of custody, so file it with the export logs.

You should seethe same message count in the converter log as in the export manifest, and PST files that open in Outlook with the custodian's folder names intact.

5Step 5Import the archive in batches and track every one

Migrate in batches of 20 to 50 mailboxes with the oldest data first, the archive-first order most migration teams use. Record each batch in the inventory sheet: files, size, job name, status, report result. For Microsoft 365 that means one mapping file and one import job per batch, covered step by step in how to import PST to Office 365. For Mimecast it means one Legacy Archive Data Management submission per batch with per-user and journal data kept apart. Never delete a source export until its batch shows clean.

6Step 6Verify, re-apply retention, then retire the old archive

Verification is three checks per batch. The import report shows zero failed files and no orphaned or corrupted items. Item counts in the target match the export manifest within a small tolerance. Two named users have opened old messages with attachments. Then re-apply retention policies and legal holds in the target, because imports often pause them. Only after every batch passes do you set the old archive to read only. Keep it for 30 to 90 days and then decommission.

What Each Archive Platform Exports

The table below is the export layer of the email archive migration map, platform by platform. Green means the platform can hand you PST, so the Microsoft 365 and Mimecast routes may need no conversion. Amber means you will get EML, MSG, MBOX or an EDRM package and a conversion sits in the middle. Each row links to the Univik page that reads that platform's export and to our click-by-click export guide where we have one.

What Each Migration Target Accepts

The target sets the rules for a legacy archive migration, and the rules are stricter than most teams expect. These are the ones that shape batches and file sizes.

Journal or per-user decides the target too. In a Microsoft 365 archive migration, per-user data lands in individual accounts, so each account must exist first, including leavers as shared or inactive mailboxes. Journal data is a single compliance store: in Microsoft 365 it goes to a dedicated journal mailbox, in Mimecast to the Not Per User queue, EJF preferred so BCC recipients survive. Mixing the two in one PST is the fastest way to duplicate a year of mail in every inbox.

Fix Common Email Archive Migration Problems

Three problems account for most stalled attempts to migrate an email archive. Read the symptom in the red box, then the fix beneath it.

Not sure which route your archive needs? Zip twenty or so messages from the export, note the platform, the total size and the data type (per-user or journal), then send it to our support team. We will map it before you buy anything, or quote the done-for-you migration service if you would rather hand it over.

Email Archive Migration Questions

Leena Taylor Paul

Written and maintained by Leena Taylor Paul and the Univik team, developers of Windows data conversion and recovery software since 2013. This guide distils the archive migrations our support team has walked customers through, from Enterprise Vault decommissions to Mimecast contract exits, and the target limits were checked against Microsoft's and Mimecast's current documentation. Last verified September 2026. Need a hand? Contact our support team.

Sources checked: Microsoft Learn, Overview of importing PST files · Microsoft Learn, Network upload · Mimecast, Archiving PST Data · Mimecast, Zipped EML Data · Arctera eDiscovery Help, Exporting emails

Related Email Archive Migration Guides