# Tenant control vs data ownership worksheet | SourceX

Canonical: https://refer.sourcex.si/guides/post-merger-tenant-data-ownership-referral
Last updated: 2026-11-04

No. Controlling a tenant means holding its admin roles: the power to export, migrate, retain or delete what is stored there. Ownership is a separate chain: who created the records, what the deal documents transferred, and whose content sits inside, such as client deliverables, customer attachments or vendor-licensed data. After a merger the two often diverge. Before anyone discusses licensing, the company should trace both for each inherited system and record where they part.

This guide is part of [system decommissioning after an acquisition](/guides/system-decommissioning-after-acquisition), which covers what to export before legacy systems are switched off. Here the job is narrower: a company-authorized worksheet that separates tenant control from chain of title, one system at a time, so an introducer knows who can actually say yes.

## Two tracks that answer different questions

The control track answers "who can act on this tenant?". In Microsoft 365, for example, a user with the Global Administrator role has access to all administrative features in Microsoft Entra ID and in services that use Entra identities, including Exchange Online and SharePoint Online. That is real power over the data, and it sits with whichever account the integration team assigned.

The title track answers "who may license what is in it?". Data protection guidance draws a similar line between running a service and deciding what happens to the data it holds: the UK Information Commissioner's Office explains that an organization using a cloud service to store and analyze its data remains the controller, while the provider acts as its processor. Controller status is not ownership, but inside a merger a comparable logic applies one level down. An IT team that administers an add-on's tenant, during a transition period or after a migration, gains control, not title.

Migration makes the gap easy to miss. Microsoft's cross-tenant mailbox migration, designed for mergers and acquisitions, moves Exchange Online mailboxes into the acquirer's tenant and moves mailbox data only. Afterwards the email lives in a new tenant under new admins, yet it was created by the add-on's staff under the add-on's client relationships. The [Microsoft 365 tenant-to-tenant migration guide](/guides/microsoft-365-tenant-to-tenant-migration-after-acquisition) covers the mechanics.

## The worksheet, part by part

The company fills in one sheet per inherited system. Every field is metadata or a document reference; no records are opened.

### Part A: tenant control

| Field | What to record | Source document |
|---|---|---|
| Tenant or account name | The system and instance, such as "add-on help desk, EU instance" | Vendor admin console, as read by IT |
| Subscribing entity | The legal entity on the vendor contract today | Vendor order form or invoice |
| Admin holders | Roles, not names: "platform IT, two global admins" | Access review |
| Basis for control | Ownership after migration, a transition services agreement or a temporary delegation | Integration plan or agreement |
| Control end date | When a transition arrangement or delegation lapses | The agreement's term clause |

### Part B: chain of title

| Field | What to record | Source document |
|---|---|---|
| Records created by | The entity whose staff generated the records, and the years | Company history, integration lead |
| Deal structure | Stock purchase, asset purchase or merger | Purchase agreement |
| Transfer language | Whether the records, systems or databases are named, included or excluded | Purchase agreement schedules |
| Post-close assignments | Any later intercompany transfer of records or IP | Board minutes, assignment deeds |
| Title holder today | The entity counsel believes holds the records | Deal counsel's note |

Stock and asset deals move records differently; [asset vs stock purchase records ownership](/questions/asset-purchase-vs-stock-purchase-records-ownership) explains why, and [chain of title for training data](/questions/chain-of-title-training-data) lists what a data buyer expects to see.

### Part C: content inside the tenant

| Field | What to record | Why it matters |
|---|---|---|
| Client-owned material | Deliverables or documents assigned to clients by contract | The company may hold them without the right to license them |
| Customer-supplied content | Attachments, files or data customers uploaded | Customer terms may limit reuse |
| Vendor-licensed data | Purchased lists or datasets | Many licenses forbid relicensing |
| Personal data | Categories only, such as employee names or customer contacts | Drives de-identification in the rights review |

### Part D: authority

| Field | What to record |
|---|---|
| Who can authorize a licensing discussion | The CEO of the title-holding entity, such as the acquired company's CEO, with the platform's general counsel advising |
| Who must also consent | A seller still running the system, a lender or a client with restrictive terms |
| Counsel sign-off | Date deal counsel reviewed Parts B and C |

## A completed example

Illustrative and fictional. A platform company acquired a 240-person architecture and engineering firm by stock purchase. The firm's project collaboration tenant is administered by platform IT after migration. The integration lead and deal counsel complete the sheet:

| Part | Finding | Status |
|---|---|---|
| A: control | Platform IT holds both admin roles; the platform pays the subscription | Complete |
| B: title | Records created by the acquired firm's staff since 2014; stock purchase left them with the acquired entity; no later transfer | Title with acquired entity |
| C: content | Drawings and reports for public-sector clients, several assigned to clients by contract; consultant submittals uploaded by third parties | Open: client-assigned and third-party files to exclude |
| D: authority | Acquired firm's CEO, with platform general counsel advising | Named |

Reading it: control is complete and says nothing about licensing. Title sits with the acquired entity, which is the company to introduce, not the platform. Part C keeps one link open, so any discussion would start from internal project records, with client-assigned deliverables and third-party submittals excluded unless the rights review finds otherwise.

## Where the two tracks usually part ways

| Situation | Control sits with | Title usually follows | What to check |
|---|---|---|---|
| Seller still runs the system under a transition agreement | Seller | Acquired entity, if the agreement says so | Export rights before the term ends; see [exiting a transition services agreement](/guides/transition-services-agreement-exit-data) |
| Mailboxes migrated into the acquirer's tenant | Acquirer IT | Entity whose staff created them | Whether only mail moved, leaving files and chat behind |
| Asset purchase that excluded some systems | Acquirer, if it took the tenant anyway | Seller, for excluded records | The excluded-assets schedule |
| Client portal hosting client uploads | Acquirer IT | Clients, for their content | Client terms on reuse |

## Qualification and limits

Records: closed operational history in systems where Parts B to D are filled in. Ownership: the entity named in Part B, subject to SourceX's rights review. Authority: the role in Part D. The referred company has to meet the baseline on its own: 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.

Unknown until SourceX reviews it: whether open Part C items can be excluded cleanly, the de-identification needed, buyer interest and whether the platform and its add-on count as one referred company or two under the [terms](/terms). Partners never take exports, admin credentials or sample files. The [post-merger integration checklist](/resources/post-merger-integration-checklist) and the page for [post-merger integration consultants](/for/post-merger-integration-consultant-referral) place this worksheet in the wider integration plan; more rights topics are on the [guides hub](/guides).

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

When a worksheet shows title with a named entity and an authorized signer, [register as a partner](/register), check that entity against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing the Part D contact.

## Sources

- https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/artificial-intelligence/guidance-on-ai-and-data-protection/what-are-the-accountability-and-governance-implications-of-ai/
- https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference
- https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-mailbox-migration?view=o365-worldwide
- https://refer.sourcex.si/terms
