This script is part of the domain consolidation guide for Google Workspace resellers. Afterwards, the archive context checklist tracks each answer against the project calendar.
People to invite, and the sentence that gets them there
Four seats. More than that and the conversation drifts into DNS records, calendar resources and licensing counts.
| Seat | What they bring | Blocks |
|---|---|---|
| Owner, CEO or managing partner | Has the final word on old accounts and on any licensing conversation | 5 |
| Workspace super admin, in-house or outsourced | Knows the console, past offboarding steps and policy settings | 1, 3, 4 |
| Office or operations manager | Remembers who left when, and how handovers happened | 2, 4 |
| Reseller lead (usually you) | Knows the project plan and the tool's limits | 1, 3 |
Invite line: "Half an hour on how far back our email history really goes, before anything old is cleaned up. Descriptions only, no searching." It signals that the conversation protects the company first, which is true.
Agenda card
Illustrative. A reseller is consolidating a fictional 140-person architecture practice that acquired a smaller firm in 2019. Both domains have run on Google Workspace since 2011.
| Minutes | Block | Question | Who answers |
|---|---|---|---|
| 0-5 | What is moving | Which users and team spaces are on the move list, and is anyone missing from it? | Super admin and reseller |
| 5-11 | Years of mail | Which years of company-owned messages and linked files remain accessible? | Super admin and operations |
| 11-16 | Very large emails | Which teams routinely emailed drawings, scans or photo sets? | Operations manager |
| 16-23 | Departing staff | How were people offboarded in each period, and what cleanup is planned now? | Super admin |
| 23-30 | Owner and decision | Who owns this history, and would the company like to hear how licensing works? | Owner |
Write the answers in a continuity grid as you go: years down the side; messages, attachments and linked files across the top. By minute 23 the grid should have a value or "unknown, {name} to check" in every cell.
How good answers sound, block by block
Minutes 0-5: what is moving
Good: "All 92 active mailboxes, 31 suspended leavers and four shared drives from the acquired domain. The suspended ones were going to be deleted after cutover." The phrase to listen for is "going to be deleted". It sets the timing for block four.
Minutes 5-11: years of mail
Good: "Mail is complete from 2011. Attachments are mostly fine. Links in older threads are reliable only from 2018, when we moved project files to shared drives." That is the span the main guide describes, and it is metadata: written down without opening anything. Google's data migration service copies data rather than moving or deleting it, so on day one the old and new tenants both look complete. The span depends on what happens after.
Minutes 11-16: very large emails
Good: "Site photos and stamped drawing sets often went out by email. Some of those are big." Google documents that the data migration service does not migrate messages, including attachments, larger than 25 MB. In practices that email drawings, those are exactly the threads where the attachment carried the decision. Ask which years and teams sent them, not for examples.
Minutes 16-23: departing staff
Good: "Until 2017 we deleted leavers outright. After that, files were transferred to their manager. The 31 suspended accounts have not been touched." Three documented rules decide this block. If an admin deletes a user without transferring their Drive files, the files are deleted, and files in Trash are not transferred. A deleted user can be restored for up to 20 days, then the data is gone. Deleting a user also removes Vault retention rules and holds on that user's data, and Google suggests an Archived User license to preserve data instead.
Minutes 23-30: owner and decision
Say three things before asking for a decision. SourceX licenses approved business data directly from companies for AI training and evaluation, manages agreement, rights review, data preparation, delivery and payout, and nothing is shared unless the company agrees terms. You are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX funds it separately and it never reduces the company's payout. The consolidation goes ahead either way.
Early exits
| What you hear | Why it ends the meeting | Record |
|---|---|---|
| "The acquired firm's accounts were deleted months ago." | Past the 20-day restore window; that history is gone | Closed; note the surviving span |
| "Almost all our email is with one client under strict confidentiality." | Rights may block any reuse | Note for counsel; stop |
| "We're about 30 people." | Below the 50 full-time baseline | Closed |
| "Not interested." | The owner has declined | Closed; the project carries on |
The decision on the table at minute 30
| Outcome | When | Then |
|---|---|---|
| Introduce now | The grid shows several years of intact threads, the owner is identified and opts in | Send the domain consolidation introduction email |
| Revisit by a date | Account deletions or retention settings are still undecided | Follow up before the scheduled deletion date |
| Stop | The owner declines, or size or confidentiality rules it out | Record why and close |
Before "introduce now", check fit: 50+ full-time employees at peak (contractors excluded), a 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. Unknown until SourceX reviews it: whether those years of threads fit current dataset needs, the rights review on client and employee terms, de-identification and any offer.
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, with one partner per company. Illustrative only: a first qualifying transaction with a USD 100,000 Actual Supplier Payout would mean a USD 55,000 default reward, payable after the conditions on the rewards page are met.
What domain-specific data is explains why years of one firm's threads can matter, the software consolidation handoff checklist covers the other tools in the same project, the Google Workspace partner page sets out the admin-rights boundary, and the first board meeting agenda shows a timed agenda in an investor setting.
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 meeting ends on "introduce now", register as a partner, confirm the company against who qualifies and read the program terms before any source accounts are deleted.