> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/in-memory-db/how-tos/migrate-from-v1-v2.md).

# Migrate from In-Memory DB v1 to v2

{% hint style="warning" %}
**Important:**

* **In-Memory DB v2**, powered by [<mark style="color:blue;">Valkey</mark>](https://valkey.io/), is now available, bringing Valkey (Redis®-compatible) engines in versions 8, 8.1, and 9. It also adds extended snapshot retention and native <code class="expression">space.vars.ionos\_cloud</code> Observability integration.
* Use **In-Memory DB v2** to create clusters using either the [<mark style="color:blue;">DCD</mark>](/cloud/databases/in-memory-db/how-tos/v2.md) or the [<mark style="color:blue;">API</mark>](https://api.ionos.com/docs/in-memory-db/v2/).
* Creation of clusters using In-Memory DB v1 is deprecated through the [<mark style="color:blue;">DCD</mark>](/cloud/databases/in-memory-db/how-tos/v1.md) and only limited operations are supported on legacy clusters.
* Creation of v1 clusters through the [<mark style="color:blue;">API</mark>](/cloud/databases/in-memory-db/api/v1-api.md) will be deprecated as of **July 31, 2026**.
* An automatic migration from v1 to v2 is impossible. You must manually migrate existing v1 clusters to the new v2 infrastructure through the v2 API. For step-by-step instructions, see [<mark style="color:blue;">Manual migration</mark>](/cloud/databases/in-memory-db/how-tos/migrate-from-v1-v2.md#manual-migration).
  {% endhint %}

## Manual migration

You must perform the migration through the In-Memory DB v2 API.

{% hint style="warning" %}
**Important:** Creation of v1 clusters through the API will be deprecated as of **July 31, 2026**. Migrate existing clusters to v2 before this date.
{% endhint %}

{% hint style="info" %}
**Prerequisites:**

* You must have the contract administrator or owner role, or the **Access and manage DBaaS** privilege, to manage clusters.
* The v2 API requires API token authentication (`tokenAuth`). Include a valid token in the `Authorization` header of every request. For information on generating tokens, see the [<mark style="color:blue;">Authentication API</mark>](https://api.ionos.com/docs/authentication/v1/#tag/tokens/operation/tokensGenerate).
  {% endhint %}

1\. Create a new In-Memory DB v2 instance using the v2 API. For the API documentation, see [<mark style="color:blue;">In-Memory DB v2 Cloud API</mark>](https://api.ionos.com/docs/in-memory-db/v2/).

2\. If you want to move data from your v1 instance, migrate it to the new In-Memory DB v2 instance.

3\. Update your applications to connect to the new In-Memory DB v2 [<mark style="color:blue;">Endpoints</mark>](https://api.ionos.com/docs/in-memory-db/v2/#tag/Overview/Endpoints).

{% hint style="info" %}
**Note:** Updating your applications to the new endpoint may briefly interrupt connections. Plan for a short cutover window while traffic switches from v1 to v2.
{% endhint %}

## Next steps

* [<mark style="color:blue;">Create an In-Memory DB Cluster</mark>](/cloud/databases/in-memory-db/how-tos/v2/create-in-memory-db-cluster.md): Provision your new v2 cluster in the DCD.
* [<mark style="color:blue;">FAQ</mark>](/cloud/databases/in-memory-db/in-memory-db-faqs.md): Common questions about In-Memory DB v1 and v2.


---

# 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://docs.ionos.com/cloud/databases/in-memory-db/how-tos/migrate-from-v1-v2.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.