Microsoft 365 tenant-to-tenant migration after an acquisition: keep the history

Why the tenant cutover is the moment to decide about history

A tenant-to-tenant migration moves people; it does not automatically move the past. Integration plans usually scope active users' mailboxes and current files, so the acquired company's archive mailboxes, former employees' mail, older Teams chats and retired SharePoint sites are the items most at risk when the source tenant is switched off.

For a buy-and-build platform, that history is often the only complete record of how the add-on actually ran: quotes and approvals in email, customer escalations in Teams, project files and proposals in SharePoint. Once the source tenant is decommissioned and its subscriptions lapse, getting it back ranges from expensive to impossible.

Longer holds raise the stakes. Bain's 2026 global private equity report found that almost 40% of portfolio companies had been held for more than five years, up from 29% in 2019, and says GPs are holding assets longer to buy time to grow EBITDA. When owners need new sources of value inside companies they already hold, deleting an add-on's operating history by default is an expensive habit.

What gets left behind in a tenant-to-tenant migration?

Whatever sits outside the migration scope. Ask the MSP or migration partner to confirm in writing, workload by workload, what will arrive intact in the destination tenant.

Microsoft's documentation and your migration tool's documentation describe what each method supports, and those capabilities change. Confirm against current documentation, not against the last project someone remembers.

Timeline: from close to tenant decommission

If the add-on is itself an MSP, the MSP acquisition due diligence checklist adds the PSA and ticket checks that belong in the same review.

Who should be in the room

• Integration lead or operating partner: owns the plan and signs off on decommissioning.
• The add-on's IT lead or MSP: knows where history actually sits, including the forgotten archive.
• Platform CIO: destination design, retention settings and storage cost.
• General counsel: legal holds, privacy commitments and employee notices.
• CFO: the cost of keeping the source tenant a little longer against the cost of losing its contents.
• The add-on's former owner or CEO, if still involved: which records mattered in running the business.

What to preserve before the source tenant goes

• Every mailbox type (active, archive, shared and former employees') for its full date range, under the company's control.
• Teams chats and channel messages with dates and participants.
• SharePoint sites and departed staff's OneDrive content, with version history where it matters.
• Documentation of the retention policies and holds in force at cutover.
• A metadata inventory of counts, date ranges and owners, kept in the data inventory builder.
• An export log recording what was exported, by whom, when and where it is stored.

Payables history often straddles an ap@ mailbox and a payables tool; the guide on Bill.com invoice and approval history covers the tool side. The same integration usually cuts the add-on's duplicate sales tools as well, which the sales tech stack consolidation checkpoint handles.

These exports are for the company's own records. Nothing is sent to SourceX or any buyer, and no data work starts unless a license is later signed.

Privacy commitments to check before any reuse

Before an acquired company's mail or files are considered for licensing, counsel should read what that company promised customers and employees. FTC staff have stated that promises not to use customer data for undisclosed purposes, such as training or updating AI models, are enforceable whether they appear in privacy policies, terms of service or marketing materials. Customer contracts with confidentiality clauses and employee monitoring notices belong in the same review. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

What to say to the platform CEO

When the history merits a licensing review

It merits one when the add-on reached 50+ full-time employees at peak (contractors excluded), operated for several years, kept records across many systems rather than only mail, and the rights to that history now sit clearly with the platform or the acquired entity. Being acquired does not disqualify a company: operating, acquired and wound-down companies can all qualify if the data still exists. The full criteria are on the who qualifies page.

1. Ask the platform CEO or CFO whether they want to explore it.
2. Create your partner account and pass on your referral link, or use the referral form and name the entity that holds the records.
3. SourceX works out whether the company meets the baseline and who holds the rights after the acquisition.
4. The company records each system, its years of history and rough volumes in a metadata inventory.
5. One all-in price and the license terms are agreed before AI labs and data buyers review.
6. After signature, the company delivers de-identified data under the agreed rules and is paid once.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and the reward is paid only after the buyer pays and SourceX receives its fee. No reward is guaranteed. The operating partner overview explains how sponsors use the program across a portfolio.

Next step

Add a history decision to the cutover checklist for your next add-on. If the add-on fits, register as a partner and introduce the platform CEO, or have them apply at sourcex.si/apply with your referral link.