Systems and records
M&A vendor sunset data loss: prove the archive before access ends
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
To preserve tool history before an acquisition integration team cancels access, make cancellation a gated step. Prove the archive is complete (counts by year and entity match the live system), intact (checksums validate after transfer), usable (someone outside the export team can read it) and owned (the entity holding each record set is tagged). If access already ended, act inside the vendor's retention window, often weeks rather than months.
System export
M&A vendor sunset data loss
Key takeaways
- An export on a shared drive is not an archive until counts, checksums, links and readability have been tested.
- Vendor grace periods after cancellation are short and uneven, and some actions, such as explicitly deleting a Microsoft 365 subscription, remove data at once.
- Each cancellation ticket should cite a runbook ID with ten gates, each with pass evidence and a named signer.
- Tag every workspace or record set with the legal entity, contract and customer-data status, because shared tenants mix records the buyer does not hold.
- After a premature cancellation, ask for reactivation inside the retention window and write down what was lost; a new subscription does not bring deleted data back.
Why does history disappear when the integration team cancels a tool?
History disappears because the cancellation date and the archive check belong to different people. The integration team owns a synergy plan with a line for each duplicate subscription, while the person who knows what the acquired company's help desk, chat or project tool actually holds is often a departing administrator with no say over that date.
In that gap, an export gets mistaken for an archive. A file that exists on a shared drive proves only that something was downloaded. It does not prove that every year, every record type and every attachment came across, that the files survived the transfer, or that anyone outside the export team can open them.
Three losses repeat across deals: a partial export that left out attachments, internal notes or the audit log; an archive saved under the wrong legal entity or in a workspace due to be divested; and a format nobody can read once the source tool is gone. Each is cheap to catch while the subscription is live and expensive or impossible afterward.
How long do vendors keep an account's data after the end date?
Usually weeks to a few months, and some actions delete immediately. The table below summarizes what four vendors' own help pages said when checked on October 18, 2026. Treat it as a reason to read your own contract and the current vendor page, not as a schedule to plan around.
The contract can override the help page. Enterprise agreements sometimes add a longer data-return window, an extract service or a deletion certificate, and some only promise deletion. Pull the order form and the data processing terms for each tool before setting a date, and note the contractual window next to the vendor's published one.
Two patterns matter for integration plans. First, access often narrows before deletion: users lose access while an administrator can still sign in, so the archive check has to happen while that administrator still works for the group. Second, some steps skip the grace period entirely, such as explicitly deleting a Microsoft 365 subscription or unsubscribing from every Jira app on a site.
| Vendor | What the vendor says happens after the end date | Who can still reach the data | What removes data at once |
|---|---|---|---|
| Microsoft 365 for business | The subscription moves through Expired, Disabled and Deleted statuses; data left behind is deleted no later than 180 days after cancellation | All users while Expired; only admins while Disabled | Explicitly deleting the subscription deletes SharePoint and OneDrive content immediately |
| Zendesk | Deletion begins 90 days after cancellation, with product-specific timelines in the deletion policy | The account owner can request reactivation within the 90 days | The policy sets separate timelines per product; read the one for each product in use |
| Atlassian Cloud | A site is deactivated 15 days after the subscription period ends; paid plans keep data 60 days after deactivation, trials 15 | Reactivating within the retention period restores data | Unsubscribing from all Jira apps on a site deletes Jira data immediately |
| Slack | Export scope depends on plan: full exports including private channels and direct messages need a Business+ or Enterprise plan and an approved application | Workspace or org owners, within the plan's export rights | Without an approved full export, owners get only what their plan's export covers |
The pre-sunset archive verification runbook
The runbook turns cancellation into a gated step: a subscription is canceled only when every gate below has a pass and a named signer. Run it per system, give each run an identifier, and require the cancellation ticket in procurement to quote that identifier. If a gate cannot pass, the subscription stays live or the gap is written down and accepted by the person who owns the risk.
Gates one, two and eight are judgment calls that need the right person; the rest are mechanical tests anyone careful can run. Keep the evidence in the archive itself, next to the data, so it survives the people who produced it.
| Gate | Test | Evidence that it passed | Signer |
|---|---|---|---|
| 1. Scope frozen | The system, tenant, workspaces, legal entities and date range in scope are listed, including the earliest record date the live system shows | Inventory row with tenant ID, workspace list and earliest and latest record dates | Records owner at the acquired company |
| 2. Holds checked | Counsel confirms whether any litigation hold, regulatory retention rule or customer obligation touches the system | Dated note from counsel naming any hold and what it covers | Counsel |
| 3. Every object type exported | Records, comments and internal notes, attachments, users, custom fields, tags, audit or activity logs and configuration are each exported or listed as not exportable | Object checklist compared against the admin schema, with gaps marked | System administrator |
| 4. Counts reconcile | Record counts by year and by legal entity in the export match the live system's own reports, and any difference is explained | Reconciliation sheet: live count, exported count, difference, reason | System administrator and records owner |
| 5. Fixity proven | Every file has a checksum in a manifest, and the manifest validates again after the files reach group storage | Validation log showing a complete and valid package after transfer | Whoever moved the files |
| 6. Links resolve | A random sample of records is opened and each attachment, comment and related record resolves to its parent ID | Sample log with record IDs and pass or fail per link | Someone outside the export team |
| 7. Readable without the tool | A person who did not run the export finds and reads three named records using only the archive and its documentation | Short test note with the records found and the time taken | Future archive owner |
| 8. Authority tagged | Each workspace or record set carries the legal entity that holds it, the contract it came under, a customer-data flag and any carve-out boundary | Tag table attached to the archive | Integration lead with deal counsel |
| 9. Custody assigned | The archive sits in storage the surviving entity controls, with two named owners whose access was tested | Access list and a dated access test | IT owner for the surviving entity |
| 10. Release to cancel | All gates passed, or each failed gate has a written acceptance | Signed release quoting the runbook ID; the cancellation ticket cites it | Integration lead |
When should the runbook start, and who should own it?
Start the runbook when the integration plan is drafted, not when the cancellation notice is due. The plan's subscription list is the natural index: every line that ends in cancel, downgrade or merge gets a runbook ID before any date is committed, and the date is then set by whichever is later, the planned saving or the expected verification finish.
Give ownership to one person on the acquirer's side who will still be there in a year, usually someone in IT or records management, and pair them with the acquired company's administrator for each tool. The administrator knows where the old history hides; the owner makes sure the evidence ends up in group storage and that the cancellation waits for the release.
Budget the runbook in days of work, not in license months. Most of the time goes into gates three, four and six, and the largest single risk is the administrator leaving before those gates pass. If retention of that person is uncertain, run the export and reconciliation first and the paperwork after.
Which legal entity holds each workspace once the deal closes?
The entity that holds a record after closing depends on the deal structure and the contracts the tool sits under, so the archive has to record it rather than assume it. In a stock purchase the acquired company usually keeps its own accounts and contracts; in an asset purchase only the assets and contracts listed in the agreement move; in a carve-out the seller often keeps the subscription while the divested unit's records sit inside it.
Shared tenants are where the mistakes happen. A single help desk instance can hold tickets for a product line that was sold, a customer whose contract requires return or deletion of its data, and an affiliate that was never part of the deal. Tag the archive at the level where authority actually changes, usually workspace, brand, product line or customer account, and leave anything ambiguous untagged and flagged for deal counsel.
Customer data needs its own flag. Records that customers supplied under a service contract are governed by that contract's data terms, which may require return or deletion at the end of the relationship. For those records, the verification task becomes proving that the right data was returned or deleted, not that it was kept.
How do you prove the archive is complete rather than merely present?
Prove it with counts and checksums, not with a folder listing. Completeness has two parts: the export holds everything the live system holds for the scope, which gate four tests by reconciling counts by year and entity, and the files that arrived are the files that left, which gate five tests with a checksum manifest.
The BagIt packaging specification, published as RFC 8493, gives useful vocabulary for the second part. It calls a bag complete when every required element and every file listed in its manifests is present, and valid when it is complete and every checksum in every manifest has been verified against its file. It also offers Payload-Oxum, a byte and file count for quickly spotting an incomplete bag, while requiring full checksum validation before a bag is declared valid. Whether or not you use BagIt tooling, adopt the distinction: present, complete and valid are three different claims.
Counts by year catch the most common silent gap, which is old history that the live system stores separately. Archived tickets, closed projects and retired channels are often excluded from default exports, and a year-by-year comparison shows the missing years at a glance.
Audit and activity logs deserve their own line in the reconciliation. They show who changed a record and when, which is often what a later dispute, audit or analysis needs, and they are frequently exported by a separate job or kept for a shorter period than the records themselves. Configuration matters for the same reason: custom field definitions, status names and routing rules are what make an exported record readable once the tool is gone.
Worked example (illustrative): a help desk and chat workspace due for day-60 cancellation
This example is illustrative; the company, counts and percentages are invented to show how the runbook reads. An acquirer plans to cancel the acquired company's help desk and its chat workspace 60 days after closing, when both move to the group's tools.
Gate four fails first. The help desk export matches the live counts for the last four years but is missing about 11% of all tickets, all from the two oldest years, which the tool had moved to an archive store the default export skipped. A second export job closes the gap and the reconciliation sheet records both runs.
Gate six finds that about 4% of sampled tickets reference attachments that are not in the package, because inline images were exported as links to the vendor's servers. Those links will stop working at cancellation, so the files are fetched and the package is validated again.
Gate eight produces the exception. One chat channel and one help desk brand served a product line the seller kept under the purchase agreement. They are tagged to the seller's entity, excluded from the group archive and handed over under the transition arrangements instead. The chat plan's export rights also turn out to cover public channels only, so the integration lead decides whether to apply for a fuller export before downgrading, with counsel's input on the consent questions that raises.
Cancellation moves from day 60 to day 75. The 15 days are the whole cost of the runbook in this case.
What can you still recover if the subscription is already canceled?
Often something, if you move inside the vendor's retention window and ask before deletion starts. Contact the vendor's support with the account identifier, ask for reactivation or administrator access, and run the full runbook on whatever comes back. Zendesk says the account owner can request reactivation within 90 days of cancellation; Atlassian says reactivating within the retention period restores the app's data.
Do not assume a new subscription brings old data back. Microsoft states that adding a new subscription of the same type does not restore data associated with a deleted subscription. Record what was lost, when, and why, in the archive's evidence folder; an honest gap record is worth more to an auditor or a later buyer than an archive that implies completeness.
If litigation is reasonably foreseeable, the question changes. Under Federal Rule of Civil Procedure 37(e), a court can respond when electronically stored information that should have been preserved is lost because a party failed to take reasonable steps and it cannot be restored or replaced. The committee notes say the routine operation of a system may have to be interrupted when litigation is in prospect. Bring counsel in before anything else is deleted.
When should the cancellation wait, and when should the archive shrink?
Delay the cancellation when the cost of keeping the tool for a few more weeks is small compared with what an unverified archive could lose. Shrink the archive when keeping everything would break a customer contract or keep personal data with no purpose.
At a glance
When should the cancellation wait, and when should the archive shrink
- Wait: counsel has named a hold that covers the system, and the hold's scope is not yet reflected in the export.
- Wait: gate four or gate six fails and the vendor's grace period after cancellation is shorter than the time needed to fix it.
- Wait: authority over a workspace is unclear between buyer and seller, and the purchase agreement or transition services agreement does not settle it.
- Shrink: customer contracts require return or deletion at termination; verify deletion for those accounts instead of archiving them.
- Shrink: the tool holds personal data such as chat messages or HR threads that no retention rule or business purpose requires; decide with privacy counsel what to keep.
- Escalate: the archive is the only remaining copy of records the group may later want to analyze or license, because that decision depends on rights review the integration team cannot make alone.
A verified archive keeps a later licensing decision open
Years of tickets, project threads and operational records from an acquired company can have uses beyond compliance, including licensing selected records as AI training data. That option exists only if the history survives integration with its entity tags, contracts and evidence intact, which is exactly what the runbook produces.
Should a company later choose to license selected archived records to AI developers, SourceX runs the rights review, contracting, preparation and delivery around them. It begins with a short assessment that needs no data upload, and delivery waits until the company has approved the scope and terms and signed.
Frequently asked questions
How long do SaaS vendors keep data after a subscription ends?
It varies by vendor and plan. Microsoft says data left behind is deleted no later than 180 days after cancellation, Zendesk starts deletion 90 days after cancellation, and Atlassian keeps paid-plan data 60 days after a site is deactivated. Check your contract and the vendor's current page, because some actions, such as explicitly deleting a subscription, remove data immediately.
Does exporting data before canceling meet a legal preservation duty?
Not by itself. An export helps only if it captures what the duty covers, is complete and can be produced later. Where litigation is reasonably foreseeable, counsel decides what must be preserved and how, and routine deletion may need to be suspended.
Who should sign off before an acquired company's tool is canceled?
At minimum the records owner who knows the system, the administrator who ran the export, counsel for holds and entity questions, and the integration lead who owns the cancellation. The release should reference the verification evidence so the decision can be reconstructed later.
Can you get data back by buying a new subscription after deletion?
Generally no. Microsoft states that adding a new subscription of the same type does not restore data associated with a deleted subscription. Recovery is only realistic inside the vendor's grace or retention window, before deletion begins.
What is a checksum manifest, and why does an archive need one?
It is a list of every file in the archive with a cryptographic checksum of its contents. Validating the manifest after each transfer proves that the files that arrived are the files that left, which a folder listing cannot show.
Sources
- Microsoft says a Microsoft 365 for business subscription moves through Expired, Disabled and Deleted statuses, that only admins can reach data while Disabled, that explicitly deleting a subscription deletes SharePoint and OneDrive content immediately, that data left behind is deleted no later than 180 days after cancellation, and that a new subscription does not restore deleted data. Source
- Zendesk's Service Data Deletion Policy starts deletion 90 days after an account is canceled or terminated, with product-specific deletion timelines after that. Source
- Zendesk says the account owner can request reactivation of a canceled account within 90 days. Source
- Atlassian says a subscription is deactivated 15 days after the current period ends, that paid plans keep data 60 days and trials 15 days, and that reactivating within that period restores data. Source
- Atlassian says unsubscribing from all Jira apps on a site deletes the Jira data immediately. Source
- Slack says exports that include private channels and direct messages are available on Business+ and Enterprise plans and require owners to apply. Source
- The BagIt specification (RFC 8493) defines a complete bag and a valid bag, describes payload manifests with checksums and Payload-Oxum, and requires checksum validation before a bag is declared valid. Source
- Federal Rule of Civil Procedure 37(e) addresses lost electronically stored information that should have been preserved, and its committee notes say the prospect of litigation may call for intervening in a system's routine operation. Source
See if your company qualifies
A short company assessment. No data uploads are needed.