Facts
My client was a vertical SaaS company providing an analytics platform to a mid-sized enterprise customer on a three-year subscription. As the renewal window approached, the customer notified my client that it would not be renewing and was migrating to a competing platform. The customer then demanded, in writing, that my client produce a full structured export of all data in the customer's workspace, including derived analytics tables, in a specific schema the customer dictated, within fifteen business days, at no charge.
The signed master services agreement included a data-export clause, but the clause was modest: it required my client to make raw customer-input data available in CSV format for thirty days post-termination on a self-service basis. The agreement did not require derived or computed outputs, did not require any specific schema, and did not require attorney-mediated extraction. The customer's general counsel framed the demand around portability and an implicit threat to publicize what she described as a vendor-lock-in pattern.
What I did
I read the master services agreement, the data processing addendum, and the customer's order form against the export demand. The contract analysis was straightforward; the harder layer was the reputational risk if the customer carried out her implied threat. I drafted a written response from my client's general counsel mailbox that did three things in sequence: it affirmed the export obligation that the contract actually imposed, declined the contractually-unsupported demands in plain English with section citations, and offered a paid-engagement schedule for the broader derived-data export the customer was asking for.
I also drafted, separately, a short post-mortem memo for my client identifying which terms of the master agreement had created the ambiguity that allowed this dispute to arise, with proposed redline language for the next version of the standard form.
Outcome
After the written response, the customer's counsel withdrew the no-charge demand and accepted the contractually-required CSV export. The customer also engaged my client at the proposed paid schedule for a portion of the derived-data export. There was no public escalation. The post-mortem redline was incorporated into my client's next standard-form revision. Each matter turns on its facts; the outcome here does not predict the outcome on a similarly framed customer-offboarding dispute.
Lesson
A SaaS vendor's strongest position at customer offboarding is a master services agreement whose data-export clause is specific about format, scope, timeline, and cost. Vague language reads to a departing customer's counsel as room to negotiate, and the negotiation always happens at the worst possible moment, with renewal off the table and a new vendor already in flight. The form contract is the leverage; the dispute is just where the form contract is tested.
Have a SaaS contract matter that looks similar?
Send the agreement and the facts in writing. I read every inquiry myself.
See the SaaS practice page Email owner@terms.law