SaaS Exit Plan Checklist: How to Leave a Software Tool Without Losing Data

Nobody signs up for a subscription tool planning to leave it. That is why leaving can end up improvised: the renewal date is close, the new tool is already chosen, and someone realizes that three years of records sit inside an account with no obvious "download everything" button.

An exit plan is a short document, written before you need it, that answers one question: if we had to stop using this tool in 90 days, how would we do it without losing anything we need? This checklist walks through building one and running it. For background on how subscription software works, see our explainer on what software as a service is.

This is general information, not legal advice. Contract terms and data-protection rules differ by vendor and jurisdiction, so have a qualified adviser review anything high-stakes.

Why plan the exit at all?

• Switching is a normal event. Teams outgrow tools, vendors change plans or prices, and companies merge. Planning for it is routine risk management.
• Your leverage is highest early. Before you sign, you can ask for export options and data-return terms. After you cancel, you are asking for a favor.
• Data you cannot read is data you have lost. An export that nobody has opened is not a backup.

Phase 1: Know what you have (do this now, not at the end)

1. Name the system of record. For each important tool, write down what it is the official home of: customer records, support history, project files, notes, invoices. If the tool holds the only copy, it is a system of record and needs the most careful exit plan.

2. List the data types. Go beyond the obvious tables. Typical categories include:

• Core records (contacts, tickets, tasks, documents)
• Attachments and uploaded files
• History (comments, activity logs, status changes, version history)
• Configuration (custom fields, templates, automations, permissions)
• Users and their roles
• Reports and saved views

Configuration is easy to overlook. A raw export of records may not include the rules and templates that made the tool work for you.

3. Find the export options. Look in the product's settings and help documentation for what each export includes, which formats it offers, whether it is self-service, and whether limits apply. If the documentation is unclear, ask the vendor in writing. Our guides on CRM software and note-taking apps illustrate how different the data in each category can be.

4. Check the contract. Read the sections on termination, data return, and data deletion. Write down:

• How much notice you must give to end the agreement.
• Whether data remains available after termination, and for how long.
• Whether the vendor deletes data after termination and how it confirms that.
• Any fee for exporting data or for professional help with migration.

Phase 2: Know your rights

If your tool holds personal data about people in the European Union, the General Data Protection Regulation may apply, and two of its provisions are relevant to exits. This is a summary, not a legal analysis.

• Data portability (Article 20). In certain situations, a person has the right to receive the personal data they provided to a controller in a structured, commonly used, and machine-readable format, and to transmit it to another controller. The right applies where processing is based on consent or on a contract and is carried out by automated means. It is a right of the individual about their own data, so it does not by itself guarantee that your business can export everything in a tool.
• Processor obligations at the end of services (Article 28). The contract between a controller and a processor must provide that, at the controller's choice, the processor deletes or returns all personal data after the end of the services, and deletes existing copies unless law requires storage.

If these rules might apply to you, check whether your vendor's agreement includes a data processing addendum covering return and deletion, and ask your adviser how the rules apply to your situation. Outside the EU, other privacy laws may contain comparable provisions; the names and details vary.

Phase 3: Prepare the migration

5. Pick the destination first. Do not cancel anything until the new tool is chosen and tested. Our comparisons, such as the project management software comparison, can help you shortlist.

6. Map the fields. Create a simple table with the old tool's fields on the left and the new tool's on the right. Mark fields that have no equivalent, fields that must be merged or split, and values (such as status names) that need translating. Mistakes in the field map carry straight into the new system, so check it carefully.

7. Decide what not to move. Not all history deserves a place in the new system. Agree in advance what to archive in a readable format and what to leave behind. Document the decision.

8. Do a test migration. Move a small, representative sample and compare it to the original. Check that links, attachments, dates, time zones, and user assignments survive. Fix the mapping, then repeat before moving everything.

9. Plan the cutover. Choose a window with low activity. Decide whether the old tool becomes read-only on a set date so that changes do not slip in after the export. Tell users exactly when to stop entering data in the old system and where to enter it instead.

Phase 4: Export and verify

10. Take the full export while the account is active. Do not wait until the last day. Exports may be slow, rate-limited, or incomplete on first try. Download more than once if the product allows it, so you can compare runs.

11. Open the files. Check row counts against the numbers in the tool's interface, spot-check records, and confirm that special characters, long text, and dates display correctly. Make sure attachments are present, not just links to them.

12. Store the export safely. Keep the files in an access-controlled location that your team controls, with a clear name and date. If the export contains personal or confidential data, limit who can open it and decide how long it will be kept. A copy that sits in an unmanaged folder forever is its own risk.

13. Capture what the export misses. Take screenshots or written notes of configuration: automations, templates, permission settings, integrations, and scheduled reports. This is the knowledge you would otherwise have to rebuild from memory.

14. Record your integrations. List every other tool connected to this one: single sign-on, accounting, email, chat, and any automation connectors. Each connection needs to be switched to the new tool or turned off. Our overview of connecting business apps explains how these links usually work.

Phase 5: Switch and cancel

15. Run both systems briefly if you can. A short overlap lets you catch missing data before the old account disappears. Check what the overlap costs against the risk.

16. Give notice in the way the contract requires. Use the method and the address the agreement specifies, keep a copy, and ask for written confirmation of the end date. Cancelling inside the product when the contract requires an email, or the other way around, may leave you on the hook for another term.

17. Remove access. Revoke user accounts, API keys, and connected-app permissions. Remove the vendor from single sign-on. Change shared passwords the vendor's staff or integrations could have used.

18. Cancel payment methods carefully. Stop the subscription itself rather than only removing the card, and verify that no further charges appear on the next statement.

Phase 6: After the exit

19. Request deletion and confirmation. Ask the vendor in writing to delete your data after the retention period in the agreement, and to confirm when it has done so. If personal data is involved, ask your adviser what confirmation you should keep.

20. Update your records. Mark the tool as ended in your subscription tracker, note the date, and store the contract, the notice, and the confirmation together. If you do not have a tracker yet, see our guide to building a SaaS renewal date tracker.

21. Hold a short retrospective. Within a few weeks, ask the team what was lost, what took longer than expected, and what you would do differently. Fold the answers into the exit plans for your other tools.

A one-page template

For each important tool, keep a single page with these headings:

• Tool and owner
• What it is the system of record for
• Data types and where each can be exported
• Export format and who runs it
• Contract notice period and method
• Data return and deletion terms
• Connected tools
• Likely destination options
• Last time we tested an export (date)

The last line matters. A tested export is the only proof that your exit plan works.

Common mistakes

• Cancelling before the export is verified. Some accounts close or lock on cancellation.
• Exporting records but not attachments or history.
• Forgetting configuration and automations.
• Leaving integrations and API keys active after the switch.
• Assuming deletion happens automatically without asking for confirmation.

For a practical inventory before you switch tools, see our SaaS renewal date tracker spreadsheet guide and questions to ask a SaaS vendor.

Sources

• GDPR Article 20 (Right to data portability): https://gdpr-info.eu/art-20-gdpr/
• GDPR Article 28 (Processor), provision on deletion or return of personal data at the end of services: https://gdpr-info.eu/art-28-gdpr/

Note for reviewer: no statistics, prices, quotes or named people. The only checkable claims are the two GDPR articles summarized above; everything else is process advice.