Can your software vendor refuse to export your data when you leave?

Which contract clauses decide whether you get your data back?#

Your data return rights are decided by a small set of clauses spread across the order form, the master agreement and sometimes a data processing addendum. Read them as one system: a strong ownership clause can be undercut by a short retention window or an export fee.

Pull the version of each document that actually governs your account. Many vendors update online terms, and the order form may say which version applies.

Weak clauses are easiest to fix at renewal, when the vendor wants the signature. A one-line addition that guarantees a full export with attachments and history, and a stated window after termination, costs the vendor little and can save a difficult negotiation later.

What do published vendor terms say about data after you leave?#

Published vendor terms show how much the post-termination window varies, from a short request period to no access at all once the term ends. The examples below come from vendors' own terms or help pages as checked for this article; your order form or a negotiated agreement may say something different.

Two patterns stand out. Where a window exists, it usually depends on a written request made in time, so missing the request can mean losing the data even when the window has not closed in practice. And several vendors say plainly that they have no obligation to keep data after the window, which turns a slow export into a permanent loss.

When can a vendor hold back an export?#

A vendor can usually hold back an export when the contract gives it a reason, and the common reasons are predictable. Unpaid invoices are the first: many agreements let the vendor suspend services, and some do not separate export from other services.

The second is timing. If the retention window has passed, the vendor may have deleted the data as the contract required. The third is definitions. Audit logs, field history, attachments, call recordings and outputs created by the vendor's own AI features may fall outside 'customer data' as the contract defines it.

Format disputes are the fourth. A vendor may meet its obligation with a flat export that drops relationships between records, such as which comments belong to which ticket. The contract rarely promises more than the product's standard export unless you negotiated it.

What a complete export should include#

A complete export includes the relationships between records, not just the records. For operational history, the links are what make the archive useful later, whether for a new system, litigation or a data license.

Many native exports skip history, attachments or internal notes, and some limit how far back they reach. Check the vendor's documentation and your plan, then compare record counts in the export against counts in the product before relying on it.

• 1Help desk: tickets, every public and internal comment, attachments, field change history, tags and satisfaction ratings.
• 2CRM: accounts, contacts, opportunities with stage history, activities, emails, notes and attachments.
• 3Field service: customers, sites, estimates, jobs, dispatch notes, technician notes, photos, invoices and warranty claims.
• 4Project tools: issues, comments, status history, linked commits or documents, and attachments.
• 5Across all systems: user and team tables so authors can be resolved, and custom field definitions.

Steps to take before giving notice of non-renewal#

The steps before notice of non-renewal matter most, because your leverage drops once the vendor knows you are leaving. Run them early enough that a failed test export can still be fixed by negotiation.

• 1Read the order form, master agreement and any data addendum, and note the retention window.
• 2Inventory the objects you need, including attachments, history and audit logs.
• 3Run a test export and verify completeness against record counts in the product.
• 4Ask the vendor in writing to confirm the full export scope, format and post-termination window.
• 5Negotiate transition assistance or a read-only period if the standard export falls short.
• 6Schedule the final export before the account ends, and keep a written record of what was exported, when and by whom.
• 7Store the export in storage your company controls, with access limited to named people.
• 8Give notice only after the export plan is confirmed.

Illustrative: an HVAC contractor retires its old field service system#

Illustrative: a fictional HVAC and plumbing contractor is moving from an older field service platform to a new one. Its contract allows export through the product during the term, says nothing about attachments and deletes data at termination.

Before giving notice, the COO runs a test export and finds it covers customers and invoices but not technician notes, job photos or callback history. She asks the vendor in writing for a full export. The vendor offers it as a paid professional services project, and the contractor accepts before the renewal date passes.

The final export includes job histories with notes, photos and linked invoices. The contractor stores it in its own encrypted storage, migrates what the new system needs and keeps the full archive under its retention schedule.

What to do if the vendor still refuses#

If the vendor still refuses, escalate in writing and cite the clauses that support your request. Ask for the specific reason, because the answer shows whether the issue is fees, definitions or timing, each of which has a different fix.

Bring in counsel before the account closes. Workarounds such as automated scraping may breach the vendor's terms, and dispute resolution clauses may set out notice steps you have to follow. Outside the US, rules on switching between cloud services, such as those in the EU Data Act, may add rights that a US contract alone does not give.

Why exports matter for data licensing, and how SourceX helps#

Exports matter for data licensing because the operational history in a retiring system is often the most valuable part of a company's records. Once a vendor deletes it, no license is possible.

SourceX starts with the Supply step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check collects metadata only, such as system names and years of history, and large archives stay in the company's own storage. Whether vendor terms allow exported records to be licensed is checked in the Rights step.