# Tenant consolidation referral playbook | SourceX

Canonical: https://refer.sourcex.si/guides/tenant-consolidation-data-referral-opportunity
Last updated: 2026-11-04

Usually, yes. Pairing each person's old account with a new one after an acquisition relies on addresses and account identifiers, not on what anyone wrote. For a migration partner, that makes "Can the owner map old and new users without exposing message content?" a safe opening question. The answer shows which history will stay attributable to real roles after cutover, and which history, such as former employees' mailboxes, has nothing to map to and needs an owner's decision. That decision is where an introduction can start.

This playbook is part of the guide to [Microsoft 365 tenant-to-tenant migration after an acquisition](/guides/microsoft-365-tenant-to-tenant-migration-after-acquisition). It is organized the way the opportunity unfolds: the trigger, the signals, the records at risk and the conversation. If you already have the owner's yes, go straight to the [tenant consolidation introduction email](/resources/tenant-consolidation-introduction-email).

## The trigger: a closing date puts a cutover on the calendar

Tenant consolidation follows an acquisition. Once the deal closes, the buyer wants a single environment for sign-in, mail, files and security policy, so the acquired company's environment gets a retirement date. Three facts turn that into a documented event rather than a vague opening:

- **A cutover is scheduled.** People and workloads move on a plan, and the old environment is shut down after it.
- **Someone builds a crosswalk.** Each person in the old environment is paired with an account in the new one before licenses are assigned there. Microsoft's tooling does this from directory attributes, as the conversation section below explains.
- **Some people have no counterpart.** Leavers, and often shared or archive boxes, have nowhere to go in a person-to-person move, and Microsoft notes that objects left out of the crosswalk can raise warnings.

That third fact is the opening. Nobody budgeted for the history of people who left years ago, yet it often runs back further than anything else the acquired company holds.

## Signals that a client is in a tenant consolidation

You will rarely be told "we are consolidating tenants and have unowned history". You will hear the signals.

| Signal | Where you hear it | What it tells you |
| --- | --- | --- |
| "We closed on the add-on last quarter" | Account review, renewal call | A second tenant exists and has a likely retirement date |
| A request to scope cross-tenant mailbox moves | Statement of work | The identity map and cutover plan are being built now |
| Questions about licensing in the destination tenant | Procurement or IT lead | Mapping must happen before licenses are applied, so timing is live |
| "What do we do with leavers' mailboxes?" | Project meeting | History without a target account is already on someone's mind |
| A request to retire the source tenant by a set month | Steering committee | The access event is dated, which is real urgency |
| The company has 50 or more full-time employees and a long history | Deal announcement, client briefing | The history may be deep enough to matter for a review |

Two or more of these together mean the client is in the moment. One alone usually means wait.

## The records a consolidation puts at risk

Not every record set is at risk in the same way. The partner's job is to sort them at metadata level, not to judge their value.

| Record set | Why it is at risk at cutover | Who decides what happens |
| --- | --- | --- |
| Current staff mailboxes | Low risk: they map to a target user and move | IT lead, under the migration plan |
| Former employee mailboxes | No target account, so nothing to map to | Owner, with counsel and HR |
| Shared and archive mailboxes | Often excluded from the first wave or left without an owner | Department heads and the owner |
| Team sites and shared files of the acquired company | May be re-homed, merged or left in the source tenant | Department heads and the owner |
| The identity map itself | It is the only key linking old addresses to new roles | IT lead, kept with the project records |

The second, third and fourth rows are where history can disappear by default. What happens to data once a Microsoft 365 subscription lapses is covered on the page about [Microsoft 365 data after a subscription ends](/systems/microsoft-365-data-after-subscription-ends), and the [Microsoft 365 retention policy checklist](/resources/microsoft-365-retention-policy-checklist) helps the client confirm what its own policies keep.

## The conversation: from the identity map to an introduction

Illustrative. A migration partner is moving a 210-person regional insurance broker into its acquirer's tenant. The steps below keep the conversation at metadata level and give the owner an exit at each point.

1. **Open with the safe question.** Ask the IT lead: "Can the owner map old and new users without exposing message content?" A strong answer: "Yes. SMTP matching for current staff, a CSV for renamed accounts." That answer is plausible because Microsoft's Cross-Tenant Identity Mapping pairs each source user with one target user, automatically by primary SMTP address or from a CSV with the target object ID filled in, and runs before workload licenses are applied in the destination. For mailbox moves, the target MailUser carries the source ExchangeGUID and the old LegacyExchangeDN as an x500 address, so replies to older mail still resolve. None of it involves reading mail.
2. **Size what will not map.** "Roughly how many source mailboxes have no target account?" Illustrative answer: about 75 former employees and a dozen shared boxes.
3. **Date the history.** "What is the oldest year of mail and files in the source tenant?" Illustrative answer: 2011.
4. **Find the decision-maker.** "Who can decide what happens to that history after closing?" Usually the platform company's CEO, with counsel. Not the IT lead.
5. **Offer the option, with disclosure.** With the decision-maker, say that SourceX licenses approved business data directly from companies for AI training and evaluation, that you are a SourceX referral partner and may receive a reward if a qualifying license completes, and that SourceX pays it separately so it never reduces the company's payout. Then ask whether they want an introduction at all.

Record only the answers, the date and who gave them. Never request exports, mailbox lists with names, screenshots or admin access. If the owner says no, the migration continues exactly as planned. For a timed version of this conversation, see the [migration partner moment guide](/guides/moment-tenant-consolidation-microsoft-365-migration-partners); for the wider handoff, the [software consolidation handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-software-consolidation) covers what to pass on.

## Qualification: what you know before the introduction and what you do not

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

| Known before the introduction | Unknown until SourceX reviews it |
| --- | --- |
| Whether users map without reading content | Whether the history fits a dataset need |
| Rough count of unmapped mailboxes and sites | What can be licensed after the rights review |
| Oldest year in the source tenant | De-identification and preparation needs |
| Who owns the history after closing | Any offer and its terms |

Sign the Channel Partner Agreement before you submit. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Other partner playbooks are on the [partner hub](/for), and reward mechanics are on the [rewards page](/rewards).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When unmapped history needs a decision before the source tenant is retired and the owner wants to explore it, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the decision-maker.

## Sources

- https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-identity-mapping?view=o365-worldwide
- https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-mailbox-migration?view=o365-worldwide
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
