Before you cancel software subscriptions: export and preserve your records

Why do records get lost when a subscription ends?#

Records get lost when a subscription ends because the renewal date, not the export, drives the timeline. Finance declines a renewal to cut cost, and the team that used the tool learns later that its history went with it.

Vendors handle closed accounts differently. Some keep data for a period and then delete it, some downgrade the account to read-only, and some delete on a schedule written into the terms of service. The details sit in the contract and the help center, so read both before giving notice.

Exports also look more complete than they are. A file of ticket summaries or contact records can omit the conversation threads, comments, attachments and change history that explain what actually happened.

The pre-cancellation checklist#

The pre-cancellation checklist applies to any SaaS tool that holds business records, from a help desk to a project tracker to a field service app. Work through it with the tool's administrator and the business owner of the records at the same table.

• 1Name the business owner of the records and the administrator who will run the export.
• 2Read the contract and help center for export options, plan limits and what happens to data after cancellation.
• 3List every object the tool holds: records, comments, attachments, users, custom fields, tags and workflows.
• 4Choose formats that preserve structure, such as JSON or database exports where offered, not only CSV summaries.
• 5Download attachments and inline files separately if the main export only links to them.
• 6Export audit logs, change history and permission records where the plan allows.
• 7Capture configuration: field definitions, picklists, automation rules and templates that explain the data.
• 8Verify counts and spot-check records from different years against the live system.
• 9Store the archive in company-controlled storage with an index and access rules.
• 10Get the owner's written sign-off, then set the cancellation date.

Which export formats keep records usable?#

Export formats keep records usable when they preserve the relationships between items, such as which comment belongs to which ticket and which file belongs to which project. Flat CSV files often break those links or cut off long text fields.

Attachment links deserve a separate check. Many exports reference files by URL, and those URLs can stop working once the account closes. Download the files themselves and keep the mapping between each file and its record.

Do audit logs and change history need their own export?#

Audit logs and change history usually need their own export, because they record who did what and when, and that sequence often matters more than a record's final state. A ticket's closed status says little; the reassignments, escalations and replies show how the work was done.

History may be available only on certain plans or for a limited look-back period, and some tools keep logs in an admin area separate from the main export. Check the vendor's documentation for each tool, and export what the plan allows before any downgrade changes it.

How long do vendors keep data after you cancel?#

Vendors keep data after cancellation for whatever period their own terms set, and that period varies widely by vendor and plan. Some offer a grace window to export, some delete promptly, and some hold backups for a time but will not restore them for a former customer.

Published vendor policies show how wide the range is. Atlassian says a cancelled cloud site stays accessible for 15 days after the subscription period ends before deactivation, and that unsubscribing from all Jira products on a site deletes the Jira data immediately. Help Scout says the account becomes inaccessible as soon as Delete Account is clicked and data is permanently deleted 60 days after cancellation. Pipedrive says a closed paid account is scheduled for permanent deletion within 180 days, with no access after cancelling.

Other vendors are more forgiving, at least on paper. Intuit's Canadian help page says cancelled QuickBooks Online data stays read-only for one year. monday.com keeps data by default after cancellation but says it cannot guarantee this indefinitely. Zendesk also asks for notice of intent to cancel at least 30 days before the term ends. These policies change, so check the current page for each tool you hold.

Treat any window as a safety margin, not a plan. Ask the vendor in writing how to export after notice, whether read-only access continues and when deletion happens, and file that answer with the archive.

Integrations add another wrinkle. A help desk or project tool often pushes data into other systems, such as a CRM, a data warehouse or a reporting tool, and those copies may survive the cancellation in partial form. Note them in the index, but do not treat them as the archive, because they rarely hold the full record.

Who should sign off before cancellation?#

The business owner of the records should sign off before cancellation, not only IT or finance. The head of support signs for the help desk, the controller for accounting tools and the project director for a project tracker.

Sign-off should confirm three things: the export was verified, no legal hold or open dispute requires the live system, and the archive location and access rules are written down. Counsel should confirm holds, because a hold can require keeping records in a specific form or system.

Illustrative: an architecture firm consolidates its tools#

Illustrative: a fictional architecture firm is moving project work into Procore and SharePoint and plans to cancel a standalone RFI tracker, an older project management tool and a legacy file-sharing service. Finance has already set the renewal dates; the operations director asks for exports first.

The RFI tracker's CSV export lists RFIs but not the attached markups or reply threads, so the administrator runs a full JSON export and downloads attachments project by project. The project management tool keeps task history only on its higher plan, so the firm exports that history before downgrading. Each project principal signs off, and the archive goes to company storage indexed by project number.

One tool is held back. A client dispute is open on a project whose files live in the file-sharing service, and counsel asks for that account to stay active until the hold is lifted.

How SourceX looks at pre-cancellation archives#

Archives exported before cancellation are often the only remaining copy of years of support, project or job history. SourceX treats them as possible Supply, the first stage of the SourceX five-step transaction: the fit check uses metadata such as the tool, the years covered and the record types, and nothing is shared during that first assessment.

Large archives stay in the company's own storage. If one proceeds, the Rights and Preparation steps check vendor terms, customer contracts and personal details before the company approves any delivery.