Rights and contracts
M&A archive rights uncertainty: keeping open questions visible after close
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Keep unresolved archive rights visible after an acquisition closes by moving every open diligence question into an exception register before the deal team disbands. Each row names the archive, the entity that holds authority, the missing evidence, an interim restriction on use, an owner, a close condition and a review date. Exceptions close only on evidence, a narrowed scope or a permanent quarantine, never by being forgotten.
License terms
M&A archive rights
Key takeaways
- Diligence ends at signing but its open questions do not; they need a home before the deal team moves on.
- Each exception gets one owner, one interim restriction, one close condition and one review date.
- Authority over a record depends on the transaction form: merger, asset purchase or carve-out each move rights differently.
- Privacy promises and legal holds travel with the archive and are the two exceptions most often lost in integration.
- An exception closes on evidence, a narrower scope or a recorded quarantine, never on the passage of time.
How do you keep unresolved archive rights visible after an acquisition closes?
Move every open rights question from diligence into a register that the integration team owns, before the deal team disbands. Each entry names the archive, the entity with authority over it, the evidence that is missing, a restriction on use until the question is answered, the person responsible, the condition that closes it and the date it will be looked at again.
Diligence rarely resolves everything. Time runs out, the seller cannot find an old agreement, or a question about a shared system is parked for after closing. Those parked questions are the ones that resurface years later, when someone proposes using an old archive for analytics, model training or licensing and nobody remembers why it was flagged.
The register is deliberately small and boring. It does not repeat the diligence report. It carries only the exceptions, and it is reviewed on a fixed schedule until each row is closed.
Why rights questions about archives outlive the deal team
Archive questions survive closing because the people who raised them leave and the records move. Deal counsel and the diligence team hand over to an integration lead, systems are consolidated, and the archive that carried a warning in a data room folder becomes an unlabeled export in a new storage account.
Three patterns cause most of the loss. Disclosure schedule items are written for the purchase agreement, not for the people who will later use the data, so they never reach the system owners. Shared systems in a carve-out keep running under a transition services agreement, and nobody records which records belong to whom when the service ends. And retention or hold notices issued before closing stop being enforced when the administrators who knew about them depart.
A register fixes the handover by making each open question a named piece of work instead of a sentence in a closed folder.
Merger, asset purchase or carve-out: who controls each archive now?
Authority depends on how the deal was structured, so record the transaction form for every archive before deciding anything else. Counsel should confirm the answer for each archive; the patterns below are general and the documents control.
Copyright in archived documents illustrates why the form matters. Under 17 U.S.C. 204(a), a transfer of copyright ownership other than by operation of law is valid only with a signed writing. A merger may carry rights by operation of law, while an asset purchase moves only what the transfer documents convey. The Copyright Office also notes that a nonexclusive grant does not need a written agreement, so old informal permissions may exist that nobody wrote down.
| Transaction form | What usually moves | What to check for each archive | Typical open question |
|---|---|---|---|
| Stock purchase | The target company keeps its records and its obligations; ownership of the company changes | Whether the target's own contracts restrict use after a change of control | Change-of-control or anti-assignment clauses in customer agreements |
| Merger | Assets and obligations of the merged entity pass to the survivor under the governing statute | Which entity now holds the records and which notices and contracts came with them | Records collected under the merged entity's notices being used under the survivor's |
| Asset purchase | Only the assets and contracts listed in the transfer documents | Whether each archive and the rights in it appear on a schedule | Archives physically delivered but never listed, and copies the seller kept |
| Carve-out | The divested business, with shared systems often run by the seller for a period | Which records in shared systems belong to the buyer, and when access ends | Mixed records in a shared ERP, CRM or mailbox tenant |
| Roll-up of add-ons | Several of the above, one per acquired company | Which original entity created each record after archives are combined | Merged archives that no longer show which company the records came from |
The diligence exception and remediation register
Use these ten fields for every exception. They are enough to act on and short enough that someone will keep them current. Where a dataset may later be documented for outside use, the identity fields line up with the Data Provenance Standards, which define fields for the legal entity that issued a dataset, the legal name of the original source when it differs and the location of the license that governs use.
At a glance
The diligence exception and remediation register
Keep the register in a system the integration team already uses, such as a Jira project, a SharePoint list or a tab in the integration workbook, with restricted access, because entries may describe legal exposure.
| Field | What to record | Why it matters |
|---|---|---|
| Exception ID and source | A short ID plus the diligence item, disclosure schedule entry or memo it came from | Links the open question back to what was known at signing |
| Archive and record family | System, export location, record type and date range | Exceptions attach to records, not to whole companies |
| Originating entity and transaction form | The company that created the records and how they changed hands | Sets which contracts and notices govern the records |
| Rights question | One sentence stating what is unknown | A vague question cannot be closed |
| Evidence held and evidence missing | Documents on file and the specific document or confirmation still needed | Turns the question into a retrieval task |
| Interim restriction | What may and may not be done with the records until closure | Stops quiet reuse while the question is open |
| Owner and reviewer | One accountable person and the counsel or privacy reviewer | Shared ownership means no ownership |
| Close condition | The evidence or decision that ends the exception | Defines done before anyone starts |
| Review date | Next date the row is checked, usually monthly then quarterly | Keeps the row alive after integration ends |
| Closure record | Outcome, date, approver and where the evidence is filed | Lets a future user rely on the answer |
Six exception types and the default interim restriction for each
Most archive exceptions fall into six types, and each has a sensible default restriction while it is open. Start from the default and loosen it only with the reviewer's agreement.
| Exception type | Typical missing evidence | Default interim restriction | Usual remediation |
|---|---|---|---|
| Privacy notice gap | The notice in force when the records were collected | Use only for the purposes the original business had | Find archived notice versions; exclude periods with no notice |
| Customer contract restriction | Data-use, confidentiality or assignment clauses for key accounts | No use outside service delivery for those accounts | Contract review by account; consent or exclusion |
| Third-party content | License terms for embedded documents, images or client files | No copying outside the archive | Identify content owners; remove or license |
| Legal hold or preservation duty | Hold notices, litigation list and custodians | No deletion, migration that alters metadata or system shutdown | Counsel confirms release in writing |
| Shared system in a carve-out | Record-level split between buyer and seller | Read-only; no export of mixed records | Agree a split rule and export before service ends |
| Lost provenance in a combined archive | Which acquired company created each record | Treat the whole archive as the most restricted source | Rebuild origin from source system IDs or keep separate |
Do privacy promises follow the archive to the new owner?
Generally yes, and this is the exception most often lost in integration. When the FTC reviewed Facebook's acquisition of WhatsApp in 2014, its staff letter said that, absent affirmative express consent, a company cannot use data in a way materially inconsistent with the promises made when it was collected, and the agency said both companies could violate Section 5 of the FTC Act if those promises were not honored.
California's privacy statute takes a similar line. Civil Code section 1798.140 excludes from the definition of a sale the transfer of personal information as an asset in a merger, acquisition or bankruptcy, provided the information is used consistently with the law, and a new owner that materially changes how it uses or shares the information in a way inconsistent with the promises made at collection must give consumers prior notice.
For records about people in the European Union, GDPR Article 6(4) asks whether a new purpose is compatible with the original one, weighing the link between purposes, the context of collection, the nature of the data, the consequences and the safeguards. Record the notice that applied to each period of the archive as evidence, and keep the interim restriction in place until counsel confirms which uses that notice supports.
Legal holds: the exception that deletion can never close
A legal hold is closed only by counsel releasing it, so it must never be resolved by cleaning up the archive. Integration work such as decommissioning a system, consolidating mailboxes or running a retention policy across a new tenant can destroy held records without anyone intending it.
Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation and is lost because a party failed to take reasonable steps, where it cannot be restored or replaced. Carry every hold from the target into the register with its custodians and systems, and require the owner of any decommissioning task to check the register first.
Holds also block a quieter kind of loss: migrations that change metadata such as authors and dates. If a held archive must move, counsel and the IT owner should agree how to preserve it in a form that keeps the original metadata.
Worked example (illustrative): three open exceptions from a distribution carve-out
This example is illustrative. A buyer acquires the industrial parts division of a larger distributor. The division's order history sits in the seller's ERP, which the seller runs for the buyer under a twelve-month transition services agreement. Diligence closed with three open items, which become register rows on the day of closing.
| ID and archive | Rights question | Interim restriction | Close condition and review |
|---|---|---|---|
| EX-01: ERP order history, 2017 to closing | Which order lines belong to the division when customers bought from both divisions? | Read-only access; no exports of mixed customers | Split rule signed by both parties and export verified before month ten; reviewed monthly |
| EX-02: customer portal messages, 2019 to 2021 | Which privacy notice applied to portal users before 2021? | Use only for answering current customers | Archived notice located, or period excluded from any new use; reviewed quarterly |
| EX-03: engineering drawings from OEM customers | Do supply agreements let the division keep or reuse customer drawings? | No copying outside the archive | Contract review of the top accounts by drawing count, with the remainder excluded; reviewed quarterly |
| Register status at month six | EX-01 open, EX-02 closed by exclusion, EX-03 narrowed | Restrictions unchanged for open rows | Next full review at month nine before the services agreement ends |
What do you do with an exception that will not close?
Some exceptions never get the evidence they need: the old notice is gone, the counterparty has dissolved or the archive's origin cannot be rebuilt. Do not leave these open indefinitely. Choose one of three recorded outcomes and have the reviewer sign it.
Narrow the scope by removing the uncertain period, accounts or fields so the rest of the archive can close. Quarantine permanently by keeping the records only for the purposes the original business had, with access limited and the reason recorded. Or escalate to specialist review when the records are large, sensitive or commercially important enough to justify outside counsel, a privacy specialist or a forensic rebuild of provenance.
Stop and escalate immediately if a held archive is scheduled for shutdown, if records about children, health or finances turn up in an archive flagged for broad use, or if anyone proposes using an open-exception archive outside the company.
What a closed register makes possible later
A register with every row closed or quarantined is what lets a company later say, with evidence, which acquired archives it may use for analytics, AI development or licensing. Without it, a future opportunity starts by repeating diligence on records whose original custodians are long gone.
If the acquirer later decides to license selected archives, SourceX runs rights review and contracting along with preparation and delivery, and no record moves until the company has approved the scope and terms and signed. Closed exceptions with filed evidence shorten that review considerably, and quarantined archives simply stay out of scope. Eligibility is checked first with a short company assessment that needs no data upload.
Frequently asked questions
What is a diligence exception register?
It is a short list of the rights and data questions that diligence did not resolve, carried forward after closing. Each entry has an owner, an interim restriction on use, a close condition and a review date. It differs from the diligence report because it holds only open items and is maintained until each one is closed.
Who should own archive rights exceptions after closing?
The integration lead owns the register, and each row has one accountable person, usually the system owner for the archive, with counsel or the privacy lead as reviewer. Deal counsel should hand over each item in writing before the deal team disbands.
Does a new privacy policy after the acquisition cover the old records?
Usually not on its own. The FTC has said that data cannot be used in a way materially inconsistent with the promises made when it was collected without affirmative express consent, and California requires prior notice for materially changed uses after a merger. Counsel should map each period of the archive to the notice in force at collection.
Can we delete an archive to close a rights exception?
Only after counsel confirms that no legal hold, retention duty or contract requires keeping it. Deletion that destroys records subject to a preservation duty can create serious litigation consequences. Record the release and the deletion in the register.
How long should an exception stay open?
Until it closes on evidence, is narrowed, or is recorded as a permanent quarantine. A practical rule is to force one of those outcomes by the end of the first year after closing, or before any transition services agreement ends, whichever comes first.
Sources
- FTC staff said that, absent affirmative express consent, a company cannot use data in a manner materially inconsistent with the promises made when the data was collected, including after an acquisition. Source
- The FTC said that if WhatsApp failed to honor its privacy promises after the acquisition, both companies could be in violation of Section 5 of the FTC Act. Source
- California Civil Code section 1798.140 excludes from a sale a transfer of personal information as an asset in a merger, acquisition or bankruptcy if used consistently with the law, and requires prior notice when the new owner materially changes use inconsistently with promises made at collection. Source
- GDPR Article 6(4) sets out factors for judging whether processing for a new purpose is compatible with the original purpose. Source
- Under 17 U.S.C. 204(a), a transfer of copyright ownership other than by operation of law is not valid unless it is in a writing signed by the owner of the rights conveyed or an authorized agent. Source
- Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved for litigation and is lost because a party failed to take reasonable steps, where it cannot be restored or replaced. Source
- The Data Provenance Standards define metadata for the issuing legal entity, the original source's legal name when it differs, and the location of the license governing use. Source
- The Copyright Office's Circular 1 explains that transfers of copyright generally must be in writing and signed, while granting a right on a nonexclusive basis does not require a written agreement. Source
See if your company qualifies
A short company assessment. No data uploads are needed.