Cancelling SaaS subscriptions in a wind-down: export checklist

What should you export before cancelling SaaS subscriptions?#

Before cancelling SaaS subscriptions, export the full history of every system that holds company records, not only the systems you expect to need again. In a wind-down the tools themselves are worth little, but the records inside them may be needed for tax filings, creditor claims, customer obligations and any later sale or license of company data.

The safest sequence is register, freeze, export, verify, assess and then cancel. A common way records are lost is a finance lead cancelling card payments in bulk to stop the spend, after which a tool quietly drops to a free tier or suspends the account before anyone has pulled its history.

• 1Register: list every paid and free tool, its admin, its billing owner and its contract terms.
• 2Freeze: pause auto-deletion rules, retention purges and seat removals that would erase content.
• 3Export: pull full history, attachments and audit logs from each system.
• 4Verify: check counts, dates and links against the live system.
• 5Assess: decide what must be retained, what could be licensed and what should be deleted.
• 6Cancel: end subscriptions in reverse order of dependence, with identity and email last.

Start with a subscription register#

A subscription register is the wind-down officer's control sheet for every tool the company pays for or signed up to. Build it from card statements, the accounts payable ledger, expense reports and the single sign-on app list, because each source catches tools the others miss.

Free tools and individual sign-ups matter as much as the large contracts. Engineering teams often run a free plan of a diagramming or testing tool, and sales teams sometimes keep call recordings in a product one manager put on a personal card.

System-by-system export checklist#

The system-by-system checklist below covers the tools most growing companies run, grouped by the job they do. For each one, export the history with its native IDs, so a ticket, a customer record and a code change can still be linked after the source system is gone.

Treat the identity provider, such as Okta or Google Workspace sign-in, and the company password manager as infrastructure rather than record systems. Keep both running until the last export is verified, because losing single sign-on or the stored admin credentials can lock you out of every tool on the list at once.

Why you should not cancel before the records are assessed#

Cancelling before assessment removes options that cannot be recovered later. Once a vendor deletes an account after nonpayment or termination, the history is usually gone for good, and an export taken in a hurry often lacks attachments, internal notes or the links that give records their meaning.

Assessment asks three separate questions of each system. What does law, contract or an open claim require you to keep? What were customers and employees promised about deletion? Do the records have value that should be preserved for creditors or shareholders? Directors and wind-down officers may owe duties to preserve the value of remaining assets, which counsel can confirm for your entity and state, and operating archives can be among those assets.

Downgrades deserve the same caution as cancellations. A move to a cheaper or free tier can cap visible history, remove audit logs or disable bulk export, so check the vendor's documentation for your plan before changing it.

How do you know an export is complete?#

An export is complete when it matches the live system on counts, dates and links, and when someone other than the person who ran it has opened a sample. Spot checks take far less effort than rebuilding a lost record after the account is closed.

• 1Record counts match the source system's own totals for tickets, deals, issues or messages.
• 2The date range runs from the first record to the last, with no gaps at old plan or migration boundaries.
• 3Native IDs are present, so tickets, accounts, issues and commits can be relinked.
• 4Attachments open, and file names map back to their parent records.
• 5A sample of threads reads correctly from start to finish, including internal notes.
• 6Two copies sit in company-controlled storage, with access limited to named custodians.
• 7An export log records who ran each export, when, from which plan, and any known gaps.

In what order should you cancel the tools?#

Cancel tools in reverse order of dependence: first the tools that hold no unique records, then each record system once its export is verified, and the identity provider, password manager and company email last. That order keeps admin access and password resets working until the final export log is signed.

Cancellation dates and renewal dates are different controls. On an annual plan the term is often prepaid, so the saving usually comes from sending non-renewal notice before the deadline in the contract, not from cancelling early, and the remaining paid term is time to finish exports.

• 1First: tools with no unique records, such as scheduling, design mock-up or survey tools, after a quick check that nothing is stored only there.
• 2Second: record systems such as the help desk, CRM, issue tracker, chat and docs, each one only after its export passes verification.
• 3Third: cloud infrastructure, after databases and storage buckets have been exported or deleted as contracts require.
• 4Last: password manager, identity provider and company email, once the custodian signs the final export log.
• 5Keep running: the company-controlled storage account that holds the archive, with billing that survives the wind-down.

Illustrative: a software company closes its tools in order#

Illustrative: a fictional route-planning software company decides to wind down after a financing round falls through. Its stack includes Zendesk, HubSpot, Jira, GitHub, Slack, Notion and Google Workspace, plus a call recording tool the sales lead paid for personally.

The wind-down officer builds the register from card statements and the sign-on app list, pauses Slack retention rules, and keeps Zendesk and Jira on their current plans for another billing cycle while full exports run. The call recording tool turns up only through an expense report; its recordings are exported and set aside for privacy review rather than mixed into the main archive.

A former employee has an open wage claim, so on counsel's instruction the Slack direct messages of the people involved are exported, stored separately under a legal hold and kept out of any licensing assessment. The support and engineering exports are checked against source counts, stored in two company-controlled locations and assessed before cancellation. Google Workspace is cancelled last, after the officer signs the final export log.

Where data licensing fits in the checklist#

Data licensing fits after verification and before cancellation, as part of the assessment step. Support conversations linked to resolutions, CRM histories with outcomes and issue trackers linked to code changes are the kinds of operational records AI developers license, and they are also the records most easily lost in a rushed shutdown.

SourceX approaches a wind-down through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The first step is a fit check on metadata only, such as system names, years of history and record families, so nothing leaves company storage during assessment. If a package proceeds, the company licenses the records rather than selling them, approves every step, and the transaction is documented in a SourceX Evidence Packet.