# Domain consolidation archive checklist | SourceX

Canonical: https://refer.sourcex.si/resources/domain-consolidation-archive-context-checklist
Last updated: 2026-11-05

Usually the years whose senders' accounts were kept and whose files were transferred before anyone was deleted; the checklist finds out which those are. Confirm twelve items at three checkpoints: before the domain consolidation is announced, before cutover, and before any old user is removed. Each item names who confirms it and what breaks if it slips, from the inventory of users to oversized messages, file ownership transfers and legal holds. The company sets every date on the countdown; the one fixed clock is Google's 20-day restore limit after a user is deleted.

This checklist sits under the [domain consolidation guide for Google Workspace resellers](/guides/moment-domain-consolidation-google-workspace-resellers). The first answers usually come out of the [timed owner conversation](/resources/domain-consolidation-meeting-agenda); this page carries them through to cleanup day.

## Fix the dates first

Pin down three calendar points, and who set each, before ticking anything. A blank is an answer too.

| Milestone | Usual source | If not set |
|---|---|---|
| Announcement | The integration plan after the acquisition, or the IT project brief | You are early; take milestone one at a normal pace |
| Cutover | The migration runbook and MX switch date | Record who owns the go-live call |
| User removal | A license-reduction plan, a renewal or the old subscription's end | Leave it open; the first item is finding out who decides |

Mark each item **confirmed** (someone with authority said so), **unknown** (with a named person to check) or **at risk** (the current plan loses it). Admin console access does not make an item confirmed; a person's answer does.

The sheet records counts and roles, never content. Nobody searches, opens or exports anything to fill it in.

## Before the consolidation is announced

Nothing has been scheduled for deletion yet, so these questions read as ordinary diligence.

| Confirm | Owner | If skipped |
|---|---|---|
| Every user and team space on the old domain is on the list, including people who already left | Super admin | Former staff drop out of scope without anyone deciding |
| Which years each domain has run on Workspace, and any earlier mail system | Super admin or IT provider | The span starts later than the owner believes |
| How departures were handled in each period: hand over, keep or remove | Operations manager and admin | Years of broken links are discovered after the fact |
| Who owns the company's mail and file history, and any client or employee terms limiting reuse | Owner or counsel | Rights questions arrive after an introduction |

If the acquired firm's ownership of its email is still unsettled, the explainer on [who owns business email after selling a company](/questions/who-owns-business-email-after-selling-company) is the place to start.

## Before cutover

The migration copies; it does not delete. Google's data migration service copies data and leaves the source in place. These items catch what the copy itself will not carry.

| Confirm | Owner | If skipped |
|---|---|---|
| Teams and years that sent messages above 25 MB are identified | Operations manager | Those messages, attachments included, are not migrated, and nobody notices |
| A decision on how oversized messages will be kept: left in source, archived or exported separately | Super admin | The source is deleted with the only copies |
| Files owned by each user are mapped to a transfer target before any account is removed | Super admin | Linked files in old threads stop opening |
| Shared drives are migrated as shared drives, with their member structure | Reseller lead | Files with no single owner become files with no home |

## Before source accounts or the tenant are deleted

The last checkpoint. After deletion there are 20 days to change course, then none.

| Confirm | Owner | If skipped |
|---|---|---|
| Drive files of each user due for deletion have been transferred, and Trash is not relied on | Super admin | Files are deleted with the user; Trash is not transferred |
| Leavers who matter are moved to Archived User licenses instead of deleted | Owner and admin | Their mail and files are gone after the 20-day window |
| Vault holds and retention rules on those users are reviewed before deletion | Counsel or admin | Deleting a user removes holds and retention rules on that user's data |
| Who can authorize a licensing discussion about the retained history | Owner or managing partner | An interested company has nobody able to say yes |

Transfers also have a boundary worth noting: Google does not allow Drive transfers to or from external accounts, so files held by contractors on outside accounts cannot be pulled back this way. If the acquired domain itself changes hands, [transferring a domain after buying a business](/guides/transfer-domain-name-after-buying-a-business) covers that separate step.

## Finished checklist: one firm's read-back

Illustrative. A fictional 175-person environmental consulting firm completed the checklist while folding an acquired lab's domain into its own tenant.

| Item | State | Note |
|---|---|---|
| Accounts in scope | Confirmed | 64 active, 22 suspended leavers, 3 shared drives |
| Span of mail | Confirmed | Acquired domain on Workspace since 2013 |
| Oversized messages | At risk | Lab reports often above 25 MB; decision pending |
| Leavers' files | Partial | Deleted outright before 2018, transferred since |
| Archived User licenses | Unknown | Owner to decide for 22 suspended accounts |
| Ownership | Partial | Two public-sector clients restrict reuse |

That is a metadata description, assembled without opening a mailbox. If the owner wants to explore licensing, the next steps are disclosure, fit and introduction.

Tell the owner you are a SourceX referral partner. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout; nothing is shared unless the company agrees terms. If a qualifying license completes and all payment conditions are met, SourceX may pay you a reward it funds separately and never deducts from the company's payout.

Fit requires 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. Demand, the rights review and any offer remain unknown until SourceX reviews the application.

Sign the Channel Partner Agreement, then send the [domain consolidation introduction email](/resources/domain-consolidation-introduction-email). 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 $400,000 Actual Supplier Payout would mean a $70,000 default reward, payable under the conditions on the [rewards page](/rewards). For other tools in the same project, use the [software consolidation handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-software-consolidation) and the [software consolidation guide](/guides/a-software-consolidation).

## 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 checklist shows years of intact threads will survive cleanup and the owner wants to talk, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before any source accounts are deleted.

## Sources

- 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
- https://support.google.com/vault/answer/11542069?hl=en
- https://refer.sourcex.si/terms
