Systems and records
Acquisition data preservation budget: shutdown deadlines and cost lines
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
An acquisition integration budget should carry archive preservation as its own line, built system by system from the date each one stops being reachable: the subscription end, the vendor's post-termination deletion window or the transition services expiry. For each system, budget the export, validation, storage, read-only access and legal hold work in people-days and months, name an owner, and fund it before the first shutdown date.
Value drivers
Acquisition data
Key takeaways
- Build the preservation budget from deadlines: the earliest of subscription end, vendor export window and transition services expiry.
- Vendor deletion windows are short and differ by vendor, so read each agreement rather than assuming.
- Cost each system in people-days and months across export, validation, storage, read-only access, documentation and legal holds.
- Keep preservation as its own integration line so it is not cut in favor of migration work.
- Legal holds and statutory keep periods set the floor; counsel confirms before any system with relevant records is shut down.
How should an acquisition data preservation budget be built?
Start from deadlines, not from systems. For every application the acquired business uses, find the date after which its records can no longer be exported in full, then work backwards to schedule and cost the preservation work. The budget is the sum of those per-system schedules plus a contingency for legal holds and for systems discovered late.
Preservation is often treated as a by-product of migration: whatever is moved to the acquirer's platforms is kept, and the rest is assumed to sit safely in the old tools. It does not. Cloud subscriptions end, vendors delete data on published timetables, and transition services agreements have hard expiry dates. When nobody has funded the export, validation and storage of the history that is not being migrated, it is lost by default.
This page is about the money and the calendar. Existing guidance covers whether to archive or migrate and what a records checklist should contain; the question here is how to put that work into the integration budget with dates attached, so that it is approved and staffed before the first deadline passes.
Which date actually ends access to each system?
The binding date is the earliest of three: the end of the subscription or license, the end of any post-termination window the vendor allows for export, and the expiry of a transition service that keeps the seller's systems running for the buyer. Each is written down somewhere, and each needs to be read rather than assumed.
Vendor windows differ and are usually short. Microsoft says it keeps Microsoft 365 customer data in a limited-function account for 90 days after a subscription ends so the customer can extract it, and deletes all customer data no more than 180 days after expiration or termination. Salesforce's security and privacy documentation says customers may request return of their data within 30 days of contract termination, after which the data is held inactive for a period and then deleted. Atlassian's cloud licensing terms describe deleting a paid site's data 60 days after the subscription ends or is cancelled. These windows change: Salesforce's document reserves the right to reduce how long it keeps data after termination, so recheck each vendor's current terms when the schedule is built.
Transition services agreements add a second calendar. In the 2023 agreement between BorgWarner and PHINIA filed with the SEC, each service was capped at 12 months from the effective date, with a limited extension, and on expiry the recipient had to expunge data from systems in its possession or control. The Jacobs and Amentum agreement filed in 2024 required the provider to keep a backup during electronic data migration and preserve it for 90 days after notifying that transmission was complete, so the recipient could validate the transfer. These are examples of how such terms are drafted, not a standard; read the schedule in your own agreement.
The system shutdown deadline and preservation cost schedule
Fill one row per system, and sort the finished schedule by the binding date. The rows below are illustrative system types with the kind of entries each needs; the deadline driver column tells you which document to read for the actual date.
Two columns are deliberately missing from the illustration because they must come from your own documents: the binding date itself and the start date for the work. Work back from the binding date by the estimated people-days, then add a validation buffer long enough to rerun a failed export before access ends. Any row whose start date falls before close, or within the first weeks after it, is a signal to raise the item in the pre-close integration plan, since waiting for the first integration budget cycle may already be too late.
Review the schedule at every integration steering meeting and treat a missed export date the same way as a missed migration milestone.
| System (illustrative) | Deadline driver to read | Preservation work | Cost lines to budget | Owner |
|---|---|---|---|---|
| Office suite and email tenant | Subscription end plus vendor retention window | Mailbox and file export, litigation hold check, index | Export people-days, storage months, eDiscovery tool access | IT integration lead |
| CRM | Contract end and post-termination export request window | Full object export with history, attachments and audit fields | Export and validation people-days, storage, read-only seat months | Sales operations |
| Help desk or ticketing | Subscription end and vendor deletion period | Tickets with full comment threads, macros and attachments | Export scripting days, validation sampling, storage | Support operations |
| ERP or accounting system | License or hosting end, or TSA service expiry | Ledger, subledgers, documents, record layouts and field definitions | Read-only license months, conversion days, documentation days | Controller |
| Seller-hosted shared system under a TSA | TSA service term and extension notice period | Separation, transfer, integrity validation before expiry | Migration days, validation days, extension months if needed | Integration management office |
| Code repositories and issue tracker | Hosting or license end | Repository mirrors, issue history, CI logs | Export days, storage | Engineering lead |
| HR and payroll | Vendor contract end and statutory keep periods | Employee and payroll records, tax filings | Export days, restricted storage, access controls | HR lead with counsel |
| Records under legal hold | No earlier than release of the hold | Preserve in place or forensically collect before shutdown | Collection days, hold storage for an open-ended term | Legal |
What cost lines belong in the preservation budget?
Budget each line in units the integration team can estimate and finance can price: people-days for work, months for storage and licenses, and counts of systems for tooling. Leaving the pricing to finance keeps the schedule usable across deals and keeps the integration plan focused on effort and dates.
At a glance
What cost lines belong in the preservation budget
- Export labor: scripting or running exports, including attachments and history tables that default exports omit.
- Validation: record counts, sample checks against the live system and checksum logs, done before the source is switched off.
- Storage: months of archive storage, with a separate line for restricted storage of HR, payroll and other sensitive records.
- Read-only access: license or hosting months to keep a system queryable where an export cannot reproduce what auditors or courts may need.
- Format and documentation: conversion to open formats and written record layouts and field definitions, so the archive can be read without the old software.
- Legal hold handling: collection, chain-of-custody records and storage for holds with no end date.
- Access management: named custodians, access reviews and logging for the archive after the original admins leave.
- Decommission sign-off: a certificate that export and validation were completed before shutdown.
- Contingency: systems found after close, extension months on transition services and rework when validation fails.
Which retention duties set the minimum keep period?
Tax, employment and litigation rules set the floor, and the archive must still be usable when they apply. The IRS says to keep records supporting a return until the period of limitations runs out, generally three years, and longer in specific cases: seven years for a bad debt or worthless securities claim and at least four years for employment tax records.
For records kept in electronic systems, Rev. Proc. 98-25 sets expectations for machine-sensible records: they must be retained while they may be material to tax administration, reconcile to the books and the return, contain enough transaction-level detail to trace source documents, and come with documentation of record formats and field definitions. It also says a record retention limitation agreement does not cover subsidiaries acquired after the evaluation it was based on. That makes the layout documentation line in the budget a compliance item, not a nice-to-have.
Litigation adds a duty that no schedule can override. Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation and was lost because a party failed to take reasonable steps. The committee notes say reasonable steps, not perfection, are required, and that a less costly form of preservation can be reasonable if it is substantially as effective. Before any system with potentially relevant records is shut down, counsel confirms whether a hold applies.
Which entity controls each record after close?
Write the controlling entity next to every system in the schedule, because the answer decides who pays for preservation and who may later use the archive. In a stock purchase the acquired company usually keeps its own records and contracts. In an asset purchase or carve-out, only the assets and contracts listed in the transaction documents move, and records about excluded businesses may stay with the seller even when they sit in the same database.
Shared systems are the hard case. When a seller's ERP or email tenant holds the carved-out business's records and runs under a transition services agreement, the buyer depends on the seller's cooperation to separate and export them before expiry, and some agreements require the recipient to delete seller data from its own systems at the end. Budget the separation work early and confirm in writing which records the buyer is entitled to take.
Control of records is separate from the right to use them for anything new. An acquirer that controls an archive still inherits the customer contracts, privacy notices and consents under which the records were collected, and those continue to govern later uses.
Is preservation a transaction cost or an integration cost?
Treat it as integration spending with its own line, and agree the classification with finance before close. Under IFRS 3, acquisition-related costs such as advisory, legal, accounting and valuation services are expensed as incurred rather than added to the purchase consideration, and the standard explains that they are separate transactions in which the buyer pays for services received. Preservation work after close sits in operating or integration spending in most models, which is exactly why it gets squeezed when integration synergies are being chased.
Keeping preservation visible as a separate line protects it. When the archive budget is folded into a general IT integration bucket, it competes with migration work that has a visible business case, and the export of history that nobody uses day to day is the first item cut. Accounting treatment varies by framework and facts, so the finance team confirms classification for the specific deal.
Worked example (illustrative): a carve-out with a twelve-month transition period
Illustrative only; the businesses, systems and durations are invented. A buyer acquires a regional distribution business carved out of a larger group. The business runs on the seller's ERP and email tenant under a transition services agreement with a 12-month term, and on its own CRM and help desk subscriptions, which renew in month 4 and month 7 after close.
The schedule puts the help desk first: the team does not plan to renew it, the vendor's deletion window is short, and the binding date falls in month 7. Export and validation are planned for 6 people-days in month 5. The CRM is being migrated, but its history tables and attachments are not, so the archive export is planned for month 3, before renewal. The ERP has the latest binding date but the most work: separating the carved-out entity's ledgers, converting them and documenting layouts takes an estimated 30 people-days across months 6 to 9, leaving three months of buffer before expiry.
One legal hold covers sales correspondence from a customer dispute. The email export for the held mailboxes is collected forensically in month 2 and kept in restricted storage with no end date. The finished budget lists 4 systems, about 50 people-days, storage and read-only access months per system, and a contingency for one transition services extension.
When is keeping the old system running the cheaper path?
Keep a system read-only instead of exporting it when an export cannot reproduce what an auditor, regulator or court will ask for. Audit trails, approval histories and calculated balances in ERPs and regulated record systems often lose meaning outside the application, and rebuilding that context can cost more than months of read-only access.
The exception has a limit: a read-only system still needs a license, someone who knows how to query it, security patching and an end date. Put those months in the schedule with a review date, and plan the final export for when the longest applicable keep period expires. Stop and get specialist review when records are subject to a hold, sector-specific retention rules or a dispute over which entity controls them; integration leads should not decide those questions alone, and this page is general information rather than legal or accounting advice.
What a preserved archive makes possible later
A validated, documented archive keeps future options open, including assessing whether selected records could be licensed for AI. If an acquirer later explores that route, SourceX can take chosen records through rights review, contracting, preparation and delivery as a licensed dataset, and an archive too big to host can be read where it sits or carried on encrypted drives, since SourceX does not host multi-terabyte sets. The acquirer would approve scope and terms and sign before any record moved, so funding preservation today commits it to no later use.
Frequently asked questions
What should a system shutdown deadline and preservation cost schedule include?
One row per system with the document that sets its binding date, the date itself, the preservation work, the cost lines in people-days and months, and an owner. Sort it by date and add a contingency for systems found after close and for legal holds.
When does a cloud vendor delete data after a subscription ends?
It depends on the vendor and the agreement. Microsoft describes a 90-day limited-function period for Microsoft 365 data, Salesforce a 30-day window to request return of data after termination, and Atlassian deletion of paid site data 60 days after the subscription ends. Read the current terms for each system rather than assuming.
Who should own archive preservation after an acquisition?
The integration management office should own the overall schedule, and each system should have a named owner from the function that uses it. Legal owns holds, and finance owns classification of the cost.
Can we shut down a system that holds records under a legal hold?
Not until counsel confirms the records have been preserved in a way that satisfies the hold, either in place or by forensic collection. Federal Rule 37(e) addresses loss of electronically stored information when reasonable preservation steps were not taken.
Is archive preservation part of the purchase price?
Generally not. Under IFRS 3, acquisition-related service costs are expensed as incurred rather than included in consideration, and preservation after close is usually budgeted as integration spending. Finance confirms the treatment for the specific deal and framework.
Sources
- Microsoft keeps Microsoft 365 customer data in a limited-function account for 90 days after a subscription ends and deletes it no more than 180 days after expiration or termination. Source
- Salesforce's security, privacy and architecture documentation lets customers request return of their data within 30 days after contract termination, after which data is held inactive and then deleted. It also reserves the right to reduce that retention period. Source
- Atlassian's cloud licensing terms describe permanently deleting a paid site's data 60 days after the subscription ends or is cancelled. Source
- The 2023 BorgWarner and PHINIA transition services agreement capped services at 12 months with limited extension and required data to be expunged from systems on expiry. Source
- The 2024 Jacobs and Amentum transition services agreement required a backup during data migration, preserved for 90 days after notice of completed transmission. Source
- The IRS advises keeping records until the period of limitations expires, generally three years, seven years for bad debt or worthless securities claims and at least four years for employment tax records. Source
- Rev. Proc. 98-25 requires machine-sensible records to be kept while material, reconcile to books and returns, and come with record format and field documentation; retention limitation agreements do not cover later-acquired subsidiaries. Source
- Federal Rule of Civil Procedure 37(e) addresses loss of electronically stored information that should have been preserved when reasonable steps were not taken; notes say perfection is not required. Source
- IFRS 3 requires acquisition-related costs to be expensed in the periods incurred, except costs to issue debt or equity securities. Source
See if your company qualifies
A short company assessment. No data uploads are needed.