Interoperability and the Right to Exit SaaS Platforms

Apr 16, 2026 | Interoperability

In this article:

Interoperability is the technical and legal condition that makes genuine market competition possible. Without it, switching costs accumulate until the platform can raise prices without consequence. The Electronic Frontier Foundation and the Free Software Foundation Europe have been fighting for interoperability mandates at the regulatory level. Businesses have a direct stake in that fight and most do not know it.

What Is Interoperability and Why Does It Make Competition Possible

Interoperability means that data generated on one platform can be used on a competing platform without loss of functionality. It means that the switching cost is the effort of learning a new interface, not the loss of years of accumulated data. It means that platforms must compete on product quality because users can actually leave.

The absence of interoperability is not a technical inevitability. It is a business decision. Platforms that could support open data export standards choose not to because interoperability reduces lock-in. Lock-in is the mechanism that enables price increases without competitive consequences.

What Policy Fight Are EFF and FSFE Running on Interoperability

The Electronic Frontier Foundation's work on interoperability includes legal analysis, policy advocacy, and public education about the competitive and rights implications of platform lock-in. The EFF has argued for interoperability mandates as a consumer protection measure and as a prerequisite for a functioning competitive market in digital services.

The Free Software Foundation Europe has pushed for interoperability requirements in European digital regulation, including contributions to the Digital Markets Act framework. The argument in both cases is that voluntary interoperability does not emerge from markets dominated by platforms with strong incentives to maintain lock-in.

Why Should Businesses Follow the Interoperability Policy Fight

A business paying recurring fees to a platform it cannot leave without losing years of operational history is experiencing the consequences of absent interoperability directly. The regulatory fight for interoperability mandates is the policy-level version of the same argument.

The business does not need to wait for regulatory intervention. But understanding that the policy fight exists, who is making it, and why clarifies what is at stake in the infrastructure decisions made today.

Frequently Asked Questions

What is interoperability in software and why does it matter?

Interoperability is the technical condition under which data generated on one platform can be used on a competing platform without loss of functionality. Without it, switching costs accumulate until platforms can raise prices without competitive consequence. Interoperability is the structural precondition for market competition in digital services.

What is the Digital Markets Act and how does it address interoperability?

The EU Digital Markets Act designates large platforms as gatekeepers and imposes interoperability requirements including data portability obligations that allow users to move their data to competing services. The Free Software Foundation Europe contributed to this framework. what open standards and interoperability look like in tool migration practice.

Do any SaaS platforms currently support meaningful interoperability?

Open source platforms built on standard protocols support interoperability by default because their codebases are inspectable and their data schemas are documented. Proprietary SaaS platforms vary: some offer meaningful exports, others offer exports that cover data they are comfortable losing while retaining data most valuable for lock-in.

References

Electronic Frontier Foundation. eff.org.

Free Software Foundation Europe. fsfe.org.

Doctorow, Cory. The Internet Con: How to Seize the Means of Computation. Verso, 2023.

Interoperability Standards and Tool Migration Paths

Apr 11, 2026 | Interoperability

In this article:

Interoperability standards are the technical foundation of data portability. Open standards define data formats that multiple tools can read and write, making migration between platforms possible without data loss. The business that evaluates tools on interoperability criteria before adoption pays a lower exit cost if the product enshittifies than the business that evaluates on features alone.

What Do Open Standards Look Like in Practice for Data Portability

A tool that stores data in open, documented formats can be migrated from. CSV exports of operational data, JSON exports of audit histories, standard database dumps: these are interoperability in practice. A tool that stores data in proprietary formats accessible only through its own export mechanism is a lock-in architecture.

The distinction is not always visible before adoption. It becomes visible when you try to leave. Evaluating interoperability before adoption means asking: what format does this tool export data in? Can I import that format into a competing tool? Can I access my data directly, not just through an export function the platform controls?

Which Tools Support Portability and Which Build Lock-In by Design

Why open source tools support portability where proprietary SaaS does not
AttributeOpen Source ToolsProprietary SaaS
CodebaseInspectable: anyone can read itClosed: governed entirely by the vendor
Data schemaDocumented: you know how your data is storedProprietary: format defined and controlled by vendor
Export formatOpen standards by default (CSV, JSON, SQL)Varies: often incomplete or vendor-specific
PortabilityBuilt into the architecture by designDesigned against: portability reduces switching cost
Switching costLow: data migrates with youHigh by design: accumulated data is the lock-in mechanism
Lock-in mechanismNone: governance structure removes the incentiveCentral to the business model and revenue strategy

Open source tools built on standard protocols generally support portability because they have to. The codebase is inspectable, the database schema is documented, and the community that maintains the tool has an interest in open standards that the community driving proprietary SaaS does not share.

Proprietary SaaS tools vary. Some offer meaningful data exports that cover the data the business actually needs to migrate. Others offer exports that cover the data they are comfortable with you taking while retaining the data that is most valuable for lock-in.

What Does a Real Migration Between Platforms Actually Cost

A migration from a platform with good interoperability costs time: the time to export, transform, import, and validate data. A migration from a platform with poor interoperability costs that plus the loss of data that cannot be exported and the rebuilding of baselines from scratch.

The second cost is the one that lock-in pricing depends on. The platform that keeps your most valuable historical data in a format you cannot meaningfully export has made that data a hostage. The ransom is continued subscription payments at whatever price the platform decides to set.

Frequently Asked Questions

What data formats should you look for when evaluating SaaS portability?

When evaluating a SaaS tool before adoption, check whether it exports data in open, standard formats:

  • CSV for tabular operational data: rows, columns, importable anywhere
  • JSON for structured records with relationships preserved
  • SQLite or PostgreSQL dumps for complex datasets where schema matters
  • CalDAV for calendar and scheduling data
  • IMAP for email archives

Proprietary formats accessible only through the platform's own export function are lock-in architectures regardless of what the sales team tells you about data ownership.

How long does it actually take to migrate from one SaaS platform to another?

A migration with good data portability takes days to weeks. A migration with poor portability takes months and involves rebuilding baselines from scratch. the step-by-step migration guide with a realistic time estimate for each phase.

What is the difference between data export and data portability?

Data export is the platform giving you a file containing some of your data. Data portability is the condition under which that file can be imported into a competing service without loss of functionality. Most platforms offer data export. Meaningful portability, where exported data retains its analytical value in another system, requires open standard formats.

References

Electronic Frontier Foundation. eff.org.

Free Software Foundation Europe. fsfe.org.