When Your Software Shuts Down: Why Every System Needs a SaaS Data Export Exit Plan
When companies choose software, they ask whether it is easy to use and what it costs. Few ask: "If we stop using it one day, how do we take our data with us?" In 2026, that question became very practical. AI automation tool Relay.app announced in July that it was shutting down, giving paying customers roughly 60 days to move. Meta's enterprise collaboration platform Workplace closed on May 31, the same day its data export window ended. Meanwhile, on October 6 the European Commission issued guidance on how the EU Data Act applies to SaaS, requiring providers to offer free, machine-readable data export. For businesses, SaaS data export is no longer a minor IT detail. It is an exit plan you should write before adopting any system.
Tools Shut Down Too: Can You Move Out in 60 Days?
According to Inbox Zero's summary of the notice, Relay.app told customers on July 16, 2026 that it was winding down: free accounts would be deleted on August 15 and paid accounts on September 14, with any unexported data permanently lost. Customers could export workflows (as JSON), run history and tables (as CSV), but connected accounts and authorizations had to be set up again in a new tool, and no alternative could import those workflows in one click.
Meta's Workplace followed a different rhythm: the shutdown was announced in 2024, the service went read-only in September 2025, and export ended along with the service on May 31, 2026. The runway was long, but once the deadline passed, the data was gone all the same.
Both cases make the same point: software vendors may close, get acquired or change direction, and the only thing a company truly owns is what it can take with it.
The EU Data Act: SaaS Data Export Now Has Rules
The EU Data Act's chapter on switching between services has applied since September 12, 2025. According to an October 6, 2026 analysis by German law firm LIS, the key points include:
- Notice and transition: customers give at most two months' notice; the transition normally takes no more than 30 days, extendable to up to seven months where it is technically unfeasible.
- Retrieval: data must remain retrievable for at least 30 days after the transition ends.
- Switching charges: until January 12, 2027, providers may charge only costs directly linked to the switch; after that, switching charges are prohibited.
- Scope: customer input and output data, metadata generated through use, and digital assets such as configurations that the customer is entitled to use independently, but not the provider's source code or trade secrets.
SaaSRise's summary of the Commission guidance adds that exports must be free and machine-readable, contracts must list exportable data categories, and attachments, relationships and change history should be included.
Taiwanese businesses may not be directly bound by EU law, but these rules set a useful benchmark: a responsible software service should let customers take their data with them at any time.
More Than Data: Three Things Most Often Forgotten
Many people assume that being able to download a CSV means being able to move. In practice, these three things cause the most trouble:
1. Workflows and settings
Automation rules, approval flows, permission settings and pricing formulas represent years of refining "how we work." If only raw data can be exported, you must rebuild all of it in the new system.
2. History and relationships
Links between customers and orders, back-and-forth on support tickets, file version history. Once relationships break, the data still exists but loses its meaning.
3. Connections and authorizations
As the Relay.app case shows, every connected account and authorization has to be set up again. The more integrations you have, the longer this takes.
An Exit Plan Written Into Contracts and System Design
Whether you rent SaaS or commission custom development, think through the exit from day one:
- List the data: which data, settings, attachments and history must be portable.
- Specify formats and documentation: export formats, field descriptions and API docs should be complete, not readable only by the vendor.
- Agree on timelines: put notice, transition, retention and deletion dates into the contract.
- Assign responsibility: who exports, who imports and validates, and who is on call on cutover day.
- Test it once: before signing or launching, export a sample and try importing it into another environment.
Custom systems have a natural advantage here: you decide the database structure, the data lives in your own cloud account, and export features can be built in from the start. But the contract must make ownership of the source code and data clear; see "Who Owns AI-Written Code?" for more. For when to rent and when to build, see "SaaS or Custom Software?"
Conclusion: A Good System Lets You Leave Anytime
It sounds paradoxical, but the systems most worth using for the long term are often the ones that let you leave at any time. AI makes software faster to build, and it also makes the market churn faster. In that environment, control over your data is one of your most important assets. AI delivers perfection; people deliver emotion, and keep a way out for the company's future.
If you are evaluating a new system, planning SaaS data export and migration for existing tools, or need a custom system where your data stays fully in your hands, take a look at TitApeX's services, or simply get in touch.
Comments