You checked how to get into your cloud software. Did you check how to get out?
Keep up with IT Club
Add IT Club as a preferred source in Google Search.
A practical guide to SaaS exit planning for UK small businesses: check data exports, attachments and history, contract end dates, access, deletion, migration help and the workarounds you would need if a critical service became unavailable.
Signing up for cloud software is usually easy.
Choose a plan. Enter payment details. Create some users. Import your data. Off you go.
Leaving can be rather more interesting. The worst time to discover that you cannot easily export your data is after you have fallen out with the company holding it.
The short version
Before an important system becomes part of daily operations, find out what you can take with you, how long you can access it, what happens to your information when the service ends, and how the business would keep working during a move. Then test the export while the supplier relationship is still healthy.
Most businesses now depend on SaaS
Software as a Service — SaaS — sounds technical. In practice, it is the subscription software many businesses use every day. You access it online; another company operates the service.
- Customer relationship management (CRM)
- Accounting and payroll
- Human resources
- Cloud backup and file storage
- Project and document management
- Email security
- Marketing platforms
- AI tools
- Industry-specific software
That arrangement can be convenient. It also means your work, records and day-to-day processes can become dependent on a service outside your direct control. Even familiar business apps belong on your cloud-services list.
What counts as a cloud service? →
The important question is not only “Does it work?”
When choosing software, businesses sensibly ask whether it does the job, what it costs, whether it connects to existing systems and whether staff can use it. There is another question that is easy to leave until later:
What happens when we want to leave?
You might want to move because the price rises, service quality changes, a better product appears, an important feature disappears, ownership changes, the relationship breaks down, a billing issue arises, service is interrupted or the supplier stops operating.
At that point, a software decision can become a business-continuity problem. The technical dependency may need attention before a contractual disagreement is resolved.
Can you actually get your information back?
You may expect your customer records, documents or accounts information to remain yours. But the practical question is whether you can retrieve it in a form you can use.
“Yes, you can export your data” is not the same as “the export contains what we need and another system can use it.” Ask whether an export includes:
- Attachments and uploaded files
- Historical records and previous communications
- Custom fields, tags and notes
- Audit trails and timestamps
- Metadata and the relationships between records
- User, role and configuration information needed to rebuild the service
Find out the format, how long the export takes, who is allowed to request it, whether it costs extra and whether you can repeat it without the supplier doing manual work. A sample export is more useful than an untested promise: open it, check the contents and see whether the data still makes sense outside the product.
Data ownership does not automatically mean simple data portability. Product features, the agreement and the type of information all matter.
One legal point is easy to misread: the UK GDPR right to data portability belongs to individuals and covers certain personal data in specific circumstances. It is not a blanket company right to export every commercial or operational record from every SaaS platform. For a contractual dispute or a question about your obligations, take appropriate legal advice.
ICO guidance: the right to data portability →
What happens when the agreement ends?
Check the exit process before you need it. For the service you are considering, find out:
- How long you can sign in and retrieve information after cancellation
- When the provider removes your active data
- How long copies may remain in backups or archives
- Whether you can request a deletion confirmation
- Whether migration help is available and what it costs
- Which integrations, automations or connected accounts will stop working
The exact answers depend on the product and the agreement you accepted. Keep a copy of the relevant terms and service details somewhere the business can reach if the platform account is unavailable.
Could access be interrupted during a dispute?
A disagreement about an invoice, renewal or service delivery has a contractual side and an operational side. What the provider may do depends on the terms and circumstances; do not assume that every supplier can suspend a service, or that access will necessarily remain available while a disagreement is resolved.
For a critical CRM, ask what staff would do if they temporarily could not sign in. Could they find essential customer contacts and previous conversations? Could they continue urgent support cases, prepare quotations or retrieve records? Would they have a recent export, and would it be accessible to an authorised person outside the provider account?
You do not need to expect a dispute. You do need to understand what the business relies on and what the fallback is.
Do not let auto-renewal make the decision for you
Some SaaS services have a minimum term, renew automatically or require notice before a renewal date. Those terms are not automatically unreasonable, but someone in the business should know:
- When the agreement renews and what notice is required
- Who owns the supplier relationship
- Where the agreement and account details are stored
- Whether the price or included features may change at renewal
- What the business would need to do if it decides not to renew
A forgotten renewal should not become your cloud strategy.
What if the provider or product disappears?
It does not have to end in an argument. Suppliers can be bought, products can be discontinued and companies can stop operating. If a platform that matters to you changes or disappears, the useful questions are how quickly you can retrieve the information, where it can go next and how long the business can manage without the usual service.
Many organisations have a plan for recovering servers, but no equivalent record of how they would leave their most important SaaS applications. These guides cover related recovery and supplier risks:
Before buying SaaS, ask the exit questions
You do not need to turn every £20-a-month application into a six-month procurement project. Be proportionate. The more important the platform is to your business, the more carefully you should check:
| Area | Questions to answer |
|---|---|
| Data | What will we store? Can we export it? In what format, and does the export include files, history and the details we need? |
| Access | Who controls the account and administrator access? What happens to access when the agreement ends or an account is interrupted? |
| Agreement | Is there a minimum term or automatic renewal? What notice is required, and where are the current terms recorded? |
| Migration | How would we move to another service? Is help available, is it included, and what might it cost? |
| Retention | When is information removed after termination? What does the provider say about backups and retained copies? |
| Continuity | How long could we operate without the service? What is the alternative or temporary manual process? |
Also check the people and connections around the platform: who knows how it is configured, which other services depend on it, what integrations will stop, and whether the business controls the domain, administrator accounts and recovery contacts. Microsoft 365 has additional tenant, licence and access questions when changing support providers:
Changing your Microsoft 365 provider →
A simple exit plan is better than no exit plan
For many small businesses, a useful first record is only a few lines long:
Example SaaS exit record
- Supplier: Example CRM
- Renewal date: 1 March
- Notice required: 30 days
- Data export: CSV and attachments; last tested in June
- Critical dependency: customer records and sales pipeline
- Alternative or fallback: identified
- Business owner: named role or person
Replace the example details with the actual agreement and product behaviour. The important point is that somebody owns the record and the export has been checked.
For a critical service, go one step further: keep a secure export where the business can reach it independently, check it contains the needed information, confirm authorised people know how to retrieve it, and rehearse the first steps of a move. A backup is only useful if the business can access and restore it.
Do not wait until you need to leave
Hopefully you never have a serious problem with a SaaS supplier. That is not the point. Technology management is not only about planning for what you expect; it is also about understanding what happens when circumstances change.
Before putting another important part of the business into the cloud, do not only ask: “How quickly can we get started?”
Ask this too
If we need to leave, how quickly can we get out — with our information, our access and our business still working?
This article covers the technology and operational issues rather than providing legal advice. For contractual disputes or interpretation of terms, take appropriate legal advice.
For questions about backups, continuity or a cloud service you rely on, you can ask the IT Club Advisor.
Found this useful? Forward it to someone who might too.
Sources and further reading
The legal clarification about the individual right to data portability is based on the Information Commissioner’s Office guidance. This article does not interpret the terms of any specific SaaS contract.
Plain-English Takeaway
For important SaaS services, plan the way out before you need it. Confirm what can be exported, whether the export is complete and usable, what happens to access and data after termination, and how the business would keep operating during a switch. Test the exit route while the supplier relationship is still working.
Frequently asked questions
What should a small business include in a SaaS exit plan?
Record the service owner, what the platform is used for, renewal and notice dates, how data and attachments can be exported, who can access the export, migration or termination charges, what happens to retained copies, an alternative or manual fallback, and when the export was last tested.
Does owning our data mean we can easily move it?
Not necessarily. A contract or product may allow an export, but the resulting files might not include attachments, history, custom fields, audit information or relationships between records. Check what is included and test whether another system or a person can actually use it.
Does UK GDPR give my company a right to export all SaaS data?
No single blanket company right should be assumed. The UK GDPR right to data portability is an individual's right covering certain personal data in specific circumstances. It is not a general right for a business to export every type of commercial or operational data from any SaaS provider. Check the contract and take legal advice for a specific situation.
Can a SaaS provider suspend access during a billing dispute?
Do not assume either that access will continue or that a provider can suspend it in every situation. Check the terms that apply to your service and plan for the operational possibility that access could be interrupted while an issue is resolved.
How often should we export data from a SaaS platform?
There is no single interval for every service. Set the frequency according to how important the system is, how quickly its data changes and how much recent information the business could afford to recreate. For a critical platform, make sure exports are accessible outside that provider account and test that they are usable.
Do we need a detailed exit plan for every app?
No. Be proportionate. A low-cost tool holding little important information may need only an owner and renewal reminder. A platform that supports customer records, finance, staff operations or a core service needs a clearer export, access, migration and continuity plan.
Related Articles
Your IT Provider Has Five-Star Reviews. What Do They Actually Prove?
Five-star IT provider reviews are useful evidence, but they are not due diligence. Learn how to read ratings, check selection effects and ask better questions.
Read articleWhen Your IT Provider Finds a Compliance Problem, Who Benefits From the Fix?
Your IT provider finds six compliance gaps and can sell you six fixes. That is not automatically a problem — but it is a reason to ask what is required, what is recommended and who benefits from the decision.
Read articleCould Your Business Keep Running If Its Owner Died Tomorrow?
Death is the ultimate key-person test. This practical guide helps small businesses find the digital dependencies that could stop communication, money, customer delivery or recovery if an owner or key person became unavailable.
Read article