A technology continuity checklist for acquirers.
Use this checklist to identify what the business depends on, what must transfer at closing and who will operate it afterward. For every item, record the evidence, current owner, gap, business consequence and next action. An unknown is a finding to resolve, not a pass.
01 / Evidence to request before closing.
| Area | Request and verify | Question for the business |
|---|---|---|
| Dependency | Map revenue and delivery processes to systems and integrations. | What stops if this fails? |
| Control | Company admin, billing and recovery rights for cloud, domains, repositories and data. | Can the buyer operate without the seller’s personal account? |
| Knowledge | Named operators, runbooks and transition sessions. | Whose departure would interrupt the business? |
| Recovery | Backup inventory and a recent restoration record. | What service and data can be recovered, and how was it tested? |
| Rights | Project work rights, licenses, source availability and vendor transfer requirements. | What needs consent or a replacement contract? |
| Vendors | Service scope, renewals, dependencies and contacts. | Which supplier can stop a critical process? |
| AI | Tools, data exposure, permissions, evaluations and fallback. | Who accepts the output and who can stop the agent? |
| Roadmap | Costed priorities, assumptions and unresolved incidents. | What must be funded before the next improvement? |
02 / Use one action record for every gap.
Copy these fields into your diligence tracker. This is a working template, not a scored certification.
- 01
System or process; business owner; criticality.
- 02
Evidence requested; evidence received; what was actually verified.
- 03
Current account owner; receiving company account; transfer requirements.
- 04
Gap; consequence; cost assumption; specialist review needed.
- 05
Action owner; target date; dependencies; acceptance evidence.
A single aggregate score can hide an untransferable critical account. Review critical exceptions individually.
03 / Make closing dependencies explicit.
Separate items required before closing from items that can proceed under an agreed transition arrangement. For each deferral, record who will keep the process running, how the buyer can escalate and when the arrangement ends. Legal and transaction advisers decide how the obligations belong in the deal documents.
04 / Turn the findings into the first 100 days.
Sequence account control, seller knowledge capture, recovery tests and the first stabilization change. Keep cost assumptions visible as new evidence arrives. The same record should be useful to the buyer, operator and any alternative remediation provider.
Follow the first 100 days plan. See acquisition continuity support. Compare build, buy and retirement decisions.
Editorial review: Ego Eimi · Updated September 6, 2026 · About the team
Your technology
Start with the business
Your business depends on it.
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.