How to harmonize data retention policies after an acquisition

After an acquisition, set one retention schedule by record class, using the longest of the legal minimum, contract duty and business need, rather than defaulting to the shortest policy. Pause auto-deletion first, honor any legal hold, and have counsel confirm each period so records stay available for audits, disputes and later data licensing.

What should happen to retention schedules when you buy a company?

Do not default to the shortest schedule, and do not default to the acquirer's. Build a single schedule record class by record class, keep anything under a legal hold or contract duty, and write down what the acquired company already held before you change anything.

The reason is practical. Deleting under a new, shorter schedule is permanent, while keeping records a little longer costs only storage. Deleted history cannot be recovered later for an audit, a dispute or a buyer diligence request, and it also cannot be licensed. This is general information, not legal, tax or financial advice. Confirm with your own counsel before changing any retention rule.

Why the shortest schedule should not win by default

Two policies in conflict usually look like a simple choice: pick the stricter one, or pick the parent's. Both shortcuts fail in specific ways.

  • The shortest period can be shorter than a statute, a customer contract or an insurer requires for that record class.
  • A schedule written for a software company rarely fits the acquired field-service or finance-heavy business.
  • Auto-deletion jobs keep running on the acquired company's systems unless someone turns them off, so a "temporary" gap in policy can still destroy records.

Operating partners usually meet this problem during the first integration quarter, when IT consolidates tenants and someone asks whether old Slack, helpdesk and mailbox data can simply be purged to cut cost.

The harmonization sequence

Work through it in this order. The first two steps are what most teams skip.

  1. Freeze deletion. Pause automated purge jobs and retention labels on the acquired company's mailboxes, chat, helpdesk and shared drives until the review is done.
  2. Inventory what exists. For each system, record the owner, oldest record, current retention setting and whether deletion has been running. Capture metadata only, never content.
  3. Check for holds and duties. Ask counsel to list any pending or threatened dispute, regulatory request, customer audit right or contract clause that requires keeping records.
  4. Map record classes. Group records into classes such as contracts, finance, HR, customer communications, support tickets, engineering and operations.
  5. Set the period per class. Use the longer of the legal minimum, the contract requirement and the business need, then document the reason.
  6. Re-enable deletion deliberately. Switch purge jobs back on only after the class schedule is approved, and log who approved it.

What does a retention conflict look like in practice?

The table shows common conflicts and how to resolve them. Treat the "typical resolution" column as a question to put to counsel, not as an answer.

SituationWhat to checkTypical resolution to confirm
Target keeps support tickets for ten years, parent keeps twoCustomer contract terms, audit rights, dispute historyKeep the longer period for the class until counsel signs off
Target auto-deletes chat after 90 days, parent keeps indefinitelyWhether the setting is a policy or a plan defaultDecide per channel type; suspend deletion in the meantime
Pending claim against the targetScope and custodians named in the holdHold overrides every schedule for the named custodians and systems
Departed founder's mailboxWho owns the account, notice to employeesPreserve the mailbox; decide the period after the review
Records created by a contractorWritten assignment of rightsKeep them, but note rights may sit with the contractor

Legal holds override every schedule

A legal hold is an instruction to preserve records because a dispute or investigation is pending or reasonably expected. It is counsel's call, not IT's or the operating team's. When a hold exists, it applies to the acquired company's records after closing, and the new owner inherits the duty.

Ask the seller's counsel for the list of active and past holds as part of closing, and ask your own counsel how holds are released and recorded. Keep the hold notice with the retention inventory so a later reviewer can see which systems were affected.

How retention choices affect what a company can later license

Records that survive can be assessed; records that were purged cannot. A company that is considering a data license later needs years of connected records across several systems, and consolidation is the moment they are most likely to disappear. A longer, documented schedule for support, engineering and operational records keeps that option open without committing anyone to a license.

Licensing also depends on promises already made to customers. The FTC has stated in staff guidance that a company's commitments not to use customer data for undisclosed purposes, such as training or updating models, are enforceable. So when you harmonize policies, keep the acquired company's customer commitments with the records they cover. Which entity may license which set is covered in the guide to legal entity rationalization after acquisitions.

The system-level guides show where history tends to be lost first: merging Slack workspaces and merging helpdesk instances. If a license is ever considered, the term and exclusivity are matters for counsel, and the page on exclusive license term length explains how they work.

What to say to the portfolio company CFO

Keep it a process request. Do not ask the company to export, send or describe any record contents to you.

How this connects to a SourceX introduction

A retention inventory is also most of a data inventory. If a portfolio company has long-lived records and an authorized sponsor, you can introduce it to SourceX, which runs qualification, inventory, pricing, buyer review and delivery. You make the introduction only; you never handle the records. De-identification and redaction are agreed with the company before any work begins, and nothing is delivered without an executed agreement.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward is payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. Check your firm's policies on fees connected to portfolio companies first, and read the program terms.

When this is not the right moment

  • A hold, investigation or insolvency process controls the records and counsel has not cleared any discussion of licensing.
  • The company never reached 50+ full-time employees at peak (contractors excluded), or has only a few years of thin records.
  • Archives were already deleted under the acquirer's schedule and nobody can export what remains.

Next step

Pause purge jobs at one recent acquisition and build the system-by-system inventory this week. Run the company through the company fit checker, review the who qualifies baseline, and if it fits, register as a partner. The wider playbook for operating partners and the guide to value creation in longer holds cover where this fits in the hold.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Who decides the retention period after a merger?

The company's board or executives approve the schedule, but counsel should set the minimums for each record class based on law, contracts and open disputes. IT then implements it. Operating partners can require that no deletion rule changes until counsel and the CFO have signed a written schedule for the acquired company.

Should we keep the acquired company's records forever?

Not necessarily. Indefinite retention raises storage cost, privacy exposure and discovery burden. The point is to avoid premature deletion while the review runs, then set a defined period for each record class. Some classes, such as contracts and finance, usually warrant longer periods than casual chat. Counsel should confirm each period.

What if the acquired company already deleted old data?

Record what was deleted, when and under which setting, and stop any further purge. Check whether backups or exports exist. Deleted history reduces both litigation readiness and any later licensing options, so document the gap rather than hiding it, and tell counsel about it promptly.

Does a retention policy affect whether data can be licensed?

Indirectly. A license needs records that still exist, rights to license them and an authorized sponsor. Retention decides whether the records exist, while contracts, privacy notices and customer commitments decide whether they may be licensed. Counsel reviews both before any agreement is signed.

Can a minority or financial owner pause deletion on its own?

Usually not directly. Investor rights vary by shareholder agreement, and the operating company controls its own systems. A sponsor can ask for a pause through the board, the CFO or the integration lead. If the request is refused, escalate it to counsel rather than touching the systems yourself.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment