EU Data Act for SaaS: how to design data export and offboarding

Since 12 September 2025 the EU Data Act lets SaaS customers switch and take their data. What the export must hold, and how to design the exit.

  • Product Design
  • B2B SaaS and workflow software
  • B2B SaaS & Workflow Software
Insights

Since 12 September 2025 the EU Data Act lets SaaS customers switch and take their data. What the export must hold, and how to design the exit. Since 12 September 2025, the EU Data Act has given customers of SaaS products a legal right to leave.

Since 12 September 2025, the EU Data Act has given customers of SaaS products a legal right to leave. A customer can give notice of at most two months, after which the provider has up to 30 calendar days to help it move all of its exportable data and digital assets to another provider or to its own infrastructure, keeps the service running while it does, leaves at least 30 more days to retrieve the data, and then erases it. Until 12 January 2027 the provider may charge only what the move actually costs it; from that date it may charge nothing for switching.

For a SaaS product, that turns an old back-office task into a product surface. The export has to carry the metadata, settings and relationships that make data usable elsewhere, in formats another system can read. The customer has to be able to see what it will get before signing and before deciding, and to follow the move while it happens. This article sets out what Chapter VI asks for in plain words, then spends most of its length on how to design it.

We write as product designers, so read this as design guidance rather than legal or regulatory advice: how the Regulation applies to your contracts and your service is for your own legal and regulatory owners to decide.

What the Data Act requires of a SaaS provider

Chapter VI (Articles 23 to 31) applies to providers of "data processing services". Recital 81 names Software as a Service as one of the delivery models the term covers, and the Commission's Data Act FAQ (version 1.4, 22 January 2026) confirms that Chapter VI applies to every SaaS product that fits the definition: on-demand network access to scalable, elastic resources that a customer can provision with minimal interaction from the provider. Two narrower regimes sit in Article 31. Services whose main features were mostly custom-built for one customer and are not offered at broad commercial scale escape some duties, and non-production versions offered for a limited time for testing and evaluation escape the chapter entirely. Customers who started on a no-cost tier keep the right to switch (Article 23(c)).

The duties, in plain words:

DutyWhere it sitsWhat it means for the product
A written contract setting out switching rights, available before signing in a form the customer can storeArticle 25(1)Exit terms are visible before purchase, not found after
A notice period of no more than two months before switching startsArticle 25(2)(d)The product records the date of notice and shows when the move can begin
A transitional period of no more than 30 calendar days to move the data, with the service still runningArticle 25(2)(a)The product keeps working while the export runs
Reasonable assistance, business continuity, clear information on known risks to continuity, and a high level of security during the moveArticle 25(2)(a)(i) to (iv)Status, risks and help are shown in the product, and the export is secured in transit
An exhaustive list of the data and digital assets that can be ported, covering at least all exportable dataArticle 25(2)(e)A complete, readable inventory of what the customer can take
An exhaustive list of internal-functioning data held back because of trade secrets, which must not delay switchingArticle 25(2)(f)What is excluded is named, not silent
At least 30 calendar days to retrieve data after the transitional periodArticle 25(2)(g)Read-only access continues after the move
Full erasure of the customer's exportable data and digital assets after retrieval, once switching has succeededArticle 25(2)(h)A deletion date, and a confirmation when it happens
Information on switching procedures, methods, formats and known limitations, plus an up-to-date online register of data structures, formats and standardsArticle 26A public, versioned page describing the export
Open interfaces made available to all customers and destination providers at no chargeArticle 30(2)A documented export API, not only a download button
A "structured, commonly used and machine-readable format" on request, where no common specification has been publishedArticle 30(5)Formats other software can parse without help
Reduced switching charges, at no more than cost, until 12 January 2027; none from that dateArticle 29(1) to (3)Charges disappear from the flow on 12 January 2027
Clear pre-contract information on standard fees, early termination penalties and any reduced switching charges, publicly available, where applicable, on a dedicated part of the website or in another easily accessible wayArticle 29(4) to (6)Fees are stated where buyers compare plans

Three details matter for design. First, if 30 days is technically unfeasible, the provider must tell the customer within 14 working days of the switching request, justify it, and propose an alternative period of no more than seven months, with the service continuing throughout (Article 25(4)). Second, the customer can extend the transitional period once, for as long as it considers appropriate (Article 25(5)). Third, when it gives notice, the customer chooses one or more of three actions: switch to another provider, move to its own infrastructure, or erase its data (Article 25(3)). The notice form should let them pick more than one.

What a SaaS provider does not have to do matters as much. The FAQ (question 58a) says functional equivalence, rebuilding the same function in the new environment, applies only to infrastructure providers. Article 24 limits the duties to the source provider's own service, and the FAQ (question 58b) says no source provider has to help rebuild the service at the destination. Article 30(6) adds that a provider need not build new technology or hand over its own intellectual property or trade secrets. A SaaS provider's job is a complete, documented, usable export and a well-run exit.


What the export must contain

Article 2(38) defines exportable data as "the input and output data, including metadata, directly or indirectly generated, or cogenerated, by the customer's use" of the service, excluding the provider's or third parties' intellectual property and trade secrets. Article 2(32) adds digital assets: elements in digital form the customer has the right to use independently of the contract. Recital 83 and the FAQ (question 53) give examples: metadata on the configuration of settings, security, and access and control rights.

The Regulation does not list fields. For most SaaS products, though, the definition reaches well past a flat table of current records. Comments, status changes, approvals and the audit trail are all generated by the customer's use. A record that refers to another record is useless when the reference is missing. And in SaaS, the customer cannot reconstruct any of this alone: the Commission's standard contractual clauses note that in SaaS "the Customer does not know the structure of the database" while the provider does, and that knowing "the relationship between Data" is what sets the order of the export.

Here is how we would cover each layer, and how to show it:

LayerTypical contents in a B2B SaaS productHow to show it in the product
Core recordsAccounts, projects, tickets, orders, documents, custom objectsA per-object list in the export screen with record counts
RelationshipsStable IDs on every record, references between records, parent and child links, many-to-many joinsA data model diagram or schema file in the export, and IDs that never change between exports
HistoryStatus changes, versions, comments, approvals, activity and audit logsA clear choice of "current state" or "full history", with the size of each
FilesAttachments and uploads in their original formats, with their links to recordsA file manifest that maps each file to the record that holds it
Users and permissionsUsers, roles, groups, permission sets, sharing rulesA separate section, because access rules are what an admin rebuilds first
ConfigurationCustom fields, workflows, templates, forms, automations, integration settingsExported as readable definitions, not screenshots
Held backData relating only to the internal functioning or security of the service, if anyNamed in a short list, with the reason, beside the export

Two vendors' own documentation shows the habit of naming both sides of the line. Atlassian's page on exporting data from Jira Cloud lists what a cloud backup includes, among them work items and fields, comments, board and sprint data, users and group settings and space configuration, with attachments, avatars and logos as an option, and then lists data that cannot be exported, such as automation flows and third-party app data. Shopware's EU Data Act page for its cloud services names the categories a customer can take, from product and customer data to orders and media, and the category held back: data relating only to the platform's internal functioning, monitoring, telemetry, diagnostics or security. Neither page is a template. Both show that a customer can read the boundary before relying on it.


Formats and interfaces

Article 30(5) asks for "a structured, commonly used and machine-readable format" where no common specification exists for the service type. In practice that points to a small set of choices:

  • CSV for flat tables, one file per object, with a header row and stable column names.
  • JSON for nested records and configuration, where a record holds lists or child objects.
  • Original file formats for attachments, never re-encoded into something the destination cannot open.
  • A manifest at the root of the export: what each file is, the schema version, record counts and a checksum for each file.
  • Schema documentation for every field: its type, whether it can be empty, and what it refers to.

Article 26(b) requires a reference to "an up-to-date online register" of data structures, formats, standards and open interoperability specifications. Treat that register as product documentation: a public page, versioned with the product, that changes when the data model changes. Article 30(4) ties its upkeep to the interoperability duties. Article 30(3) adds that once the Commission publishes common specifications or harmonised standards for a service type in its Union repository, providers have 12 months to become compatible. The register is where a customer will look to see whether you have.

Article 30(2) asks for open interfaces with enough information to build software that talks to the service. A paginated export API with the same objects, IDs and formats as the file export serves both the customer's own team and the destination provider, and it lets large accounts move data in batches rather than in one archive.


A self-serve export the customer can test before deciding

The Regulation's clock starts when the customer gives notice, but the decision to give notice is made earlier. A customer weighing a switch needs to know what it will get. The Commission's standard contractual clauses for cloud computing contracts, adopted as Recommendation (EU) 2026/2394 of 29 October 2026, are non-binding, but they show what a careful contract asks for: a switching and exit plan agreed up front, an estimate of the time needed to export, and a test, arranged by the provider or run with its help, "to check that the Plan works in practice".

A product can make that test routine rather than an event:

  • Export at any time, from the admin area. The same export used for switching is available on an ordinary day, so admins can run it, inspect it and keep it as a backup.
  • A sample export. A small, representative slice of every object type, so a destination team can build its import before the full run.
  • A size and time estimate before the export starts, based on the account's own record and file counts.
  • A sandbox import guide that shows how the files fit together, using the manifest and schema.
  • Who can export, and a log of who did. Exporting everything is a powerful action. Limit it to named admin roles and record it in the audit trail, which also supports the security duty in Article 25(2)(a)(iv).

None of these is spelled out in the Regulation. Each one turns the exhaustive list in Article 25(2)(e) from a contract clause into something the customer has seen work.


The offboarding flow

Most SaaS products already have a cancellation flow. Chapter VI needs a different one, built around the customer's choice in Article 25(3) and the periods in Article 25(2). An outline:

  1. Before signing. Plan and pricing pages state the standard fees, early termination penalties and any switching charges (Article 29(4)). The contract, including its switching terms, can be downloaded and kept (Article 25(1)).
  2. A "Data and exit" page in admin settings. It lists the categories of data and digital assets the customer can take, the categories held back and why, the formats, the link to the online register, and known limitations (Article 26). It also links to the self-serve export.
  3. The switching notice. A form in the product, not only an email address. The customer chooses switch to another provider, move to its own infrastructure, or erase. If it chooses a new provider, it gives that provider's details (Article 25(3)(a)). The product confirms receipt in writing, which the standard contractual clauses suggest doing within three working days.
  4. The notice period. A visible countdown to the start of the transition, never longer than two months, with the date the transition will begin.
  5. The transition. A progress view with each object type, record counts exported against expected, files transferred, failures and retries, and the date the 30 days end. The service keeps running, and any known risk to continuity is shown here, not buried in an email (Article 25(2)(a)(iii)).
  6. Extensions. One control for the customer to extend the transitional period once (Article 25(5)). If the provider needs longer for technical reasons, the notice, its justification and the new end date appear in the same view, sent within 14 working days of the request (Article 25(4)).
  7. Verification. A reconciliation report the customer and the destination can check: counts per object, checksums per file, and a list of anything that did not export, with the reason. The standard contractual clauses let the parties agree success metrics and milestones; the product is where they are tracked.
  8. Retrieval. At least 30 days of read-only access after the transition, with the end date shown on every screen (Article 25(2)(g)).
  9. Erasure and termination. The erasure date, a confirmation once erasure is complete, and the termination notice the provider must send (Article 25(2)(c) and (h)).

The design work is in the states between these steps: a notice sent but not yet confirmed, an export that partly failed, a customer who changes its mind about erasure, an admin who leaves during the transition. Each state needs a screen that says what is happening and what happens next.


What stays, what is erased, and when

A customer leaving a SaaS product asks three questions: what will I have, what will you keep, and when will it be gone. The Regulation sets the sequence; the product should show it as dates, not durations.

StageHow longWhat the customer can doWhat the provider must do
Notice periodUp to two monthsUse the product as normal, run test exportsPrepare the move (the Commission's model clauses also suggest confirming receipt of the notice)
Transitional periodUp to 30 calendar days, or an alternative period of up to seven months if 30 days is technically unfeasible; the customer can extend onceExport, transfer, verifyAssist, keep the service running, keep the data secure
Retrieval periodAt least 30 calendar daysRetrieve any remaining dataKeep the data available
ErasureAfter the retrieval period, or a later agreed date, once switching has succeededNothing furtherErase all exportable data and digital assets generated by or relating directly to the customer

Two cases need their own wording. If the customer chose erasure without switching, the contract ends at the end of the notice period (Article 25(2)(c)(ii)), so the erasure date comes sooner. And some personal data may have to be kept under other EU or national law; the standard contractual clauses carve this out of the erasure confirmation. The product should say what is kept, under which obligation, and for how long, so that "erased" means what the customer thinks it means.


Why an easy exit sells

The obvious fear is that a visible exit invites customers to use it. We think the opposite argument is stronger, and the law now pushes in the same direction.

The Data Act removes most of the old tools of lock-in: long notice, punitive charges, partial exports. Recital 88 says unnecessarily high egress charges and other unjustified charges "cause lock-in effects". Once a customer can leave on these terms anyway, a hard-to-read exit no longer keeps it; it only costs trust. And for some buyers, a clear exit is a purchase requirement. Under DORA, Article 28(8), EU financial entities must put exit strategies in place for ICT services supporting critical or important functions. A SaaS vendor selling to them is answering an exit question either way, and a product that already shows its export, formats and timeline answers it before procurement asks.

This is why, in our work on B2B SaaS and workflow software, data export sits with the audit trail and role rights among the places where a product's answers to enterprise buyers should be visible. A product that shows customers exactly what they can take with them gives them a reason to believe it will treat their data well while they stay. The Data Act makes the exit a floor. How clearly you show it is still your choice.

The same move has another side. When a customer arrives with data exported from somewhere else, or leaves an old system of its own, the work is mapping records, keeping the rules the business relies on and moving people's saved work without a break. That is what our legacy software modernisation work covers, and our guide to legacy software modernisation sets out the approach.


A checklist before 12 January 2027

From 12 January 2027, Article 29(1) forbids any switching charge, including data egress charges, for switching. The other switching duties have applied since 12 September 2025. Before 12 January, check the list below; items marked as our recommendation go beyond what the Regulation requires:

  • Charges. Remove switching and egress charges from price lists, contracts, invoices and any in-product step that mentions them. Standard service fees and agreed early termination penalties are not switching charges (Article 2(36)); keep them clearly separate.
  • Pre-contract information. Plan pages and order forms state standard fees and early termination penalties, and the information Article 29(6) asks you to make public, where applicable, on a dedicated part of the website or in another easily accessible way, is current.
  • Inventory. The exhaustive list of exportable data and digital assets matches the current data model, including custom objects and fields added since it was written.
  • Held-back data. The list of internal-functioning data excluded for trade-secret reasons is short, specific and does not delay switching.
  • Register. The online register of structures and formats is up to date (Article 26(b)); making it public and versioned is our recommendation.
  • Interfaces. The export API is documented and open to customers and destination providers at no charge.
  • Self-serve export (our recommendation). Admins can run a full export and a sample export without a support ticket, and every export is logged.
  • Switching notice. The product accepts a notice, records the customer's choice, and confirms receipt.
  • Timers. Notice, transition, extension, retrieval and erasure dates are calculated and shown in the product and in emails.
  • Verification (our recommendation). The reconciliation report exists and has been tested on a large account.
  • Erasure. Erasure is confirmed to the customer, and any legally retained data is named with its retention period.
  • Support script (our recommendation). Support and account teams describe the exit in the same words as the product.

Most of this list is product design and engineering work, not legal drafting. It is easier to do once, deliberately, than to answer each departing customer by hand.

About the authors

  • Rakesh Chitroda

    Co-founder

    Rakesh Chitroda is a co-founder of Tcules and writes for teams choosing an outside partner for product work. Rakesh's guides cover how to choose a product design agency, what a product design agency does, when to hire a design system consultant, how to choose a UX audit agency or a front-end development agency, and how to compare software modernisation companies. Other pieces deal with cost and working arrangements: what an MVP costs to design and build, hiring a product designer for a SaaS product, and outsourcing UX design without losing product knowledge.

    LinkedInMore from Rakesh
  • Rushali Bhatt

    Product Designer

    Rushali Bhatt is a Product Designer at Tcules. Rushali's articles start from the people inside complex software: clinicians and patients in healthcare products, users who cannot take part in research sessions, and the reviewers who check an AI feature's output before anyone acts on it. Topics include usability studies for enterprise software, human-in-the-loop patterns, a readiness checklist for AI product UX, what to fix first when adding AI to a live SaaS product, and what a heuristic evaluation should deliver. Useful reading for product teams whose software people rely on to make decisions.

    More from Rushali

Designing the exit your EU customers can see

Your export and exit flow are worth designing together, so get in touch.