Post-merger tenant control vs data ownership: a chain-of-title worksheet for each inherited system

Short answer

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.

Visual briefFull-size diagram
Two parallel tracks for one inherited tenant: a control track from tenant creator to current admin that completes at once, and a title track from records creator through the deal document to the licensing signer, where one link stays amber until third-party content is resolved.
Illustrative worksheet for a fictional acquired firm. Admin control can be complete while the title chain is still open.

This guide is part of system decommissioning after an 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 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

FieldWhat to recordSource document
Tenant or account nameThe system and instance, such as "add-on help desk, EU instance"Vendor admin console, as read by IT
Subscribing entityThe legal entity on the vendor contract todayVendor order form or invoice
Admin holdersRoles, not names: "platform IT, two global admins"Access review
Basis for controlOwnership after migration, a transition services agreement or a temporary delegationIntegration plan or agreement
Control end dateWhen a transition arrangement or delegation lapsesThe agreement's term clause

Part B: chain of title

FieldWhat to recordSource document
Records created byThe entity whose staff generated the records, and the yearsCompany history, integration lead
Deal structureStock purchase, asset purchase or mergerPurchase agreement
Transfer languageWhether the records, systems or databases are named, included or excludedPurchase agreement schedules
Post-close assignmentsAny later intercompany transfer of records or IPBoard minutes, assignment deeds
Title holder todayThe entity counsel believes holds the recordsDeal counsel's note

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

Part C: content inside the tenant

FieldWhat to recordWhy it matters
Client-owned materialDeliverables or documents assigned to clients by contractThe company may hold them without the right to license them
Customer-supplied contentAttachments, files or data customers uploadedCustomer terms may limit reuse
Vendor-licensed dataPurchased lists or datasetsMany licenses forbid relicensing
Personal dataCategories only, such as employee names or customer contactsDrives de-identification in the rights review

Part D: authority

FieldWhat to record
Who can authorize a licensing discussionThe CEO of the title-holding entity, such as the acquired company's CEO, with the platform's general counsel advising
Who must also consentA seller still running the system, a lender or a client with restrictive terms
Counsel sign-offDate 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:

PartFindingStatus
A: controlPlatform IT holds both admin roles; the platform pays the subscriptionComplete
B: titleRecords created by the acquired firm's staff since 2014; stock purchase left them with the acquired entity; no later transferTitle with acquired entity
C: contentDrawings and reports for public-sector clients, several assigned to clients by contract; consultant submittals uploaded by third partiesOpen: client-assigned and third-party files to exclude
D: authorityAcquired firm's CEO, with platform general counsel advisingNamed

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

SituationControl sits withTitle usually followsWhat to check
Seller still runs the system under a transition agreementSellerAcquired entity, if the agreement says soExport rights before the term ends; see exiting a transition services agreement
Mailboxes migrated into the acquirer's tenantAcquirer ITEntity whose staff created themWhether only mail moved, leaving files and chat behind
Asset purchase that excluded some systemsAcquirer, if it took the tenant anywaySeller, for excluded recordsThe excluded-assets schedule
Client portal hosting client uploadsAcquirer ITClients, for their contentClient 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. Partners never take exports, admin credentials or sample files. The post-merger integration checklist and the page for post-merger integration consultants place this worksheet in the wider integration plan; more rights topics are on the guides hub.

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, check that entity against who qualifies and read the program terms before introducing the Part D contact.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

If the acquirer pays the subscription, does it own the tenant's content?

Paying for the service makes it the customer of the vendor, not the creator or owner of every record inside. Title still follows who created the records, what the deal transferred and what customer contracts say.

Can a partner fill in this worksheet?

No. The integration lead and deal counsel fill it in from documents the company holds. The partner asks the questions and hears the final status in words.

What if the tenant was created by the seller's parent company?

Then both tracks need care. The admin track may run through a transition agreement, and the title track depends on whether the purchase agreement transferred the records or left them with the parent. Mark it unresolved until counsel confirms.

Sources

  1. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…
  2. learn.microsoft.com/en-us/entra/identity/role-based-access-contr…
  3. learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-m…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment