Why tenant consolidation is the moment
Consolidating tenants forces a list: every source account either maps to a destination account or does not. That list is the first time anyone sees, in one place, how much of a company's history belongs to people who have left. The migration partner is already building it, so the identity-continuity question costs nothing extra to ask.
The partner's role stays narrow. You ask about structure and dates, the owner decides, and SourceX handles any licensing review under its own agreement with the company. The tenant-to-tenant migration guide covers what to preserve; this page covers the owner conversation itself.
How do you run a 15-minute owner conversation about mapping old and new users?
Run it as five short blocks that move from the migration fact to the owner's decision, and end with a clear yes or no. The owner should leave knowing what is unmapped and who decides, whether or not they want an introduction.
The agenda
Illustrative. A partner consolidating a 230-person engineering services firm into its parent's tenant meets the firm's CFO after the mapping file is drafted.
| Minutes | Block | Partner says or asks | Output |
|---|---|---|---|
| 0 to 2 | Frame | "One question outside the migration scope, which you can decline." | Permission to continue |
| 2 to 6 | Identity map | "Can we map old and new users without exposing message content? Our file shows current staff matched by address." | Mapped share confirmed |
| 6 to 10 | Unmapped accounts | "About 85 source accounts, mostly former staff back to 2011, have no target. What should happen to them?" | Count, date range, owner |
| 10 to 13 | Decision-maker | "Who can decide whether that history is kept, deleted or reviewed for licensing?" | Named authorized contact |
| 13 to 15 | Opt-in | "SourceX runs licensing reviews; I'm a referral partner and may be paid if one completes. Want an introduction?" | Yes: introduction. No: stop |
Two rules hold the agenda together. Nothing in it requires opening a mailbox, and the reward is disclosed before the owner answers, not after. If the answer is no, the conversation ends there with no follow-up pitch. Meeting agendas for other settings, such as a sell-side kickoff or a portfolio review, use the same opt-in pattern.
What to avoid saying
Do not estimate what the history is worth, suggest any buyer, or imply the reward depends on what the owner chooses to preserve. Do not offer to export anything for SourceX. The question is whether the owner wants a decision, not which decision.
How is the identity map built without exposing message content?
From directory data alone. Microsoft's Cross-Tenant Identity Mapping pairs each source user with one target user, either by primary SMTP address or from a CSV of target object IDs, and it has to run before workload licenses are applied to target users. Nothing in that step reads a message, a file or a chat.
That is why the question at minute 2 can be asked without exposing anything or making a pitch. The partner is already holding the mapping file; the owner only needs to hear what it shows. Three numbers come straight out of it:
| Field from the mapping file | What it tells the owner | What stays closed |
|---|---|---|
| Source accounts matched to a target | How much history follows current staff into the new tenant | Every mailbox and file behind those accounts |
| Source accounts with no target | How much history belongs to people who have left, or to shared and service accounts | The content of those accounts |
| Earliest and latest activity years | How far back the unmapped history reaches | Who wrote what, and to whom |
Illustrative. In the engineering services example, the mapping file matches about 145 current staff by address and leaves about 85 accounts with no target, mostly former staff back to 2011. The partner reads those counts to the CFO and nothing more.
Two facts shape what the owner can still decide about those 85 accounts. A deleted Microsoft 365 user can be restored with their data for 30 days, after which the account and mailbox are permanently deleted. And a mailbox only becomes inactive if a hold or retention policy was applied before the account was deleted. The partner does not need to resolve either point in the meeting; it is enough that the owner knows a decision exists and who should make it.
What should you record after the meeting?
Record the outcome as metadata, in your own notes, whatever the owner decides. A short record protects the owner, protects your attribution if they opt in, and shows the conversation stayed inside the agreed scope.
- Answer to the identity question: yes, mapped by directory attributes, with the matched and unmatched counts.
- Unmapped history: account count, account types (former staff, shared, service) and date range.
- Named decision-maker: the person the owner says can authorize a licensing discussion.
- Disclosure: that you explained the referral reward before the owner answered.
- Outcome: opted in, declined, or wants to think about it, with the date.
If the outcome is "declined", that line closes the file. If it is "opted in", the next step is a short introduction to the named decision-maker, sent only once the company confirms it fits the baseline below.
Reward disclosure and who can authorize
The person who can authorize a licensing discussion is the CEO of the entity that holds the records after the acquisition, often with the CFO or general counsel preparing the case, not the IT lead who owns the migration. The company baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, 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.
Partners sign the Channel Partner Agreement before submitting introductions. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Unknown until SourceX reviews it: who holds the rights after the acquisition, what privacy commitments limit reuse, and whether a buyer wants the result. Microsoft partners can see the wider program on the CSP partner page, and other partner types under for.
Go deeper on tenant consolidation
- Tenant consolidation archive context checklist: a checklist of the retirement, licensing, restore-window and retention dates to verify before the source tenant closes.
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.
If the owner opts in at minute 15 and the company fits, register as a partner, confirm the baseline on who qualifies, and read the terms before you introduce the decision-maker.