# Tenant consolidation intro email, annotated | SourceX

Canonical: https://refer.sourcex.si/resources/tenant-consolidation-introduction-email
Last updated: 2026-11-04

Write to the executive who owns the acquired company's history after closing. Use a dated subject line, then three short blocks: the identity-mapping finding, what SourceX does with your referral interest disclosed, and an offer to introduce that asks for a description only. Attach nothing and name no individuals. The template below is ready to adapt, and the notes after it explain each sentence and what must stay out of it.

This email is part of the guide to [Microsoft 365 tenant migration after an acquisition](/guides/microsoft-365-tenant-to-tenant-migration-after-acquisition). Use it only after the conversation in the [tenant consolidation partner playbook](/guides/tenant-consolidation-data-referral-opportunity) ends with the owner saying they want to hear more.

## The email, ready to adapt

Fill each placeholder from the owner's own answers. Keep it under 200 words.

> Subject: {acquired company} history before the source tenant is retired
>
> Hi {first_name},
>
> Thank you for the time on {meeting_date}. Our mapping work confirms that current staff carry over by address match without anyone opening mail. {it_lead} estimates that about {unmapped_count} mailboxes, mostly former employees and shared boxes, have no target account, with history back to {first_year}. You said you would rather decide what happens to that history than let it lapse with the tenant.
>
> SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. Nothing leaves {company} unless it agrees terms. To be clear about my position: I am a SourceX referral partner, and SourceX may pay me a reward if a qualifying license completes. SourceX funds it separately, it does not reduce what {company} would receive, and it has no effect on our migration work.
>
> If useful, I can introduce you. SourceX would start with a description only: which record sets, roughly how many years, and who can approve a discussion. Reply "yes" and I will connect you, or "no" and I will drop it.
>
> {your_name}

## Why each line is there

| Line | Why it is there | What never goes in it |
| --- | --- | --- |
| Subject line | Names the company and the dated event, so the owner can find and forward it | "Opportunity", "earn", a dollar figure or anything that reads as a pitch |
| "Thank you for the time on {meeting_date}" | Shows the email follows a real conversation the owner agreed to | Any hint that the owner already committed to something |
| "Current staff carry over by address match without anyone opening mail" | Answers the opening question in one line and settles the content worry | Technical detail the owner did not ask for, such as object IDs or GUIDs |
| "{it_lead} estimates about {unmapped_count} mailboxes..." | Credits the figure to its source and keeps it a count, at metadata level | Names of former employees, mailbox owners or anything quoted from mail |
| "History back to {first_year}" | Gives depth of record, which is what a review first wants to know | Claims about what the history is worth |
| "You said you would rather decide..." | Uses the owner's own words, so the next step is theirs | Pressure or deadlines that are not the documented retirement date |
| "SourceX licenses approved business data..." | One accurate sentence on what SourceX does | Buyer names, AI labs or promises of demand |
| "Nothing leaves {company} unless it agrees terms" | Makes clear the next step costs nothing and commits to nothing | Any hint that records are already being reviewed |
| Disclosure sentences | States your interest plainly before any introduction | Vague wording such as "I may benefit" without naming SourceX |
| "No effect on our migration work" | Keeps the referral separate from the paid project | Links between the referral and project pricing, scope or timing |
| "A description only" | Sets the metadata-only boundary in writing | Requests for exports, samples, mailbox lists or admin access |
| "Reply yes... or no" | Gives a one-word way to decline | Follow-up threats or "last chance" phrasing |

The mapping sentence is accurate because of how Microsoft's tooling works: 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, before workload licenses are applied in the destination ([Microsoft](https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-identity-mapping?view=o365-worldwide)). Do not go beyond what the client's own mapping run showed.

The disclosure is in the body, not a footer. The FTC's Endorsement Guides call for clear and conspicuous disclosure of a connection between an endorser and a seller that the audience would not expect and that could affect how much weight they give the recommendation, and the chance of payment is such a connection ([eCFR](https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5)). Whether those guides reach a private email is for your own advisors; writing it plainly removes the question.

## What never goes in a tenant consolidation introduction

- **Content of any kind.** No quoted mail, subject lines from mailboxes, file names from team sites or screenshots of the migration console.
- **People.** No names of former employees, shared mailbox owners or anyone whose account will not map.
- **Exports or lists.** Even a mailbox inventory with addresses is more than SourceX needs at this stage.
- **Reward figures as a promise.** If you mention the program, use the exact terms: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid only after the conditions in the [program terms](/terms) are met. Most partners simply link the [rewards page](/rewards).
- **SourceX on copy.** Wait for the owner's yes. The [double opt-in introduction template](/resources/double-opt-in-introduction-email-template) shows the second email that follows it.

## Adapting the draft when the answers differ

| What the owner told you | Change to the draft |
| --- | --- |
| Mapping is still in progress | Replace the second sentence with: "Mapping is underway, and the early run shows current staff carrying over by address match." |
| Shared mailboxes are the main concern, not leavers | Replace "mostly former employees and shared boxes" with "mostly shared department mailboxes" |
| The source tenant has no retirement date yet | Change the subject to "{acquired company} history before consolidation" |
| A colleague will lead for the owner | Address both and name the colleague as the contact for SourceX |
| The owner asked how the reward works | Add: "SourceX publishes its reward terms on its rewards page" with the link |

The [introduction email worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) collects the placeholders, the [introduction email builder](/tools/introduction-email-builder) produces variants, and the guide to [introduction email subject lines](/resources/introduction-email-subject-line) covers alternatives to the dated subject.

## After the owner replies yes

Submit the introduction through your partner account with the authorized contact's details and your notes, then step back; SourceX works with the company directly. Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, one partner per company.

Check fit first: 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. What stays unknown until SourceX reviews it: whether the history fits a dataset need, the rights review result, preparation needs and any offer. Other partner types are listed on the [partner hub](/for).

## 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.

Before you send the draft, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms), so the disclosure in your email matches what you signed.

## Sources

- https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-identity-mapping?view=o365-worldwide
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
