Skip to content

Rights and contracts

Acquired archive rights evidence when assignment papers are missing

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

When an acquired archive's assignment documents are missing, the first question is not whether to license the archive but which records depend on the missing link. Trace each record set to the transfer it relies on, ask counsel whether surviving evidence closes the gap, and pause only the dependent scope. Write the pause as a rerunnable exclusion rule, applied before de-identification, so excluded records never reach delivery.

License terms

Acquired archive rights

This page covers acquired archive rights evidence when assignment papers are missing.Illustrative

Key takeaways

  • A missing assignment pauses only the records whose title passes through it; records the acquirer created itself usually do not depend on it, though copied or migrated content can.
  • Lost paper and a transfer that was never documented are different gaps: one may be proved by other evidence, the other may need a new signed instrument or an exclusion.
  • U.S. copyright law requires a signed writing for a transfer other than by operation of law, while a statutory merger moves property without one, so deal form decides what is missing.
  • Recorded assignments, system access and de-identified copies do not prove rights; the USPTO says it does not determine the legality of a recorded transaction.
  • Carry the exclusion into delivery as a rule tied to source identifiers, applied before de-identification and reconciled by count against the approved scope.

What does a missing assignment force a company to decide?

It forces three decisions, in order: which records depend on the missing link, whether any evidence available today closes the gap, and how the records that stay paused are kept out of everything the company delivers. Whether the archive as a whole is licensable is the wrong first question, because the usual answer is part of it.

The situation is common after an asset purchase. The deal file holds the purchase agreement, but the separate assignment or bill of sale it lists as a closing deliverable survives only as an unsigned draft, or not at all. The records sit on the acquirer's servers, often migrated into its own systems years ago, and nobody doubts the business was bought. What cannot be shown is the document that moved the rights in those records.

Nothing here is legal advice, and none of it replaces a lawyer's reading of the actual papers. Whether a particular gap matters, and whether a particular substitute closes it, turns on governing law and the documents themselves, and those calls belong to the company's own counsel. What follows is the decision record a company can assemble so that counsel decides on evidence rather than recollection, and so that the decision survives all the way into delivery.

Lost paper, unsigned paper or no paper needed: which gap is it?

Sort the gap into one of three cases before anything else: the instrument was signed but the executed copy cannot be found, the instrument was never signed, or no instrument was needed because the transfer happened by operation of law. Each case points to different evidence and often to a different outcome.

Deal form decides whether a writing was ever required. Delaware's General Corporation Law, section 259, provides that when a merger takes effect, the property of each constituent corporation, real, personal and mixed, vests in the surviving corporation (paraphrased). The U.S. Copyright Act's section 204(a) says that a transfer of copyright ownership other than by operation of law is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights or its authorized agent (paraphrased). A merger therefore usually leaves a public filing to find; an asset purchase rests on signed transfer documents.

Lost paper and never-signed paper also differ. Courts have rules for proving a writing whose originals are gone: Rule 1004 of the Federal Rules of Evidence admits other evidence of a writing's content when all the originals are lost or destroyed, and not by the proponent acting in bad faith (paraphrased). That rule governs federal litigation, not licensing, but it shows why the search itself is evidence. A dated record of where the company looked, whom it asked and what it found is what separates a lost instrument from one that never existed.

Archives built in the EU add a parallel trail. Under the EU Database Directive, the sui generis right in a database "may be transferred, assigned or granted under contractual licence" (Article 7(3)), so a database the acquired company assembled in the EU has its own transfer question to check beside any copyright.

Only the records whose rights the acquirer holds through the missing transfer depend on it. Records the acquirer's own staff created after closing usually rest on the acquirer's own employment and contractor terms instead, unless they copy or embed content from the acquired archive.

Trace each record set by origin, not by the system it lives in today. Migration hides origin: a ticket queue merged into the acquirer's help desk, a customer history carried into a new CRM or a knowledge base copied page by page all look like the acquirer's own records now. The trace asks who created each record, under which entity, and whether a later record quotes, attaches or was generated from an earlier one.

Possession settles none of this. Section 202 of the Copyright Act treats ownership of a copyright as distinct from ownership of the material object that holds the work, so owning the servers, drives or system that store the records does not by itself carry rights in their content (paraphrased).

Rights in business records are also layered, and an assignment is only one layer. Customer contracts, privacy notices and the earlier owner's promises still govern the same records whatever the chain of title shows. Those questions get their own review, and finding the missing document does not answer them.

The rights-to-records permission matrix for one acquired archive

The matrix gives each record set one row: whether it depends on the missing link, the document that governs it and the evidence that would settle it, the decision today, and how that decision travels into delivery. The example is Illustrative. A facilities-maintenance company bought a smaller competitor's business through an asset purchase in 2019. The purchase agreement is in the deal file, but the intellectual property assignment and bill of sale it names as closing deliverables survive only as unsigned drafts, and the competitor's 2012 to 2019 work-order archive was migrated into the buyer's job system in 2020.

The post-migration work orders are the row teams miss. Records created after closing look clean by date, but when they carry fields copied from the acquired archive, those fields inherit the gap. The migrated customer records show the opposite mistake: a customer-data question does not belong in the assignment review, and resolving the assignment would not clear it.

Five record sets come out of that archive, and only two are paused outright:

The rights-to-records permission matrix for one acquired archive
Record set (Illustrative)Depends on the missing link?Governing document and settling evidenceDecision nowCarried into delivery as
Acquired work orders, 2012 to 2019Yes: created by the seller's staffThe unsigned assignment; an executed copy, or a new signed confirmation from the seller or its successorPaused for counselExclude source system A and job IDs below the migration cutoff
Buyer's own work orders for its original customersNo: created under the buyer's own termsBuyer's employment and contractor termsIn scope, subject to the normal rights reviewIncluded; no exclusion rule
Buyer work orders on migrated customers, 2020 onwardPartly: asset histories and notes copied from the old systemField-level origin flags in the migrated recordsIn scope without the copied fieldsDrop fields flagged as migrated
Seller's knowledge base pages copied into the buyer's wikiYes: written by the seller's staffSame as the acquired work ordersPaused for counselExclude pages carrying the import tag
Customer master records migrated in 2020Not the main question: customer terms and notices govern useSeller's customer contracts and dated noticesHeld for a separate contract and privacy reviewExcluded until that review closes
A flow from five record sets of an illustrative acquired archive: acquired work orders and a copied knowledge base go to excluded by rule, the buyer's own work orders and post-migration work orders with copied fields dropped go to delivered scope, and migrated customer records go to a separate review.
Illustrative archive with a missing 2019 assignment; the exclusion rule runs before de-identification.

What evidence can stand in for a missing assignment?

Evidence ranks by how directly it shows a signed transfer of the rights in question, and counsel, not the data team, decides whether what was found is enough. Work down the list and log every step, including the dead ends:

At a glance

What evidence can stand in for a missing assignment

  • An executed original or a signed counterpart: the closing set held by either side's deal counsel, an escrow or closing agent, the virtual data room archive, or an e-signature platform's completion record.
  • Operative language in a document that does survive: a purchase agreement that itself states a present transfer of the purchased assets may carry weight, and counsel reads its definitions and schedules to see whether the records, and the rights in them, fall inside.
  • Public records: a certificate of merger on the state register, or patent and trademark assignments recorded with the USPTO as part of the same deal. The USPTO's Assignment Center is explicit about what recording does not decide: "The USPTO neither makes a determination of the legality of the transaction nor the right of the submitting party to take the action." A recorded assignment shows what was filed, not that rights in business records moved.
  • A new signed instrument: a confirmation of the earlier transfer from the seller, or from whoever now holds its rights if the seller was dissolved or sold, drafted by counsel. It needs a counterparty able and willing to sign, which is its practical limit.
  • Corroborating conduct: closing statements, payment records, notices sent to the seller's customers and migration project files. They support the account of the deal; on their own they rarely show which rights were conveyed.
  • Nothing found: the dependent records stay excluded, and the log names the document whose discovery would reopen them.

Does system access or de-identification change the answer?

No. Being able to open, export or de-identify the records shows technical control, and de-identification changes what the records reveal about people; neither shows that rights in the records reached the company.

The argument is tempting because the archive works. It sits in the company's systems, the team has used it for years, and a privacy pass would strip names and contact details. But section 202 already separates owning the container from owning the content, and a redaction pass does not move title from a seller to a buyer. If the missing link is real, a de-identified copy of the dependent records carries the same gap, only harder to trace because the identifiers that showed its origin may be gone.

SourceX's process puts the question before any records move. Its how-it-works page lists what a supplier confirms, starting with having the rights to license the data, and its screening guide states the rights test plainly: "The company owns the material, or can license it without breaching client confidentiality, employee privacy or third-party contracts." A company that cannot show that yet for part of an archive can still offer the part it can show.

The review log that carries a pause into delivery

Record each gap as one log entry naming the decision owner, the evidence searched and found, counsel's outcome and an exclusion rule a data engineer can run. The entry is what lets a pause survive staff changes, re-exports and a second licensee.

Two practical rules decide whether an exclusion holds. First, write it against source identifiers, such as originating system, record ID ranges, import tags and migration flags, and apply it before de-identification, because de-identification can remove exactly the fields that show where a record came from. Second, reconcile counts: records in the source extract, minus records the rule excludes, should equal records in the delivered set, and any difference is explained before anything ships.

Keep counsel's reasoning in counsel's own files. The log carries the outcome, its date and its scope, which is what an operations team needs and what a licensee's rights reviewer will ask to see. The log's fields, with an Illustrative entry for the paused work orders:

The review log that carries a pause into delivery
FieldWhat to recordIllustrative entry
Gap ID and record setsThe missing link and every record set that depends on itG-01: 2019 IP assignment; acquired work orders and copied knowledge base
Instrument and its jobWhat the missing document should have done, under which agreementAssign the seller's rights in business records under the 2019 purchase agreement
Search logWhere the company looked, whom it asked, dates and resultsDeal counsel's closing set, e-signature account, data room export: drafts only
Substitute evidenceWhat was found and how directly it shows a signed transferPurchase agreement whose asset schedule names the job system
Decision owner and counsel outcomeWho decides for the company, counsel's conclusion in one line, dateGeneral counsel: not cleared pending a seller confirmation, dated
Exclusion ruleThe rerunnable filter that keeps dependent records outSource system A, import tag kb-2020 and migrated-field flags
Delivery checkCounts before and after the rule, reconciled to the approved scopeExtract count minus excluded count equals delivered count
Reopen triggerThe one event that would change the decisionSigned confirmation from the seller's successor

Cleared, narrowed or excluded: closing the decision

Every gap should end in one of three states: cleared on evidence, licensed in a narrower scope with the dependent records excluded, or excluded until a named document appears. A gap left open without a state is how paused records drift back into scope at the next export. Record the state, and the limits of the review, in the log:

At a glance

Cleared, narrowed or excluded: closing the decision

  • Cleared: counsel concludes the evidence shows the transfer; the record sets move into scope and the log keeps the evidence that cleared them.
  • Narrowed: the dependent record sets stay out, the rest proceed, and the exclusion rule is written into the scope the company approves.
  • Excluded with a trigger: nothing now closes the gap; the log names the document or signature that would reopen it and who checks for it.
  • Limits: what was not searched, which copies could not be opened, and which layers, such as customer terms and privacy notices, were reviewed separately and by whom.

Offering the cleared scope to SourceX

When the licensee is SourceX, the narrowed scope travels through documents the company signs. SourceX's how-it-works page says its qualification step includes a rights check, and that before SourceX presents an opportunity externally both sides sign a short Dataset Deal Confirmation fixing the exact dataset, the rights and the processing route, with any later material change needing a signed amendment. An exclusion rule written into that scope is what keeps paused records out of the deal.

Scope and terms are approved, and the agreement signed, by the company before a single record goes to SourceX, so the time to settle which records depend on a missing assignment is before that signature, not during preparation. A supplier also confirms the data has not been licensed for AI training before, so the same log can note any earlier licensing of the archive. The first step is a short company assessment that needs no data uploads; it is not an offer, and no payment follows unless a deal closes.

Frequently asked questions

What happens if the IP assignment from an acquisition cannot be found?

First establish whether it was signed and lost, never signed, or not needed because the deal was a merger. Then trace which records depend on it, ask counsel whether surviving evidence closes the gap, and keep dependent records out of any license until it does. Records the acquirer created itself often do not depend on it.

Does owning the servers mean a company owns the records on them?

Not by itself. U.S. copyright law treats ownership of a copyright as distinct from ownership of the object that holds the work, so possessing systems or drives does not show that rights in their content were transferred. Counsel should read the deal documents.

Is a recorded USPTO assignment proof that data rights transferred?

No. The USPTO says it makes no determination of the legality of a recorded transaction or of the submitting party's right to take the action. A recorded patent or trademark assignment can corroborate that a deal happened, but it does not show which rights in business records moved.

Can de-identifying acquired records cure a chain-of-title gap?

No. De-identification changes what records reveal about people; it does not move rights from a seller to a buyer. A de-identified copy of records whose title depends on a missing assignment carries the same gap, and may be harder to trace.

Should records created after the acquisition be paused too?

Usually not, if the acquirer's own staff created them under its own terms. The exception is content copied or migrated from the acquired archive, such as carried-over notes or imported knowledge base pages, which inherits the gap and should be excluded field by field or page by page.

Sources

  • Delaware General Corporation Law section 259 provides that on a merger the property of each constituent corporation, real, personal and mixed, vests in the surviving corporation. Source
  • Sections 202 and 204(a) of the U.S. Copyright Act separate copyright ownership from ownership of a material object and require a signed writing for a transfer of copyright ownership other than by operation of law. Source
  • Federal Rule of Evidence 1004(a) allows other evidence of a writing's content when all the originals are lost or destroyed, and not by the proponent acting in bad faith. Source
  • Article 7(3) of Directive 96/9/EC provides that the sui generis database right may be transferred, assigned or granted under contractual licence. Source
  • The USPTO's Assignment Center says the USPTO neither makes a determination of the legality of the transaction nor the right of the submitting party to take the action. Source
  • SourceX's how-it-works page describes the rights check at qualification, the Dataset Deal Confirmation, signed amendments for material changes, and what a supplier confirms about rights and prior AI training licenses. Source
  • SourceX's screening guide defines rights to license as owning the material or being able to license it without breaching client confidentiality, employee privacy or third-party contracts. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies