# Domain consolidation: which years survive | SourceX

Canonical: https://refer.sourcex.si/guides/moment-domain-consolidation-google-workspace-resellers
Last updated: 2026-11-04

Ask the owner which years of company-owned mail threads, attachments and linked Drive files will still open after the consolidation, and who decides. In a Google Workspace domain consolidation the messages are usually copied safely; what breaks is the context around them: oversized messages that do not migrate, Drive links whose owners were deleted, and accounts removed before anyone checked. A reseller can map those years from metadata, then introduce the owner to SourceX if the company wants to explore licensing.

## Which years of company-owned messages and linked files remain accessible?

That exact question is the opening. Ask it once the consolidation plan is agreed and before any account cleanup is scheduled, and expect the honest answer to be "we are not sure".

A thread is more than its messages. A 2017 customer escalation might be one email chain, a PDF attached to the third message, and a link to a shared spreadsheet owned by an account manager who left in 2020. After consolidation, each of those three parts has its own survival rule:

| Part of the thread | What decides whether it survives | Documented behavior |
|---|---|---|
| Message body and headers | Whether the mailbox was included in the migration | Google's data migration service copies data and leaves the source in place |
| Attachment inside the message | Message size | Messages, including attachments, larger than 25 MB are not migrated |
| Linked Drive file | Whether its owner's account still exists, or its files were transferred | Deleting a user without transferring Drive files deletes them; Trash is not transferred |
| Departed user's whole mailbox and Drive | Archived or deleted | A deleted user can be restored only for 20 days, and deletion removes Vault holds |

So the useful answer is not a yes or no, but a span: "mail from 2014 onward, attachments mostly intact, linked files reliable only from 2019, when we started using shared drives." That sentence is metadata. You can write it down without opening anything.

### Illustrative continuity map

Illustrative. A fictional 160-person engineering consultancy is consolidating an acquired firm's domain into its own Workspace tenant.

| Years | Messages | Attachments | Linked files | Note for SourceX |
|---|---|---|---|---|
| 2012 to 2015 | Acquired firm's mailboxes, copied | Large drawings above 25 MB skipped | Personal Drives of 14 departed staff deleted in 2016 | Threads intact, links broken |
| 2016 to 2019 | Copied | Mostly intact | Transferred to a manager on each departure | Threads and most links intact |
| 2020 onward | Copied | Mostly intact | Shared drives, so no single owner | Best continuity |

Every cell came from the owner and their admin. The reseller's contribution is the structure, not the content. A map like this tells SourceX, in one glance, which years carry whole conversations with their attachments and referenced files, and which carry messages whose context has already gone.

## Why is attachment and thread continuity easy to overlook?

Because the consolidation is judged a success when mail flows and users can sign in. The project plan tracks mailboxes copied, aliases set, calendars moved and DNS records switched. Nobody checks whether a link inside a 2016 message still opens, because nobody needs that link this week.

The losses also arrive late and quietly. Google's migration service copies rather than moves, so on cutover day everything looks intact in both tenants. The damage comes in the cleanup that follows: suspended accounts of departed staff are deleted to save licenses, files that were never transferred go with them, and Vault holds attached to those users are removed at the same moment. Google's own help suggests an Archived User license as the way to preserve a departed user's data instead of deleting it, but that choice has to be made by someone who knows the history matters. Twenty days later, the restore window has closed.

Oversized messages are the other blind spot. Engineering drawings, scanned contracts and site photos often sit in messages above the 25 MB limit, and those are exactly the threads where the attachment was the point.

## Four metadata questions for the owner

Stay at metadata level: what exists, how much, how long, which system and who owns it. These four questions, asked after the main one, give you the span:

1. **Which accounts are in scope?** Are all mailboxes and shared drives from the source tenant listed, including suspended accounts of people who left?
2. **What happened to leavers' files?** In earlier years, were departing staff's Drive files transferred, their accounts archived, or the accounts deleted?
3. **What is scheduled to be removed?** Is there a date for deleting source accounts or ending the source tenant's subscription, and does any Vault hold or retention rule cover those accounts?
4. **Whose history is it?** Who owns the company's mail and file history, and do customer contracts or employee commitments limit how it can be used?

Write the answers in the continuity map format: years down the side, messages, attachments and linked files across the top. Workspace admin rights are not permission to look; do not open, search or export anything to check an answer. If the cleanup already happened years ago, write that down as the answer. For a handoff list covering other tools in the same consolidation, use the [software consolidation handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-software-consolidation), and if the acquired domain itself is changing hands, see [transferring a domain after buying a business](/guides/transfer-domain-name-after-buying-a-business).

## How do you disclose the reward and get the owner's permission?

Ask permission before mentioning SourceX, and disclose your interest in the same sentence. For example: "There is a separate question of whether that history has value outside the company. May I mention one option? I am a referral partner, so I may receive a reward if it leads anywhere."

If the owner says yes, explain plainly that SourceX licenses approved business data directly from companies for AI training and evaluation, that the company keeps ownership, that nothing is binding until it agrees to terms, and that any reward to you is funded separately by SourceX and never reduces the company's payout. If the owner says no, the consolidation carries on unchanged, and the archive question was still worth raising before accounts were deleted.

State the reward exactly. The default on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap; further qualifying transactions agreed within 12 months of the first Closing pay 15%. Illustrative only: a USD 200,000 payout to the company would mean a USD 60,000 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, as the [rewards page](/rewards) explains.

## Does the company qualify, and who can authorize a licensing discussion?

The company 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 a reseller can usually confirm | What stays unknown until SourceX reviews |
|---|---|---|
| Which records exist? | Mail, attachments and Drive files, by year span | Whether buyers need those record types |
| Who owns them? | The company, subject to customer and employee terms | The rights review result |
| Who can authorize? | Owner, CEO or a designated officer | Dataset scope and de-identification |
| How much and how long? | Mailbox count and years covered | The company's offer and any reward |

The [Google Workspace partner page](/for/google-workspace-partner-referral) sets out the admin-rights boundary, the [Drive projects guide](/guides/how-google-workspace-partners-spot-referral-opportunities-during-google-drive-projects) covers a related moment, and [what domain-specific data is](/proof/what-is-domain-specific-data) explains why years of one company's threads can matter. Other partner roles are listed in the [partner hub](/for).

Sign the Channel Partner Agreement before you submit the introduction. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner credited per company.

## Go deeper on domain consolidation records

- [Domain consolidation introduction email](/resources/domain-consolidation-introduction-email): a ready-to-adapt email for introducing an opted-in owner and their mail and file history to SourceX.
- [Domain consolidation meeting agenda](/resources/domain-consolidation-meeting-agenda): a timed agenda for the owner conversation about which years remain accessible.
- [Domain consolidation archive context checklist](/resources/domain-consolidation-archive-context-checklist): a checklist of scope, deletion dates and retention settings to confirm before cleanup.

## 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 can name which years of mail and linked files survive the consolidation and wants to explore licensing before accounts are deleted, [register as a partner](/register), confirm fit on [who qualifies](/who-qualifies), and read the [program terms](/terms) first.

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