Email archive migration: what to decide before the legacy archive contract lapses

Why does an archive migration create a decision window?

Retiring a third-party email archive is one of the few moments when a company must look at years of mail it has not touched. The contract end date forces three choices: move the history, keep read access, or let it go. Licensing is a fourth option that only exists while the history still does.

Once the vendor deletes the tenant, or the data is migrated in bulk to a mailbox structure that loses journaling metadata, the option may be gone. Deciding a few months earlier costs little.

What does the timeline look like?

These are planning ranges, not contract terms. Read the actual agreement for notice, export and deletion provisions.

Who should you talk to?

The sponsor for a licensing conversation is an owner, CEO, CFO or authorized representative, not the IT manager who runs the migration. Bring the CFO or general counsel into the contract conversation anyway, because they hold the retention policy and the legal hold list.

Be careful about what an email archive contains. Email holds privileged communications, employee personal messages, third-party confidential material, and customer data. That is why rights review, redaction and exclusions are agreed with the company before any work begins, and why the company decides what, if anything, goes into scope. Partners never open, export or describe mail.

Which companies with an archive fit?

• 50+ full-time employees at peak, contractors excluded.
• Several years of journaled mail, ideally 5-10+ years, from a business with documented operations.
• Mail created by the company's own staff, not a customer's system.
• A sponsor who will consider an exclusive license for AI training for an agreed term.
• Legal hold and retention status known.
• Someone who can export, or confirm the vendor can.

Red flags: the archive was deleted already, it mainly holds another company's mail, counsel says it is under a hold or dispute, or nobody can get the data out. A company in insolvency or under an assignee also needs the court or trustee involved.

What can you say to the owner?

Keep it to one conversation. If the owner declines, drop it. The tech stack audit template is a neutral way to list every system, including the archive, with retention dates.

How does an introduction work?

1. The owner agrees to be introduced.
2. You submit the referral form or send your referral link, with basic fit information only.
3. SourceX qualifies size, history, breadth and rights.
4. The company completes a data inventory of systems, including the archive.
5. Price and terms are agreed, buyers review, and the company signs only if the terms work.
6. If a deal closes, the company is paid, and the partner reward follows after SourceX receives its fee.

Typical timing: once a company is deal-ready, buyers typically respond within about two weeks, and payment arrives within about 60 days of invoicing once the buyer selects the data. These are program norms, not promises.

What if the company is also changing ownership?

An archive contract often lapses in the same year as a sale, merger or wind-down. If a buyer is integrating the company, the acquirer's IT team may decide to purge the old archive to save cost, which can happen before anyone raises licensing. Ask early who owns the decision. In a sale, the seller's adviser and the buyer's counsel will usually want to know about an exclusive license before it is signed, because it affects what the buyer inherits. In a wind-down, a trustee or assignee may control the assets and must be involved.

How do you describe the archive without opening it?

Use facts you already have from the project scope: the vendor name if the client is comfortable sharing it, the date range, the number of mailboxes or users covered, whether journaling was on, and the retention policy. Those are enough for SourceX to gauge breadth during qualification. Anything about the content of messages stays with the company.

What should be preserved regardless of the answer?

Keep a verified export of the archive for retention reasons, record the vendor's deletion date, and keep an index of what the archive covers (dates, mailboxes, journaling scope). None of this commits the company to anything. The data migration specialist page covers how migration professionals approach it, and the project archives question addresses a consultancy's own materials.

Common mistakes

How do rewards work?

Partners earn 25% of eligible platform fees SourceX actually collects, capped at $100,000 per referred company, and only after the buyer pays and SourceX receives its fee. No reward is guaranteed. MSPs should check their client agreements for any limits on referral compensation. Further reading: the PSA records page for ConnectWise and additional revenue streams for MSPs.

Illustrative scenario

Illustrative: a fictional 140-person engineering firm has used a hosted archiver for seven years. The MSP's renewal review shows the term ends in five months. The account lead asks the CFO, who checks with counsel, confirms no holds, and agrees to an introduction. The MSP keeps the verified export and sends only the company name and sponsor details.

Next step

List clients with legacy archives using the network opportunity finder, confirm who qualifies, and register as a partner. MSP context is on the managed service providers page.