Legal holds on acquired company records: what can still be licensed

Does a legal hold stop you from licensing records?#

A legal hold does not automatically stop licensing, because a hold is a duty to preserve relevant records rather than a ban on all use. The originals must stay complete and unaltered for as long as the hold lasts. Whether a copy can be licensed is a separate question for counsel.

Counsel usually weighs four things: whether the records relate to the dispute's subject matter, whether a protective order or settlement confidentiality term covers them, whether they contain privileged communications, and whether preparing a copy could alter or delete the originals. Clear answers on all four make a copy far easier to approve.

The safe default for an acquirer is to treat every held record as excluded until counsel has reviewed the hold and signed off in writing on a defined copy.

Where inherited holds hide after an acquisition#

Inherited holds hide in documents and in systems, and integration teams usually miss the second place. A purchase agreement schedule may list pending litigation, but the hold that implements it lives in an admin console.

• 1Disclosure schedules covering litigation, threatened claims and government inquiries.
• 2Hold notices issued by the acquired company's counsel, and any release notices.
• 3Slack legal holds (an Enterprise-tier feature), which save messages and files regardless of retention settings, even if members edit or delete content.
• 4Google Vault matters and holds on Gmail, Drive and Chat.
• 5Microsoft Purview holds and retention policies on mailboxes, Teams and SharePoint.
• 6Holds or retention locks set inside help desk, CRM or document management systems.

Ask for the hold log before integration starts#

The hold log is the single most useful document a holdco general counsel can request from an acquired company. It should list each matter, the custodians and systems covered, the date range, the date the hold was issued and whether it was released.

Holds that were never formally released are common, and they should be resolved with litigation counsel rather than ignored. An open hold on a matter that settled years ago still blocks routine cleanup until someone documents its release.

Departed employees are a frequent trap. In Microsoft 365, deleting the mailbox of a user covered by an active Teams retention policy turns it into an inactive mailbox that keeps the Teams data; without such a policy, a departed user's data may not survive an account cleanup during integration.

What stays out and what may be licensed#

Record status decides the starting position. The table is a default for discussion with counsel, not a rule that replaces counsel's judgment.

The middle rows are where most judgment calls sit. A hold drafted broadly at the start of a dispute, covering every mailbox in a department, often reaches records unrelated to the claim. Counsel can sometimes narrow the hold or confirm that a defined set falls outside it, but that decision belongs to litigation counsel, not the integration team.

How to copy held records without breaking preservation#

Copying held records safely means exporting from the preserved source in a way that changes nothing, then doing every transformation on the copy. Redaction, de-identification and deduplication must never touch the originals.

Keep the export plan simple enough to explain to a court. A preservation process that a forensic examiner can follow step by step is far easier to defend than a clever pipeline nobody documented.

• 1Export read-only from the preserved system or a forensic image, and keep hashes or export logs.
• 2Pause migrations, decommissioning and retention rules that could purge held data during preparation.
• 3Download platform exports promptly: Microsoft Purview eDiscovery exports expire 14 days after creation, and Google Vault exports are deleted 15 days after the export starts.
• 4Store licensing copies apart from litigation copies, with access limited to the preparation team.
• 5Log what was copied, when and by whom, and keep the log in the hold file.

Counsel's sign-off checklist#

Counsel's sign-off should be a short written record rather than an email thread. A sponsor or holdco general counsel typically confirms the items below before a copy goes to preparation.

File the signed checklist with the hold log and the license record, so anyone who reviews the package later sees one consistent account of what was held, what was copied and why.

Illustrative: a holdco inherits a warranty dispute#

Illustrative: a fictional holding company acquires a precision components manufacturer that is in a warranty dispute with a customer over one product line. The target's counsel had placed holds on the quality team's Microsoft 365 mailboxes and on nonconformance reports and CAPAs for that line in its QMS.

After integration, the holdco considers licensing quality records: NCRs, CAPAs, inspection results and supplier corrective actions across all product lines. The holdco general counsel confirms the hold scope with litigation counsel, excludes the disputed product line and the held custodians' email, and approves a read-only export of the remaining QMS records.

Outcome: the originals stay preserved in place, the license package covers the other product lines, and the carve-out is recorded so it can be revisited when the dispute ends.

How SourceX treats records under a hold#

SourceX asks about legal holds during the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Held records are left out of scope unless the supplier's counsel signs off on a defined copy.

SourceX does not take custody of originals. Preparation works on copies, and large datasets stay in the supplier's own storage or ship on encrypted drives. The SourceX Evidence Packet records provenance and release authorization, including the carve-outs counsel required.