Cancel a SaaS platform your business uses
Cancelling a SaaS platform can delete data, break website forms and automations, and leave DNS records that let someone take over your subdomain. Export, disconnect and clean up in the right order.
Official sources last reviewed · How we review
Check what cancelling would affect
A few questions, revealed as they become relevant. Your answers stay in this browser.
Start with the basics
Optional. Product names only.
We never ask for phone numbers, card numbers, passwords or codes. Names of providers or nicknames are enough.
Your plan so far
8things this change touches
- critical1
- high4
- moderate3
- low0
Updates as you answer. Every item will explain why it’s there.
What could break
In a typical saas platform plan, these are the most serious things to get right.
Export all your data in a format you can use
Critical · Data & files
Customer records, history and settings could be gone for good once the account is deleted.
DNS records pointing at the platform (custom domains)
Critical · Website & DNS
Your subdomain could serve someone else's content, which can be used for phishing that looks like it comes from you.
Annual contract: check the renewal date and notice period
High · Subscriptions & billing
Miss the notice deadline and you could be billed for another full term.
Keep an owner or admin login until the very end
High · Sign-in & recovery
If the only admin leaves or loses access, you can't export, cancel cleanly or prove the account closed.
Attachments, files and message history
High · Data & files
Contracts, images and email threads attached to records disappear even though the records were exported.
Migrate data into the replacement and test it
High · Data & files
You find gaps after the old platform is gone and can't go back for the missing data.
Automation tools (Zapier, Make): turn off or re-point workflows
High · Integrations & APIs
Other systems silently stop receiving data, or you get a stream of error alerts.
Marketplace apps and plugins: disconnect them and cancel their billing
High · Integrations & APIs
Other systems silently stop receiving data, or you get a stream of error alerts.
Embedded forms, chat and widgets on your website
High · Website & DNS
Customers fill in forms or start chats that nobody receives.
Links in emails, invoices and documents: replace them
High · Website & DNS
Customers hit error pages and can't book, pay or log in.
Before and after you cancel
Before you cancel
- Annual contract: check the renewal date and notice period
- Keep an owner or admin login until the very end
- Export all your data in a format you can use
- Attachments, files and message history
- Download your invoices and receipts from the provider
- Shared links and public files
- Migrate data into the replacement and test it
- Users and licences
- Tell customers if anything they use is changing
After you cancel
- Automation tools (Zapier, Make): turn off or re-point workflows
- Marketplace apps and plugins: disconnect them and cancel their billing
- Embedded forms, chat and widgets on your website
- Links in emails, invoices and documents: replace them
- Webhooks
- Cancel the subscription and stop auto-renewal
- DNS records pointing at the platform (custom domains)
- Email sending records (DKIM, SPF, return-path)
- Single sign-on app and user provisioning
- Check nothing still depends on the platform
- Ask for written confirmation that your data was deleted
- Watch for charges after cancelling
Your own plan adds or removes items based on your answers, and explains why each one is there.
The safe order
Doing things in the right sequence is what keeps you from getting locked out halfway through.
Before the change
Step 1: Check the contract and keep admin access
Know the renewal deadline and make sure you can still sign in at the end.
- Annual contract: check the renewal date and notice period (high risk)
- Keep an owner or admin login until the very end (high risk)
Step 2: Export everything you need to keep
Data, attachments, logs, financial records and invoices, while you still have full access.
- Export all your data in a format you can use (critical risk)
- Attachments, files and message history (high risk)
- Download your invoices and receipts from the provider (moderate risk)
- Shared links and public files (moderate risk)
Step 3: Move data and tell people
Migrate and test the replacement, and tell users and customers what's changing.
- Migrate data into the replacement and test it (high risk)
- Users and licences (moderate risk)
- Tell customers if anything they use is changing (moderate risk)
During the change
Step 4: Disconnect integrations and customer-facing features
Nothing should depend on the platform by the time you cancel.
- Automation tools (Zapier, Make): turn off or re-point workflows (high risk)
- Marketplace apps and plugins: disconnect them and cancel their billing (high risk)
- Embedded forms, chat and widgets on your website (high risk)
- Links in emails, invoices and documents: replace them (high risk)
- and 1 more
Step 5: Cancel the subscription
Get written confirmation of the cancellation and its effective date.
- Cancel the subscription and stop auto-renewal (high risk)
Immediately after
Step 6: Remove DNS records and the sign-in connection straight away
Leftover records for a cancelled service can let someone take over your subdomain.
- DNS records pointing at the platform (custom domains) (critical risk)
- Email sending records (DKIM, SPF, return-path) (high risk)
- Single sign-on app and user provisioning (moderate risk)
Verify
Step 7: Check nothing still depends on it
Test forms, links and automations the way a customer or colleague would.
- Check nothing still depends on the platform (high risk)
Later
Step 8: Confirm deletion and watch for charges
Close the loop on your data and your billing.
- Ask for written confirmation that your data was deleted (moderate risk)
- Watch for charges after cancelling (moderate risk)
Why this change needs a plan
Business software rarely stands alone. It's embedded in your website, connected to other tools, sending email as your domain and holding records you may need to keep. Cancelling without unpicking those ties breaks things customers see and leaves loose ends behind.
Data is the first risk. Exports often leave out attachments, history and logs, and after cancellation the provider will eventually delete what's left. The second risk is what's pointing at the platform: website forms, automations, links in old emails, and DNS records for custom domains.
The safe order is to check the contract, export and migrate, disconnect everything that depends on the platform, cancel, and then remove DNS records, sending records and the single sign-on connection straight away.
Why it matters
A cancelled platform can take data, customer-facing features and integrations with it. Leftover DNS records can also let someone else take over a subdomain that customers trust.
What makes it risky
Risk is highest when the platform holds data you must keep, when it's on an annual contract with a notice period, and when a custom domain or subdomain points at it. Customer payments that run through the platform add another critical dependency.
Common mistakes
- Cancelling before exporting attachments, invoices and history that the standard export leaves out.
- Missing the notice deadline on an annual contract and being billed for another year.
- Leaving a CNAME like help.yourdomain.com pointing at the cancelled service.
- Forgetting website forms and widgets that keep accepting submissions nobody receives.
- Leaving automations and marketplace apps running, failing, and sometimes billing separately.
Frequently asked questions
What happens to my data when I cancel a SaaS subscription?
It varies by provider. Many keep data for a period after cancellation and then delete it; some delete sooner. Verify the provider's current retention/cancellation policy and export everything before you cancel.
What is a subdomain takeover?
If a DNS record such as a CNAME still points at a service you've stopped using, someone else may be able to claim that hostname on the service and show their own content on your subdomain. Removing the record when you cancel prevents it.
Do I need to give notice to cancel an annual SaaS contract?
Often, yes. Many annual and multi-year contracts renew automatically unless you give notice by a set date, sometimes in writing. Check your contract or order form for the renewal date and notice terms.
Should I revoke API keys when cancelling?
Yes. Revoke keys and tokens in the platform before the account closes, and remove them from your code, servers and secrets storage so nothing keeps calling a service you've left.
How do I know the provider deleted our data?
Ask for written confirmation of deletion, referring to your data processing agreement or terms, and keep it with your records. Some providers have an in-app deletion request for this.