SaaS offboarding checklist: what to export before canceling any tool

Why does canceling a tool need a checklist?#

Canceling a SaaS tool needs a checklist because the person who cancels it is rarely the person who knows what it holds. Finance sees the invoice, IT sees the login, and only the team that used the tool every day knows which history matters.

Most tools also hold more than one kind of record. The main export often covers current records but skips file attachments, closed or archived items, comment threads, audit logs and the settings that explain how fields were used. After the subscription ends, rebuilding any of them may be impossible.

The same ten steps work for a large help desk and for a small survey app that nobody remembers buying. Only the effort changes.

The ten-step SaaS offboarding checklist#

The ten-step SaaS offboarding checklist runs from a full export to cancellation, in order, with a single owner for each step. Steps one to nine happen while the tool works normally; step ten removes your ability to fix anything you missed.

Integrations deserve more care than they usually get. A tool that feeds another system, such as a form app that creates CRM leads or a help desk that posts alerts to chat, can fail silently once canceled, and the downstream team notices only when records stop arriving.

• 1Full record export: every object the tool holds, including archived, closed and recoverable deleted items, in the most complete format offered.
• 2Attachments and files: documents, photos and recordings linked to records, with a way to match each file back to its parent record.
• 3Audit and activity logs: sign-ins, record changes and admin actions, which some plans keep only for a limited time.
• 4Users and roles: who had access, in what role and whether they are current staff, so records written by former employees stay readable.
• 5Configuration: custom fields, picklist values, workflows, templates and automation rules that explain what each field meant.
• 6Integrations: connected apps, API keys, webhooks and scheduled syncs, so nothing breaks or keeps sending data after the tool goes.
• 7Verify: compare record counts, date ranges and a sample of full records with the live system.
• 8Store: move the export into company-controlled storage with an owner, access rules and a retention period.
• 9Document: write a one-page offboarding record listing what was exported, where it is and who checked it.
• 10Cancel: give notice, revoke integrations and get written confirmation that the account is closed and how data will be deleted.

Where does each type of tool hide its records?#

Each type of tool has its own blind spots, and the table shows where they usually are. A test export and the vendor's documentation will show the real ones for your plan.

Chat tools need a policy decision as well as an export, because private channels and direct messages raise privacy and employment questions that differ from shared business records.

How do you verify an export before canceling?#

Verification is the proof that an export and the live system agree on record counts, date ranges and content. Compare totals per object and per year, check the earliest and latest dates, and open sample records in both places to confirm comments, attachments and links came through.

Choose samples on purpose: the oldest record, the newest, one with many attachments and one edited by a former employee. Those are where exports most often break. Note any gap you decide to accept in the offboarding record.

Open the export with a different program from the one that made it. A file that only the vendor's own app can read is not much of an archive once the subscription ends.

Who signs off before the tool is canceled?#

The tool owner, IT, finance, legal or privacy and the COO each sign off on one part before a tool is canceled. That short sign-off prevents the most common failure: finance cancels a renewal to save cost while the team assumes someone else exported the history.

Time the sign-off against the contract, not the budget cycle. The notice deadline in the order form often falls well before the renewal date, so the export and its verification must be complete before that deadline rather than before the last day of service.

Illustrative: a 3PL retires its ticketing tool#

Illustrative: a fictional third-party logistics company moves customer requests from a standalone ticketing tool into its warehouse management system's client portal. Finance flags the ticketing renewal for cancellation.

The checklist shows that the standard export holds ticket fields but not attachments such as damage photos and bills of lading, and that the tags used to classify exceptions sit on a separate settings page. The systems lead pulls attachments through the API, maps each file to its ticket ID, saves the tag list and audit log, and checks counts by year.

The COO signs off, finance gives notice before the renewal date, and the archive is stored with an owner and a retention rule. Short-shipment and damage claims from past years can still be traced when clients raise them.

Where SourceX fits in an offboarding#

An offboarding is also the last easy moment to ask whether a tool's history is worth more than storage. Ticket threads, CRM activity and job records that end in an outcome can be licensable, and judging them is far harder once the account is gone.

SourceX begins with a description, not a file: system name, years of history, record families and known restrictions. That is the Supply step of the SourceX five-step transaction, and the SourceX Enterprise Data Value Framework then helps rank which archives deserve a closer look before anyone chooses to keep, license or delete them.