EU Data Act: Data Access, Portability and Switching — AI Automation article by Rui Codex

Under the EU Data Act, business software users gain rights to access their data, port it and switch providers under defined conditions. For business software, that means checking exportability, contract terms and integration design before you need to leave. Rui Codex provides technical implementation support only.

Key takeaways

  • The EU Data Act gives customers of data-processing services, including many SaaS and cloud products, a statutory right to switch providers.
  • Data access and portability are technical questions as much as contract questions, so export paths must be tested before you need them.
  • Switching charges are being phased out under the Act, but transition effort and integration rework remain real costs.
  • Most switching plans fail on missing data models, unclear exports of configuration and integrations that depend on one vendor's proprietary interface.

What does the EU Data Act cover for business software?

The Act covers data generated by connected products and related services, and it covers data-processing services such as cloud platforms. Many software-as-a-service tools that business teams use every day fall into the second group, which is why their contracts and technical setup matter.

The Act has applied since 12 September 2025, and some obligations depend on when a product was placed on the market. The text is available on EUR-Lex, Regulation (EU) 2023/2854, and it should be the reference point for any scope question.

This article is general information and not legal or tax advice.

Scope is rarely obvious from a product name. A tool may be a data-processing service in one deployment and a plain software licence in another, so the contract and the architecture both need review. Your legal advisers should make the final scope decision for your organisation.

How do you get access to your data in practice?

You get access through the export, API or reporting mechanisms the provider offers, and the Act expects those mechanisms to be usable without unreasonable obstruction. The design of your system decides how easy that access really is. A provider can comply on paper while your team still needs weeks of manual work to extract a usable dataset.

A practical access checklist

  • Identify every system that holds business-critical records, including reporting tools and integration middleware.
  • Confirm whether each provider offers a bulk export, an API or both, and whether the API has rate limits that would slow a full extract.
  • Test a full export into a neutral format on a copy of your data, not only a sample.
  • Record who in your organisation can request exports and how long that takes.

Access becomes harder when data is spread across several vendors. An integration platform that joins your CRM and accounting system holds copies of the data and mappings too, so it must be part of the access plan. Our integration services page describes how such connections are typically designed.

Which data must be portable?

Portability means you can take your data to another service in a form that the new service can use. In practice, the raw records are only one part of what you need, and the rest is often missing from a standard export.

The regulation sets out the framework for exportable data and the assistance providers must give customers during a switch, and the official wording is on EUR-Lex, Regulation (EU) 2023/2854. Read the definitions there before you write requirements, because a loose reading leads to disputes later.

Tip: Ask each provider to list, in writing, which objects an export contains: records, attachments, audit logs, custom fields, workflow rules and user permissions. Gaps in that list are the first things to negotiate.

How does switching providers work?

You switch by giving notice, receiving the provider's support for the transfer, and moving data and workflows to the new service within the transition period. The Act sets maximum notice and transition periods and allows an extension where a switch is technically unfeasible, as described in the regulation text on EUR-Lex.

Switching charges are also addressed. The regulation provides for their phase-out by 12 January 2027, which removes a cost that used to lock customers in. Egress fees and paid migration services can still appear in some contracts, so compare the full price of leaving with the price of staying.

  • Notice: check the period, the form of notice and whether it starts at a fixed date.
  • Transition: agree what support is included and what is billed separately.
  • Verification: define how you confirm that migrated data is complete and correct.
  • Shutdown: specify when the old service stops and how deletion is certified.

Where do switching plans usually fail?

Switching plans usually fail where the data is technically present but not meaningful outside the original system. The contract is rarely the bottleneck. The bottleneck is the design of your data model and integrations.

  • Proprietary formats: exports are complete but use internal identifiers that the new system cannot map without manual work.
  • Hidden logic: approval rules, calculated fields and automations live in the application, not in the data, so they disappear during migration.
  • Integration coupling: connected systems expect the old vendor's API responses, so every link must be rebuilt.
  • History gaps: audit trails or document versions are not included in the standard export.

The trade-off is real. Designing for portability from the start, for example by using open data models and documented interfaces, adds effort to the first build. It usually reduces the cost of a later switch, but the saving depends on how often you actually switch, which is something only you can judge.

Hypothetical examples of a switch

Here are two hypothetical scenarios:

In the first, a mid-sized distributor exports its customer records from a cloud CRM but not the automation rules that route quotes to regional sales teams. The new platform receives the contacts, yet the routing stops working on the first day, and the team rebuilds the logic from memory. The lesson is to inventory logic as well as data before you commit to a date.

In the second, an accounting workflow depends on a vendor's proprietary webhook format. The export works, but every connected tool needs a new adapter, and the adapter work becomes the critical path. Teams in this position often benefit from an integration layer they control, which keeps the vendor-specific code in one place. Our ERP and CRM integration service covers this kind of design work.

What should you check before you sign?

Check contract terms and technical facts together, because a clause that promises export is worth little if the export is unusable. Work through these items with your technical and legal teams.

  1. List every business-critical dataset and the system that owns it.
  2. Obtain the provider's written list of exportable objects, including logic and history.
  3. Test one full export and one partial re-import into a sandbox.
  4. Confirm notice, transition and any charges in the contract, not only in marketing material.
  5. Document which integrations would need rework and estimate that effort honestly.
  6. Assign an owner for the switching plan and review it at each contract renewal.

Building these checks into procurement is easier than retrofitting them after a dispute. Our integration and API engineering articles cover the technical side in more depth.

Frequently Asked Questions

Does the EU Data Act apply to SaaS tools my company already uses?

It can, because the Act covers data-processing services offered to customers, and many SaaS products fall into that category. Whether a specific tool is covered depends on the service and its contract, so read the regulation text on EUR-Lex and ask your provider which terms apply. Your legal advisers should make the final scope decision.

Can a provider still charge me to export my data?

Providers may charge for some things, but the Act provides for the phase-out of switching charges, with the end date set in the regulation text on EUR-Lex. Check your contract for export fees, retrieval charges and paid migration services. Get any charge confirmed in writing before you start a migration.

How long does switching to a new provider take?

The timeline depends on the notice period, the transition period and the complexity of your integrations. The regulation on EUR-Lex sets maximum notice and transition periods, with an extension where a switch is technically unfeasible. Migration testing and integration rework still take their own time, so plan in phases and keep the old service running until the new one is verified.

Do I need a technical partner to prepare for switching?

You do not always need one, but an external technical review often finds export gaps before they become a problem. Rui Codex provides technical implementation support only, including integration design and export testing. You can request a project consultation at https://ruicodex.com/Contact to discuss your systems.

Conclusion

The EU Data Act gives business software users stronger rights to their data, but those rights only become practical when the export paths, integrations and contract terms work together. Start with an inventory of data and logic, test an export before you need one, and treat switching costs as part of the purchase decision. Where the architecture is complex, a technical review can show gaps that a contract review alone will miss. Request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com to discuss your project.

Sources

Tags: EU Data Act Data Portability Switching Providers API Integration Business Software Data Access Workflow Automation Software Development Company Belgium

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request