Day 1 readiness in M&A: which data decisions to defer and which to block
A Day 1 readiness plan should block irreversible actions on the acquired company's legacy systems and defer every licensing decision. Integration leads can add a one-line hold with a review date, run a short records inventory in the first 60 to 90 days, then decide system by system.
What data decisions belong on a Day 1 readiness plan?
Day 1 should make one data decision only: do not shut down, wipe or consolidate legacy systems of the acquired company until its records have been inventoried. Everything else about licensing, archiving and value can wait. A one-line hold instruction and a review date protect the option without distracting the team from the things Day 1 is for.
Integration leads own a crowded list on Day 1: payroll, email and identity, customer communications, banking, facilities and reporting lines. Records strategy is not on it, and it should not be. What is on it, or should be, is a freeze on irreversible actions that destroy history before anyone has looked.
Why is Day 1 the wrong time to raise licensing but the right time to block shutdowns?
Day 1 is the wrong time to raise licensing because sellers, employees and customers are absorbing the change, and rights and sponsorship are unsettled. It is the right time to block shutdowns because duplicate tools can look like easy savings once the deal closes.
The acquired company's systems are the longest-lived records of how it ran: CRM history, ticket archives, finance and project tools. Once a license is cancelled or a tenant is merged, the history may not be recoverable. The hold costs a few weeks of duplicate subscriptions, and keeps the choice open.
What is the one-line hold instruction?
Put this in the Day 1 runbook under IT and data, owned by the integration lead.
Pair it with a named owner and a date. A hold with no review date becomes a permanent freeze that finance will challenge.
What is the timeline from signing to the records review?
| When | Action | Owner |
|---|---|---|
| Signing to close | List the target's systems from diligence materials; flag renewal and notice dates | Deal team, integration lead |
| Day 1 | Issue the hold instruction; confirm admin access and who can run exports | Integration lead, IT |
| Day 1 to day 30 | Keep legacy systems running; stop auto-deletion or retention changes where possible | IT |
| Day 30 to day 60 | Short inventory: system, years of history, export path, owner | IT, target's operations lead |
| Day 60 to day 90 | Decide per system: migrate, archive, retire, or screen for licensing | Integration lead, sponsor |
| Before each renewal date | Confirm no system lapses by default | Finance, IT |
The exact days should follow your own integration plan. What matters is that each system gets a deliberate decision before its renewal date.
What should the records review look at?
Keep it to a half-day with the acquired company's operations lead and IT. Ask for each system:
- Years of history held and the date of the oldest record
- Whether the company or a vendor controls the export
- Which other systems it connects to
- What contracts or notices limit use of the data
- Renewal and notice dates
Then ask whether the combined business has an authorized sponsor, whether the acquired entity has 50+ full-time employees at peak (contractors excluded), and whether the owner would consider an exclusive AI-training license. The who qualifies page has the baseline. Acquired and wound-down companies can qualify if the data still exists, and the downsized company question covers a related case.
Which systems are the usual casualties?
| System | Why it gets cut | What to do instead |
|---|---|---|
| Acquired CRM | Overlaps the buyer's CRM | Export fully; see CRM cleanup before migration |
| Salesforce or similar org | Contract expires after close | Check notice dates; see what happens to Salesforce data when the contract ends |
| Legacy file shares | Office consolidation | Archive before the move |
| Help desk | Merged into one queue | Keep read-only export |
| Old email tenant | Domain migration | Preserve before tenant deletion |
The office closure checklist helps when the deal closes an office. For broader closure plans, see how to wind down a company without losing its records.
When should the licensing conversation start?
After the first 90 days, once the hold has been honored, the inventory is complete and the sponsor has bandwidth. Ownership of the data after close should be confirmed with deal counsel: the purchase agreement defines what transferred. Records belonging to the seller's customers or to a carved-out unit may not be the buyer's to license. This is general information, not legal, tax or financial advice.
An integration lead can then raise it with the sponsor, or hand it to whoever owns commercial strategy.
The introduction email builder can draft the message.
Who do you talk to on the target side?
Records knowledge sits with a few people, and they are often the ones most at risk of leaving after close.
- Head of operations or COO: knows which systems drive daily work and which are dormant but full of history.
- IT lead or MSP contact: holds admin credentials, renewal calendars and export know-how.
- Finance lead: knows which subscriptions auto-renew and which contracts restrict data use.
- Founder or selling owner: may still be the authorized sponsor for the acquired entity during the transition; confirm who can decide.
Ask each one the same question: "Which system, if it disappeared next month, would take the most history with it?" The answers become your inventory shortlist. Capture who can run exports before retention agreements for these people end, because a system nobody can export is effectively lost.
How do referral rewards work, and what are the limits?
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Payment follows only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The reward is never deducted from the company's proceeds. Integration leads who are employees or advisors should check their employer's conflict and gift policies before registering, and see the program terms.
When should you not bother?
Skip it when the acquired company is under 50 full-time employees at peak, when the purchase agreement leaves the data with the seller, when archives are already deleted, or when a court or trustee controls the assets. The hold instruction is still good practice in each case.
Next step
Add the hold line and a review date to your Day 1 runbook this week. When a company reaches the review and passes the baseline, register as a partner and make the introduction.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Should data licensing be on the Day 1 checklist?
No. Day 1 is for continuity, payroll, access and communications. The only data item to include is a hold on decommissioning, purging or retention changes to the acquired company's systems, with a named owner and a review date. Licensing, if relevant, comes after the inventory.
How long should the legacy systems hold last?
Tie it to a review date, often within the first 60 to 90 days, and to each system's renewal and notice dates. A hold with no end date will be challenged by finance. Cost of duplicate subscriptions for a few weeks is small compared with losing the history.
Who owns the acquired company's data after closing?
The purchase agreement and the facts decide. Deal counsel should confirm what transferred, including any records belonging to the seller's customers or to excluded units. Do not assume everything in an acquired system is licensable. Rights are reviewed before any licensing process moves forward.
Can an acquired or integrated company still qualify?
Yes, if the data still exists, rights are clear, and the entity meets the baseline: 50+ full-time employees at peak with contractors excluded, several years of documented operations and an authorized sponsor. Companies that are still operating, acquired or wound down can all qualify.
Does the integration lead handle any records?
No. The integration lead or other partner makes the introduction and shares basic fit information. The company works with SourceX on the inventory, price and terms, redaction rules and delivery, and nothing is delivered without an executed agreement and the company's authorization.
Related pages
- Which US businesses are a fit for a SourceX data licensing introduction
- Does a company that downsized still qualify for data licensing?
- CRM data cleanup before migration: what to fix, what to keep, and what to assess first
- What happens to Salesforce data when the contract ends, and what to do before it does
- Office closure checklist: records, IT and data to settle before you leave
- How to wind down a company: an orderly plan that keeps the records
Free resources
- Time value of money calculator — Future and present value with optional regular payments.
- Business DSCR calculator — Debt service coverage from cash flow and loan terms.
- MCP ROI calculator — Estimate hours saved, implied savings and first-year ROI from MCP.
- All free tools · MCP resource center
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