# Domain consolidation introduction email | SourceX

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

Send a short email to the company's authorized decision-maker that states, in the owner's words, which years of mail, attachments and linked Drive files survive the consolidation, names the cleanup date the company has set, discloses your referral interest, and asks only for a call about metadata. The draft below has a subject line, three paragraphs and one ask. The annotation explains each sentence and what must never go in it.

This page is part of the [domain consolidation guide for Google Workspace resellers](/guides/moment-domain-consolidation-google-workspace-resellers). Most resellers send it after the owner conversation in the [domain consolidation meeting agenda](/resources/domain-consolidation-meeting-agenda).

## When the email is ready to send

The email is the last step of a short permission chain. If any link below is missing, fix that first and leave the draft closed.

1. **The owner opted in.** They said yes to an introduction, in words, after you disclosed that you are a referral partner. A friendly reaction during a cutover call is not consent.
2. **You have the year span from them.** "Mail from 2014, attachments mostly intact, linked files reliable from 2019" is the kind of sentence the email needs. If the owner and their admin could not give it, the [archive context checklist](/resources/domain-consolidation-archive-context-checklist) lists what to settle before writing.
3. **You know the recipient.** The person who can authorize a licensing discussion, by name and title: usually the owner, CEO or a designated officer, not the IT contact who ran the migration.
4. **The partner agreement is signed.** The Channel Partner Agreement comes before any introduction is submitted.

Workspace admin access does not change any of this. Holding super admin rights during a consolidation gives you the technical means to look inside mailboxes; it gives you no permission to do so for this purpose.

## The draft: subject line, three paragraphs, one ask

Illustrative. Bracketed placeholders are filled only with facts the owner or their admin gave you.

> **Subject:** Introduction: [Company] and SourceX, mail and file history before the domain cleanup
>
> Hi [Decision-maker name],
>
> While we planned the move of [acquired domain] into [primary domain], [Owner name] described the company's history: mail back to about [year], attachments mostly intact, and linked Drive files reliable from about [year], when the team moved to shared drives. Departed staff accounts are due for [archiving or deletion] on [date the company set].
>
> You can decide whether any of that history is worth a conversation with SourceX, which licenses approved business data directly from companies for AI training and evaluation and handles the agreement, rights review, data preparation, delivery and payout. I have not opened, searched or exported any mailbox or file; everything above came from your team.
>
> For transparency, I am a SourceX referral partner. If a qualifying license completes, SourceX may pay me a reward from its own funds, and it never reduces what [Company] would be paid. Would a 20-minute call about which years, which accounts and who owns them be useful before any accounts are removed?
>
> [Your name]

## Annotation, sentence by sentence

Each row is one sentence of the draft. The third column lists what to keep out of it.

| Sentence | Why it is there | Never put in it |
|---|---|---|
| Subject line | Names both parties and the record type, so the email is not mistaken for a sales pitch | "Opportunity", a dollar figure, or the word "urgent" |
| "While we planned the move of [acquired domain]..." | Anchors the note in a project the recipient already approved | Details of the acquisition the recipient may not be cleared to share |
| "...mail back to about [year], attachments mostly intact..." | Gives the year span, which is the answer to the core question, at metadata level | A thread subject, a customer name, or any content from a message |
| "...linked Drive files reliable from about [year]..." | Separates messages from the files they point to, because each has its own survival rule | A guess; if the owner did not know, write "not yet known" |
| "Departed staff accounts are due for [archiving or deletion]..." | States the real event that gives the email its timing | A deadline you invented or any pressure to act |
| "You can decide whether..." | Confirms the recipient's authority and hands over the choice | Any statement that the company qualifies |
| "...SourceX, which licenses approved business data..." | One accurate sentence on what SourceX does | Claims about buyers, prices or demand for mail archives |
| "I have not opened, searched or exported..." | Tells the company its records stayed inside its tenant | Any hint that you hold a sample, screenshot or export |
| "For transparency, I am a SourceX referral partner..." | Discloses your interest and that the reward is funded separately | The reward percentage, or wording that suggests the company pays it |
| "Would a 20-minute call about which years..." | A small, metadata-only ask that is easy to accept or decline | A request for logins, exports, sample threads or a mailbox list |

### Why the date sentence matters

The cleanup date is the one fact in the email that carries real timing, and Google's own documentation explains why. The data migration service copies mail and leaves the source in place, so the copy itself removes nothing from the source. Losses come with the cleanup: deleting a user without transferring their Drive files deletes those files, files in Trash are not transferred, and a deleted user can be restored only for up to 20 days. Messages larger than 25 MB, including attachments, are not migrated at all. You do not need to repeat any of this in the email. You need the date, because it tells the decision-maker how long the choice stays open.

### Filling the placeholders

| Placeholder | Where the value comes from | If nobody knows |
|---|---|---|
| [year] for mail | Owner or admin, from the migration plan | Leave out the clause |
| [year] for linked files | Owner or admin, from when shared drives or file transfers began | Write "not yet known" |
| [archiving or deletion] | The cleanup plan the company approved | Write "a cleanup the company has scheduled" |
| [date the company set] | The same plan, or license end date | Leave out the date; never estimate one |
| [Decision-maker name] | The owner, by name and title | Do not send until you have it |

## What never goes into a domain consolidation email

Some additions feel helpful and quietly turn a clean introduction into a problem.

- **Attachments of any kind.** Not a mailbox list, not a screenshot of the admin console, not a migration report. Each one moves company information outside the tenant without the owner's authority.
- **Mailbox counts you counted yourself.** If the number came from the admin console rather than the owner, leave it out. The owner can share figures with SourceX directly.
- **Names of departed staff.** The point that leavers' files were deleted in a given year is metadata; who those people were is not yours to pass on.
- **Value estimates.** Nobody knows whether a buyer wants a particular company's mail history until SourceX reviews it.
- **Copying the whole IT team.** A licensing conversation belongs to the decision-maker, who can widen the circle if they choose.

The [introduction email builder](/tools/introduction-email-builder) offers alternative openings and the [email preparation worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) helps collect the facts beforehand. If the company is closing rather than consolidating, [what to do with company email when closing a business](/data-types/what-to-do-with-company-email-when-closing-business) covers that situation.

## Who receives it, and what SourceX still has to decide

The recipient must be able to authorize a licensing discussion, and the company should look like a fit before you send. It needs 50+ full-time employees at peak (contractors excluded), a 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.

| Question | What the email can state | What stays unknown until SourceX reviews it |
|---|---|---|
| Which records exist? | Mail, attachments and linked files, by year span | Whether buyers need those record types |
| Who owns them? | The company, as the owner described it | The rights review, including customer and employee terms |
| Who can authorize? | The named decision-maker | Dataset scope and de-identification |
| What happens next? | A metadata-only call, if they want one | Any offer, its terms and any reward |

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. The reward is described on the [rewards page](/rewards): illustrative only, a $250,000 payout to the company for a qualifying completed handoff would mean a $62,500 reward. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The [Google Workspace partner page](/for/google-workspace-partner-referral) sets out the admin-rights boundary in more detail.

## 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 has opted in and you can fill every placeholder from their answers before the old accounts are cleaned up, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you send the email.

## Sources

- https://refer.sourcex.si/terms
- https://support.google.com/a/answer/7032598?hl=en
- https://support.google.com/a/answer/1247799?hl=en
- https://support.google.com/a/answer/1397578?hl=en
