Skip to main content
SaaS Directory Info

Reference edition 2026.47

Sign in

Data Export and Retention: Facts Buyers Need Up Front

Data · 10 min read ·

Which export formats, retention periods and deletion statements a SaaS product should publish, and how buyers can test them before they sign up.

Illustration: A handbook diagram of a data lifecycle: create, use, export, cancel, retention window, deletion, with date markers in muted teal

Buying software is easier when leaving is easy. A product that holds your customer records, your documents or your history becomes part of how you work, and the day may come when you need to take that information somewhere else: to a competitor, to an archive, to an auditor. Whether you can do so, in what form and how long the vendor keeps what is left behind are facts that matter at the start of the relationship, and that too few product pages state.

This how-to guide describes what export and retention facts a software product should publish and how to word them. It also gives buyers a short test they can run during a trial to check the claims for themselves.

Why this belongs on the specification page

Switching costs are the hidden cost of any tool. A vendor who makes export easy removes a major source of buyer anxiety. A vendor who hides export invites suspicion, and a buyer who suspects a lock-in tends to choose a rival, or to delay. Publishing export and retention facts is therefore good practice and sound commercial sense.

There is also a regulatory reason. In the UK and EU, individuals have a right to data portability for personal data in certain circumstances: they can obtain data they have provided to a controller, in a structured, commonly used and machine-readable format. The Information Commissioner's Office explains the right and its limits in its guidance. A business customer using your product as a processor of its own customers' data may need your export features to meet its obligations to those people. If your product can produce an export, say so; if it cannot, say that too.

What an export should cover

A complete export is more than a spreadsheet of the main table. Walk through every kind of thing a customer puts into the product and decide whether it can leave.

  • Records: the primary objects, such as contacts, projects, invoices or documents.
  • Relationships: how the records link, for example which contact belongs to which company. Exports that flatten relationships lose half the value.
  • Attachments and files: the uploaded material itself, not only a list of names.
  • History: comments, status changes and activity logs, where the customer might need them.
  • Settings and configuration: custom fields, templates and automation rules, so a setup can be rebuilt.
  • Metadata: identifiers, created and modified times, authors.

For each, state in your documentation whether it is included, partially included or not exportable. A table with those three states is plain and honest.

Formats

Two formats cover most needs.

Comma-separated values. CSV is a plain-text format for tabular data, understood by almost every spreadsheet and database. It is excellent for simple tables and poor at nested data and relationships. Document the character encoding, the delimiter, how dates are written and how text containing commas and line breaks is quoted.

JSON. JavaScript Object Notation is a lightweight data format that represents nested structures naturally, making it better for records with relationships. Document the schema: field names, types and which are optional.

Some products also offer document-oriented formats, such as PDF or HTML, for human reading and archiving, and vendor-specific or standard exchange formats for particular domains. State what each is suitable for. A PDF is a good archive of an invoice and a poor starting point for re-importing data.

Do not invent a format name. If your export is a bespoke archive, describe its structure and link to the specification so that a customer, or their next vendor, can parse it.

Export mechanics

The format is half the story; how the export is requested and delivered is the other half.

  • Who can export? Only administrators, or any user for their own data?
  • How is it triggered? A button, a request through the interface or a support ticket?
  • How long does it take? Large accounts may take hours. Say what to expect.
  • How is it delivered? A download link, an email or a cloud storage location? How long does the link last?
  • Is it complete? Are there limits on size or on the number of exports?
  • Is it available after cancellation? For how long?

The last point is worth stating clearly. Some products allow export only while the subscription is active, and a customer who cancels in a hurry may find the door shut. A grace period for export after cancellation is a customer-friendly feature, and vendors who offer it should say so.

Retention

Retention is how long the vendor keeps data. There are three moments to describe.

  1. During the subscription. Is data kept indefinitely? Are there limits, for example on activity logs or file versions?
  2. After cancellation. How long is the account kept in a recoverable state before deletion begins?
  3. After deletion. How long until copies in backups are gone?

Give each as a period, not as an adjective. "Promptly" and "as soon as possible" are not retention periods. Explain exceptions, such as legal obligations to keep invoices for a statutory period, in a sentence of their own.

Deletion

A deletion statement should explain:

  • What is deleted: the account, its content, its backups, its logs.
  • How a customer can request it, and how to confirm it has been done.
  • Whether deletion is reversible and until when.
  • What the vendor retains, if anything, and why.

Do not claim deletion is "permanent" unless you can explain how backups and replicas are handled. A more careful phrase is "removed from live systems immediately and from backups within the stated period".

A worked example

Take a fictional note-taking product. Its page used to say: "Your data is yours. Export any time." The rewritten version reads:

  • Export formats: notes as Markdown files; attachments as original files; tags and links as JSON.
  • Included: note text, attachments, tags, internal links, creation and edit dates.
  • Not included: comments from shared collaborators; page analytics.
  • How: an owner chooses export in settings; a download link arrives by email and remains valid for a stated number of days.
  • After cancellation: accounts remain recoverable for a stated number of days; exports can be requested during that time.
  • Deletion: content is removed from live systems at the end of the recovery period and from backups within a further stated period.
  • Last reviewed: date.

Every line is checkable. The two admitted gaps, comments and analytics, make the rest more believable.

A trial test for buyers

You can verify export claims in an afternoon.

  1. Create sample data that covers each object type you rely on, including at least one attachment and one relationship.
  2. Run the export the way you would after cancellation.
  3. Open the files in the tool you would use next: a spreadsheet, a database, a text editor.
  4. Check completeness: is everything there? Are relationships intact? Are the dates readable?
  5. Try re-importing into a different product, if one is on your shortlist.
  6. Read the retention terms in the agreement and compare them to the page.
  7. Ask one question about backups and deletion, and see how the vendor answers.

A product that passes with a clean export and a clear answer deserves higher confidence in all its other claims.

Keeping the statement true

Export features change as products grow. New object types appear and are forgotten by the export code. Add a standing check: whenever a new kind of data is added to the product, the release checklist asks whether it is included in the export and whether the documentation needs updating. Test the export on a schedule with a realistic account and record the date in the fact sheet.

Special cases worth documenting

Shared and collaborative content. When several people contribute to a document, whose export is it? State whether an owner's export includes content written by collaborators and whether personal data of those collaborators is included.

Deleted items. Many products keep a recycle bin. Say how long deleted items stay there, whether they appear in exports and how to remove them permanently.

Integrations and third-party data. Data synchronised from another service may be exportable from the original service rather than from you. If so, say so, to avoid the impression that your export covers everything.

Very large accounts. If an export could run to many gigabytes, say how it is split, how long the link works and whether you offer an alternative route such as direct transfer to the customer's own storage.

Legal holds and statutory retention. Invoices and certain financial records may need to be kept for a period set by law. A vendor may be required to retain them even after account closure. Explain this in plain language so customers are not surprised.

Questions to ask in a procurement review

Procurement and security teams often work from a checklist. The export and retention items that tend to appear are: the formats available, whether exports are self-service, the schema documentation, the retention period after termination, the deletion method and the certificate or confirmation of deletion. If your page answers all of them, you will have saved your prospect a round of emails; if it answers none, expect the round and a longer sales cycle.

Summary

State what can be exported, in what formats, by whom and how; state how long data lives during the subscription, after cancellation and in backups; and explain deletion honestly. Name gaps instead of hiding them. Buyers who can see how they would leave are more willing to arrive, and a plainly written export section is one of the strongest trust signals a product can publish.

Questions and answers

What is data portability?
The ability to obtain your data from a service in a structured, commonly used, machine-readable format so you can reuse it elsewhere. Under UK and EU data protection law it is a right in certain circumstances for personal data.
What should an export contain?
The records a customer created, the relationships between them, attachments, and enough metadata, such as timestamps and identifiers, for the data to make sense elsewhere.
How long should a vendor keep data after cancellation?
There is no universal figure. The vendor should state a specific period, explain what is kept in backups and say how deletion is confirmed.
Can I test an export before buying?
Often yes, during a trial. Create sample records, run the export and open the file in the tool you would use afterwards.

Sources

Questions?