Migration vs. a Clean Start
What advantages a new email environment without history brings
When moving to a new mailbox environment, the standard assumption is that all old data should be carried over as faithfully as possible. Less attention goes to the opposite option: setting up a new environment without history and handling the old data separately. This choice is not just a technical shortcut — its strongest argument is security, alongside which it also brings governance advantages. A time saving exists too, but it is secondary to security and should not be mistaken for a clear-cut financial saving — more on that below.
- Why "migrating everything" seems like the only option
- The security advantage: no inherited mess
- The time advantage and the real cost of a clean start
- The governance advantage: consistent rules from day one
- When this advantage does not apply, and what to check beforehand
- Common mistakes and recommendations
Why "migrating everything" seems like the only option
When a company sets up a new mailbox environment — moving to Microsoft 365, after a merger, an acquisition, or when spinning off part of the company (a carve-out) — it is natural to want to carry everything over so that "nothing is lost." This choice, however, is worth weighing the same way as any other management decision: what it costs, what risks it carries, and what real benefit it offers over the alternative. The table below summarizes the main differences between a clean start and a full migration.
| Criterion | Clean start (no migration) | Full migration |
|---|---|---|
| Attack surface and inherited errors | Minimal — no old permissions, forgotten shares, or shadow IT | Everything is carried over, including historical configuration errors |
| Migration time | Shorter — a small volume of data to transfer | Longer with a standard approach (can be partially shortened with paid migration tools) |
| Cost of retaining old data after the move | Additional, if the organization has not been archiving systematically so far | No new cost — the data is already in the active environment |
| Governance rules (retention, labels, DLP) | Set up consistently, based on current needs | Historically different policies of both environments need to be merged |
| Scope of eDiscovery and audits | Smaller — years of irrelevant data are not carried over | Larger — every migrated year adds further volume to retain |
| End-user access to history | Not available directly in the new mailbox — a separate solution is needed | Yes, directly in the mailbox |
The security advantage: no inherited mess
A new mailbox without history means not just less data to transfer — it also means that years of accumulated, often already-forgotten risk are not carried into the new environment.
- Forgotten shares and permissions — old clutter in access rights (for example, items shared "with anyone with the link" or forgotten external shares) simply has nowhere to be carried over to.
- Inconsistent security settings — in mergers and acquisitions, the target environment typically also inherits a different security level from the source organization (different MFA settings, conditional access, and so on); a clean start avoids this entirely.
- A smaller surface for content that is already compromised — historical mailboxes may contain long-forgotten attachments or items that have since turned out to be risky; with a clean start, these simply are not migrated.
The time advantage and the real cost of a clean start
A smaller volume of data mainly means a simpler and faster schedule: fewer migration tasks running in parallel, less room for error, and a shorter time to full functionality of the new environment. However, this advantage is best viewed mainly as a time saving, not automatically as a financial one — the same reduction in time (for example, compared to the standard pace, where Microsoft caps mailbox migration speed at roughly 2 GB per hour) can also be partially achieved by deploying paid migration tools. It is thus more of a trade-off between time, tools, and data volume than a clear-cut saving that only a clean start delivers.
Moreover, total costs do not automatically go down with a clean start — in many cases they simply shift elsewhere. If the organization decides to retain the old data anyway (for example, for compliance reasons), it needs a solution such as an online archive or Exchange Online Archiving — and that is a real additional cost. The exception is a situation where the company has already been handling archiving of old data systematically and independently of this migration — in that case, this cost is not new, it simply continues.
The governance advantage: consistent rules from day one
In mergers and acquisitions, this advantage is especially noticeable: the target environment often also inherits different retention policies, sensitivity labels, and DLP policies from both original organizations, which then need to be additionally merged and reconciled. A clean start allows these rules to be set up consistently and according to the current needs of the new organization right from day one, instead of patching together two historically different configurations afterward.
This also has a direct impact on the scope of compliance obligations: under the GDPR principles of data minimization and storage limitation (Art. 5(1)(c) and (e)), personal data should be processed only to the extent necessary for the given purpose and retained only for as long as necessary. Not carrying years of irrelevant historical communication into the new, actively used environment is directly in line with this principle — and at the same time reduces the volume of data that needs to be searched during a future audit or eDiscovery.
When this advantage does not apply, and what to check beforehand
A clean start is not a universally best solution. In the following situations, its advantages do not apply, or they require an additional measure:
- Active regulatory or contractual obligations requiring direct access to historical communication (for example, in regulated industries) — a clean start by itself does not address this obligation; the data still needs to be retained somewhere.
- Users who routinely need historical emails for their work (for example, in long-term client relationships) — losing direct access can genuinely slow down operations if a replacement solution is not chosen in advance.
- An ongoing legal dispute or hold — in that case, the data must be preserved regardless of whether it is migrated into the new live mailbox.
Common mistakes and recommendations
- Deciding on a clean start without assessing regulatory obligations — before deciding, check whether the company has a legal or contractual obligation to retain historical communication in a specific form.
- A clean start without a plan for where the old data will go — without a replacement solution (such as an archive), you risk losing data the company still has to retain.
- Treating a clean start as universally the cheapest option — with a small data volume or a low security risk in the source environment, the benefit may not outweigh the cost of duplicate work (for example, re-creating contacts or distribution lists).
- Deciding based on IT considerations alone, without involving management and compliance — the choice between a clean start and migration has operational as well as legal risk consequences, so it is a decision for company leadership, not just the technical team.