Skip to content

Rights and contracts

Carve-out dataset separation: drawing a boundary you can defend

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

A carve-out dataset boundary is defensible when every record class passes four documented tests: the records were created by or for the carved-out business, they sit in a system the licensing entity controls or may extract from, the customer relationship and contract terms traveled with them, and privacy notices and separation documents permit the new use. Record the evidence per class in a boundary memo and hold anything contested.

Document stack

Carve out dataset separation

This page covers carve-out dataset separation: drawing a boundary you can defend.Illustrative

Key takeaways

  • The deal perimeter is drawn for operations; the dataset boundary must hold at the level of each record class.
  • Four tests decide inclusion: entity of origin, system control, customer and contract transfer, and privacy and licensing permission.
  • Promises made when data was collected survive the transaction, so map each record class to the notice version in force at collection.
  • Shared customers and residual copies at the parent are where both companies most often claim the same history.
  • A versioned boundary memo with evidence per class shortens a buyer's rights review and keeps contested records out.

How do you define and evidence the boundary of a carve-out dataset?

Define the boundary record class by record class, not by the deal perimeter. A record belongs in a carve-out dataset only when four tests pass and each has a document behind it: the record was created by or for the carved-out business, it sits in a system or partition the licensing entity controls or may extract from, the customer or counterparty relationship and its contract terms traveled with it, and the privacy and licensing permissions allow the new use.

Write the result as a boundary memo with one row per record class and the evidence for each test. Any class that fails a test is excluded or held for a decision, and any class where both the parent and the new company could claim the same records gets an explicit rule about who may license it.

This is general information for planning, not legal advice. Separation agreements, privacy notices and customer contracts differ, and counsel should review the specific documents before any record class is licensed.

Why the transaction perimeter is not the dataset boundary

A carve-out agreement defines the business being sold and lists transferred assets, assumed contracts and shared services. That perimeter is drawn for operations and accounting, and it rarely says which historical records in a shared ERP, CRM or helpdesk belong to whom. Customers served by both units, staff who worked across both, and back-office functions run centrally all produce records that sit on the line.

The dataset boundary is narrower and stricter. It must hold at the level of individual record classes, survive a buyer's rights review, and keep working after the transition services period ends. A record class can be inside the deal perimeter and still fail as licensable data, for example because the privacy notice under which it was collected did not contemplate the new use.

The UK Information Commissioner's Office makes the same point for personal data: when a merger, acquisition or restructuring moves data to a new or additional controller, data sharing should be considered as part of due diligence, including the purposes for which the data was originally collected and the lawful basis for sharing it.

The entity, system, customer and rights separation worksheet

Fill one worksheet per record class, such as sales orders, service tickets, field inspection reports or supplier invoices. Each row is a test; the record class passes only when every row has evidence named in the third column. Leave a row open rather than guessing, and route open rows to the person named in the separation agreement as owning that decision.

The entity, system, customer and rights separation worksheet
TestQuestion to answerEvidence that settles itFails when
Entity of originWhich legal entity or business unit created the records?Entity, company code or cost-center field on each record, mapped to the business definitionRecords carry no entity field and the unit shared staff and systems
Business definitionDoes the separation agreement's definition of the business cover this activity?Clause and schedule references in the separation or purchase agreementThe activity is a shared service retained by the parent
System controlWho controls the system or partition the records sit in?System inventory, transferred-asset schedule, transition services scheduleRecords stay in a parent system with no extraction right after the services end
Partition ruleHow are records separated inside a shared instance?Written filter on fields such as company code, branch or queue, with countsThe split depends on free text or a person's judgment
Customer and contractDid the customer contract and its data terms transfer?Assigned contracts list, consent to assignment, data clausesThe contract stayed with the parent or bars assignment
Shared customersWhich unit's records describe a customer both served?Allocation rule by ship-from site, product line or billing entityThe same history is claimed by both companies
Privacy basisDo the notices and promises at collection allow the planned use?Privacy notice versions by date, opt-out and consent recordsThe notice limits use to service delivery or forbids sharing
Licensing permissionMay this entity license the records to third parties for AI?Separation, license-back and data-sharing clauses naming AI training or analyticsThe agreement is silent and the other party contests it
Residual copiesWhat copies remain with the other party, and under what terms?Return or destruction clause, sanitization certificate, retained-copy licenseBoth parties hold full copies with no rule on licensing

Who has authority over each record after closing?

Authority usually follows three documents: the separation or purchase agreement for ownership, the transition services agreement for access and handling during the transition, and any license-back or data-sharing agreement for continued use. Read them together and record, for each record class, which document grants the new company control and which limits it.

During a transition services period the parent often keeps operating systems on the new company's behalf. Where EU or UK data protection law applies and the parent acts as a processor, Article 28 of the GDPR requires the processing contract to say that the processor handles personal data only on the controller's documented instructions. A parent in that role cannot treat records it processes for the new company as its own licensing inventory, and the new company should not assume that access under the services agreement equals a right to extract full history.

Bankruptcy carve-outs add a court layer. Under 11 U.S.C. 363(b)(1), if a debtor's privacy policy in effect when the case began prohibits transferring personally identifiable information to unaffiliated persons, the trustee may sell or lease that information only consistently with the policy or after a court appoints a consumer privacy ombudsman and approves the sale following a hearing.

Privacy promises travel with the records

A change of owner does not reset the promises made when data was collected. In its 2014 letter on the Facebook and WhatsApp acquisition, FTC staff said that using acquired data in a way materially inconsistent with the promises made at collection requires consumers' affirmative consent first. In 2024 FTC technology staff warned that adopting more permissive data practices, such as using data for AI training, and disclosing that only through a surreptitious, retroactive change to terms or a privacy policy may be unfair or deceptive.

California's privacy law treats a transfer in a merger, acquisition, bankruptcy or similar transaction, where the recipient assumes control of all or part of the business, as outside the definition of a sale, provided the information is used or shared consistently with the law. If the recipient later materially alters how it uses or shares the information in a way materially inconsistent with the promises made at collection, it must give prior notice.

For the worksheet, this means the privacy-basis row needs the notice version in force when each record was collected, not the notice the new company publishes after closing. Records collected under different notice versions may need to be split into separate classes.

Illustrative worked scenario: a distribution division leaves a shared ERP

The following case is illustrative and invented to show how the worksheet is used; the counts are examples, not observations. A parent sells its industrial distribution division. Both units ran one ERP, one CRM and one helpdesk, and the division wants to license order and service history for AI after closing.

  • Illustrative outcome: roughly 60 percent of the order history passes without further work, about 25 percent passes after the shared-customer split, and the remainder is held or excluded.
  • The decision that moved the most records was the shared-customer allocation rule, not any privacy question.
Illustrative worked scenario: a distribution division leaves a shared ERP
Record classEntity and system testCustomer and rights testVerdict
Orders shipped from the division's own branchesCompany code on every order; extraction right in the services scheduleContracts assigned; notice allows analyticsInclude
Orders for customers both units servedCompany code present but customers sharedAllocation by ship-from branch agreed in writingInclude after split
Central accounts payable invoicesCreated by the parent's shared service centerSupplier contracts stayed with the parentExclude
CRM notes by a shared sales teamNo entity field; authors worked for both unitsNotes mention parent-only customersHold pending a field-level rule
Helpdesk tickets from the division's queueQueue ID maps cleanly to the divisionNotice version changed during the periodInclude, split by notice version
Records still in the parent's backup archiveParent controls the mediaDestruction clause unsignedExclude until the residual-copy rule is agreed

Which assumption flips a record class from in to out?

Three assumptions carry most of the weight, and the boundary memo should show each one with the evidence for it and the effect of reversing it. When a reviewer challenges the memo, these are the rows they will test first.

At a glance

Which assumption flips a record class from in to out

  • The business definition: if a clause defines the business by product line rather than by legal entity, records created by shared staff may move in or out wholesale. Quote the clause in the memo.
  • The shared-customer rule: allocation by billing entity, ship-from site or product line can produce very different splits. Pick one rule, apply it mechanically, and show the counts it produced.
  • Licensing permission under silence: if the separation documents do not mention licensing records to third parties, assume the class is held until both parties sign a short data-use addendum, rather than reading silence as consent.
  • Show uncertainty by marking each class pass, conditional or fail, and listing the single document that would change a conditional verdict.

Residual copies and the risk of licensing the same history twice

After closing, the parent often still holds backups, data warehouse extracts and archived exports that contain the division's records. If both companies hold full copies with no rule, both may try to license the same history, and a buyer's review will find the conflict.

Settle it in writing: either the parent returns or destroys its copies, or it keeps them under a license that names permitted uses and excludes third-party licensing. Where destruction is chosen, NIST SP 800-88 describes the clear, purge and destroy methods of media sanitization, from logical overwriting through techniques that make recovery infeasible with state-of-the-art laboratory methods. A sanitization certificate, or a signed retained-copy license, becomes evidence in the residual-copies row of the worksheet.

If the new company is the one licensing, it should also record what it received: the extraction date, the filter used, and record counts per class, so a buyer can see that the delivered dataset matches the boundary memo.

What goes in the boundary evidence pack?

Keep the pack versioned. Transaction scope, integration ownership, systems, consents and contract harmonization all change after closing, and each change can move a record class across the line.

  • The boundary memo: one row per record class with the verdict and the evidence reference for each test.
  • Extracts of the separation agreement, transition services schedules and any license-back clauses that the memo cites.
  • The system inventory with control and extraction rights per system, and the partition filters with record counts.
  • Assigned-contracts list and the shared-customer allocation rule, with counts before and after the split.
  • Privacy notice versions by effective date and the mapping of record classes to notice versions.
  • Residual-copy decisions: sanitization certificates or retained-copy licenses.
  • A log of open questions, the person who owns each, and the date each was closed.

Licensing records from a carved-out business

A carved-out company that has drawn its boundary can treat the in-scope classes like any other licensable records. SourceX handles sourcing and qualification, rights review, contracting, preparation and delivery for the operational data it licenses directly from businesses, and a boundary memo shortens the rights review because the hardest questions are already answered.

The company approves the scope and terms and signs the agreement before any data is delivered, so held or contested classes simply stay out. A carved-out company can check whether it qualifies through a brief assessment, before sharing any records.

Frequently asked questions

Who owns shared customer records after a carve-out?

Whatever the separation documents say, and they are often silent at the record level. Agree a mechanical allocation rule, such as ship-from site or billing entity, apply it to every shared customer, and record the counts it produced before either company licenses the history.

Can the parent still license copies of the division's records it keeps?

Only if a written agreement allows it. Without a return, destruction or retained-copy clause, both companies may claim the same history, so settle residual copies before either side offers the data.

Is transferring customer data in a carve-out a sale under California law?

California's privacy law excludes from the definition of a sale a transfer in a merger, acquisition or similar transaction where the recipient takes control of all or part of the business, provided the data is used consistently with the law. A later material change of use that conflicts with the original promises requires prior notice, so counsel should review the specific facts.

Does de-identification solve the boundary problem?

No. De-identification addresses privacy risk in the delivered data, but it does not create ownership or a right to license. A record class that fails the entity, system or licensing-permission test stays out even after de-identification.

What if the transition services agreement is still running?

Treat records in the parent's systems as accessible for operations only until the services schedule grants an extraction right. Plan the extraction, with filters and counts, before the services end, because history left behind is often lost at exit.

Sources

  • The ICO says that when a merger, acquisition or restructuring moves data to a new or additional controller, data sharing should be part of due diligence, including original purposes and lawful basis. Source
  • GDPR Article 28(3)(a) requires a processor contract to provide that the processor handles personal data only on the controller's documented instructions. Source
  • 11 U.S.C. 363(b)(1) limits a trustee's sale of personally identifiable information when the debtor's privacy policy prohibits transfer, unless consistent with the policy or approved after a consumer privacy ombudsman and hearing. Source
  • FTC staff told Facebook and WhatsApp that using acquired data in a way materially inconsistent with promises made at collection requires affirmative consent. Source
  • FTC staff warned that adopting more permissive practices such as AI training through a surreptitious, retroactive change to terms or a privacy policy may be unfair or deceptive. Source
  • The CCPA excludes from a sale a transfer in a merger, acquisition or similar transaction, provided use stays consistent with the law, and requires prior notice of materially inconsistent changes. Source
  • NIST SP 800-88 describes clear, purge and destroy as media sanitization methods, with purge and destroy making recovery infeasible using state-of-the-art laboratory techniques. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies