Preserve records before you cancel SaaS subscriptions: a shutdown order of operations

The order of operations at a glance#

The order of operations runs in five phases, and each system passes through all of them before its cancel date. The table works as a register: one row per system, one owner per row, and a retention window confirmed from the vendor's own terms rather than memory.

Build the register from the accounts payable ledger and the company card statements, not from memory. Tools bought on individual cards, free plans that still hold records and integrations installed by former employees rarely appear on an IT list, and they are where unexpected records surface.

Phase one: freeze deletions and map dependencies#

Phase one stops anything that deletes records automatically while the plan is built. Retention policies in email and chat, auto-archive rules in help desks and offboarding scripts that remove accounts can all destroy records quietly during a wind-down.

Map dependencies at the same time. Single sign-on controls access to most tools, integrations break when their source system closes, and password resets for every vendor arrive at company email addresses. Any system that other systems depend on gets cancelled late.

Phase two: secure admin access before layoffs#

Phase two secures admin access before the people who hold it leave, because a lost login is harder to recover than a cancelled subscription. In many companies a single engineer or office manager is the only admin for several systems.

• 1Add a second company-controlled admin to every system that holds records.
• 2Move multi-factor authentication off personal phones to company-held devices or a shared vault.
• 3Record billing owners and the card or invoice each subscription runs on.
• 4Check auto-renewal dates so no plan renews into a long term or lapses unnoticed.
• 5Transfer file ownership before deleting any user account in Google Workspace or Microsoft 365.

Phase three: export and verify#

Phase three exports each system and verifies the export against the live system before anything else happens. Verification is the step most often skipped, and it is the one that catches missing attachments, truncated history and broken links between records.

Check record counts by year, open a sample of exported records next to the originals, confirm that attachments and comments came through, and make sure the identifiers that link systems survive, such as ticket numbers referenced in Jira issues or CRM account IDs on invoices. Store exports in company-controlled storage with access limited to named people.

Prefer each vendor's own export features over third-party tools that pull data through APIs. According to a Hunton Andrews Kurth client alert, Slack's API terms were changed effective May 29, 2025 to prohibit bulk exporting of data through its APIs and creating persistent copies or archives, so an archiving app that worked in the past may no longer be a permitted route.

Phase four: assess before you decide#

Phase four assesses each export before the cancel decision, because three different obligations meet here: records the law requires you to keep, records contracts require you to delete or return, and records that may be worth licensing.

Apply the rules in the order shown. A legal or contractual obligation always outranks a licensing opportunity.

What vendors say happens to data after cancellation#

Vendor terms on data after cancellation range from immediate loss of access to a long read-only window, which is why the register needs each vendor's own wording rather than an assumed grace period. The examples below come from vendor terms and help pages as published; policies change, so re-check them before setting a cancel date.

Two patterns matter most. Some vendors cut off access at termination even if the data sits on their servers for a while longer, and some charge or require a written request from the account owner for a full backup. Both are easy to handle before cancellation and hard to handle after.

Phase five: cancel in reverse dependency order#

Phase five cancels systems in reverse dependency order, with the most connected systems last. Standalone tools go first once their rows are closed; help desks, CRMs and trackers follow; chat and file storage come next; single sign-on, email and the domain go last.

Keep the domain registered and email forwarding active for a period after everything else is gone. Vendors send deletion confirmations, final invoices and account notices to company addresses, and a lapsed domain can let someone else receive them.

Cancel payment methods after the subscriptions they fund, not before. A card closed early turns a planned cancellation into a failed payment, and some vendors suspend or delete accounts on non-payment faster than on a normal cancellation.

Illustrative: an engineering firm sequences its shutdown#

Illustrative: a fictional structural engineering firm is closing after its principals retire. Its records span Deltek Vantagepoint for projects and billing, Procore for RFIs and submittals, Bluebeam sessions for markups, and Microsoft 365 for email and files.

The original plan cancels everything at month end and deletes staff accounts as people leave. The operations manager instead freezes deletions, adds a second admin to each system, and exports Procore and Bluebeam history with attachments first. The assessment separates client deliverables, which stay with the firm's records custodian under its professional obligations, from internal review comments and RFI resolution histories, which are held for a licensing assessment.

Microsoft 365 and the domain stay active until the final exports are verified and the custodian confirms receipt.

Where SourceX fits in the sequence#

SourceX fits into phase four. A metadata-only fit check covering systems, years of history and record families tells the company whether any exports are worth holding for licensing, and nothing leaves the company at that stage.

If a package proceeds, the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery) works from the verified exports rather than the live systems, so subscriptions can close on the planned schedule.