Why Portability Is a Negotiation Issue
SaaS data portability is the right to get your own data out of a vendor's platform — in a usable form, on a workable timeline, and without a punitive bill — and it is a commercial issue long before it is a technical one. The reason is leverage: the moment a renewal arrives, the vendor's strongest card is the cost and difficulty of leaving. If your data is effectively trapped, every price increase becomes easier for them to impose, because your option to replace the vendor — the single most powerful lever you hold — is only as real as your ability to take your data with you. Negotiating portability is therefore not housekeeping; it is protecting the credibility of every future negotiation, which is why it belongs alongside the core moves in our negotiation handbook.
The cost of getting this wrong is rarely visible until exit, and by then it is unrecoverable. Buyers routinely discover, mid-migration, that the contract they signed years earlier promised an export but never defined its format, scope or price — and that the vendor is entirely within its rights to provide a partial dump at a premium charge over many weeks. With the average enterprise now running more than 300 applications, the portability terms of any single one look trivial at signing, which is exactly why they are conceded so casually and regretted so often. Treating portability as a standard, non-negotiable requirement across every SaaS purchase is the only way to avoid relearning the lesson one painful exit at a time.
The Export Right: Format, Timing, Cost
A meaningful export right specifies three things, and vague wording on any of them is a trap. The first is format: insist on open, machine-readable formats — JSON, CSV, XML or a SQL database dump — not a proprietary file or a PDF rendering that cannot be re-imported anywhere. "We will provide your data on request" means nothing if the data arrives in a form no other system can read. The second is timing: the contract should commit the vendor to deliver a complete export within a defined period, commonly 30 days of a request, and to maintain your data in an accessible state for a transition window of 30 to 90 days after termination. The third is cost: the export itself should be free or at genuine cost, not priced as a penalty for leaving.
Pay particular attention to completeness. An export that includes records but strips out metadata, attachments, audit history or configuration is not portability — it is a partial copy that forces you to rebuild context in the new system. Define in the contract exactly what "your data" includes, and require that the export preserve relationships and structure, not just rows. The same close reading you apply to liability and renewal terms applies here, and our guide to reading a software contract clause by clause covers how to spot the wording that quietly narrows an export right to uselessness.
| Term | Buyer-Protective Position | Vendor Default to Resist |
|---|---|---|
| Format | Open, machine-readable (JSON, CSV, XML, SQL) | Proprietary or PDF-only |
| Scope | All data, metadata, attachments, config | Core records only |
| Timing | Within 30 days; 30–90 day access window | "On request", undefined |
| Cost | Free or genuine cost | Egress priced as a penalty |
Post-Termination Transition and Assistance
Getting a file is not the same as switching providers, and the better contracts say so. Negotiate an explicit transition-assistance obligation: the vendor's commitment to maintain API access during the changeover, provide technical documentation of the data model, and actively help move data to the replacement platform. Set the transition period clearly — 30 days is a common floor, with a right to extend — and require that any switching-related charges during that window be cost-based only, not an opportunity to bill at premium rates while you are at your most captive. Without this, a vendor can comply with the letter of an export clause while making the practical migration slow and expensive enough to deter you from leaving at all.
An export file is not a migration. Without a transition-assistance obligation, a vendor can hand you your data in a technically compliant form and still make leaving slow enough that you stay.
Egress Fees and the EU Data Act
Data egress charges are one of the most effective lock-in mechanisms in modern SaaS and cloud contracts, and they are a primary hidden cost to negotiate down at signing rather than discover at exit. The regulatory direction of travel now favours buyers: under the EU Data Act, switching-related charges must be cost-based during a transition period, and providers are required to phase out egress fees entirely by 2027. Even outside the EU, that standard is a powerful benchmark to bring to the table — if a vendor is being compelled to drop egress fees for European customers, its justification for charging you elsewhere weakens considerably. Treat egress, alongside the broader exit terms covered in our work on dispute and exit provisions, as a line item to be capped or removed, not an immovable cost of doing business.
Quantify the exposure before you sign, not after. Ask the vendor, in writing, what it would cost to export your full dataset at the volume you expect to hold at the end of the term — and watch how the answer is given. A vendor confident its egress pricing is reasonable will answer plainly; one that deflects or refuses is telling you the charge is a retention device. Put a number on it, cap it in the contract at genuine cost, and you remove one of the two pillars of lock-in. The other pillar is migration effort, which is why egress protection and transition assistance have to be negotiated together: cheap export of data you cannot practically move is no freedom at all.
The Clauses to Negotiate
Translate the principles into specific contract language. Negotiate a data-ownership clause confirming, unambiguously, that the data is yours and the vendor holds it only as processor. Add an export clause specifying format, scope, timing and cost as above. Add a transition-assistance clause with API access, documentation and a defined, extendable window. Add an egress provision capping or eliminating switching charges. And add a deletion-and-certification clause requiring the vendor to delete your data after the transition and certify that it has done so, closing the loop on both portability and security. Each of these is standard in well-negotiated agreements and routinely absent from the vendor's template, which is precisely why they have to be raised. Our SaaS contract optimisation practice negotiates exactly this set, and the full checklist sits in the SaaS Optimization Guide.
Negotiate Portability Before You Need It
The entire value of portability terms depends on when you negotiate them. At signing, the vendor wants your business and concessions are cheap; at exit, you are asking the one party with every incentive to refuse. Build portability into the initial agreement and into every renewal, treat it as a precondition rather than a nice-to-have, and you preserve the credible exit that keeps the vendor honest on price for the life of the relationship. Portability negotiated early is insurance that costs nothing and pays out every time you sit down to renew. To review or negotiate the data portability and exit terms across your SaaS estate, request a confidential briefing.