> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/23.md).

# Art. 23 — Removing obstacles to effective switching

Data Act Article 23 — Removing obstacles to effective switching. Regulation (EU) 2023/2854, Chapter VI — Switching between data processing services.

Providers of data [processing](https://headlesslaw.com/definitions/data-act/processing/) services shall take the measures provided for in [Articles 25](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/25.md), [26](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/26.md), [27](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/27.md), [29](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/29.md) and [30](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/30.md) to enable customers to switch to a [data processing service](https://headlesslaw.com/definitions/data-act/data-processing-service/), covering the [same service type](https://headlesslaw.com/definitions/data-act/same-service-type/), which is provided by a different provider of data processing services, or to [on-premises ICT infrastructure](https://headlesslaw.com/definitions/data-act/on-premises-ict-infrastructure/), or, where relevant, to use several providers of data processing services at the same time. In particular, providers of data processing services shall not impose and shall remove pre-commercial, commercial, technical, contractual and organisational obstacles, which inhibit customers from:

> **(a)**terminating, after the maximum notice period and the successful completion of the [switching](https://headlesslaw.com/definitions/data-act/switching/) process, in accordance with [Article 25](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/25.md), the contract of the data processing service;
>
> **(b)**concluding new contracts with a different provider of data processing services covering the same service type;
>
> **(c)**porting the [customer](https://headlesslaw.com/definitions/data-act/customer/)’s [exportable data](https://headlesslaw.com/definitions/data-act/exportable-data/) and [digital assets](https://headlesslaw.com/definitions/data-act/digital-assets/), to a different provider of data processing services or to an on-premises ICT infrastructure, including after having benefited from a free-tier offering;
>
> **(d)**in accordance with [Article 24](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/24.md), achieving functional equivalence in the use of the new data processing service in the ICT environment of a different provider of data processing services covering the same service type;
>
> **(e)**unbundling, where technically feasible, data processing services referred to in [Article 30(1)](/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/30.md) from other data processing services provided by the provider of data processing services.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/data-act/chapter-vi-switching-between-data-processing-services-art.-23-31/23.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.