# EU Data Act: Switching, Lock-In, and Why Open Architectures Help

Date: 2026-05-04

The EU Data Act introduces rules on **access to and use of data**, contractual fairness, **switching between data processing services**, and interoperability in several contexts (including Internet of Things and B2B data sharing scenarios per its scope). It is explicitly aimed at reducing **lock‑in** and unfair contractual imbalance—not identical to GDPR, but complementary when you negotiate cloud and platform contracts.

**What to bake into an open‑source migration from a Data Act lens**

- **Switching plans** that are technically credible: export formats, APIs, documented data models, and tested egress—not marketing slides.
- **Contract review** for exit assistance, notice periods, and unfair terms that block migration; open components help only if you control interfaces and avoid proprietary data prisons on top.
- **Interoperability by design**: standard protocols, documented integration layers, and avoiding “secret sauce” in non-portable middleware.
- **Governance of shared data** in ecosystems you join; open source does not resolve consent, purpose limitation, or misuse—it clarifies implementation.

For AI stacks, watch hidden lock‑in: embeddings stores, proprietary feature formats, and managed vector APIs that make “open models” operationally non‑portable.

Are your migrations measured by *time-to-exit* and *cost-to-exit*, or only by *time-to-deploy*?