> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/en-us/cherry-studio/installation/upgrade-downgrade.md).

# Upgrade and Downgrade

Choose a version switching path, and protect V1 and V2 data before operating.

Choose the corresponding instructions based on your current version and target. V1 and V2 use different data structures; you must back up before switching between major versions.

{% hint style="danger" %}
V1 and V2 data and backup formats are not interoperable. Sessions, Agents, settings, and files added in V2 will not be automatically written back to V1.
{% endhint %}

## Upgrading and migrating to V2.0.2

{% hint style="warning" %}
If you need to keep V1 data, the correct path is:**V1.9.13 → V2.0.2 (complete data migration directly)**You no longer need to install V2.0.0 first.
{% endhint %}

| Current situation                                   | What to do                                                                                             |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Still on V1 and need to keep data                   | Update V1 to 1.9.13, then install V2.0.2 directly to complete the migration.                           |
| Already using V2                                    | Upgrade to V2.0.2 normally and continue using the current V2 data; do not click \[Re-migrate].         |
| Previously failed to migrate V1 or missed some data | After creating a full backup of the current V2, you can use \[Re-migrate] under \[Settings] → \[Data]. |
| Do not need V1 data                                 | You can choose \[Ignore and use default values], but V1 data will not be migrated.                     |

{% hint style="danger" %}
\[Re-migrate] will permanently delete the current V2 data, then re-import from the original V1 data. It will not merge or keep data from either side. Unless the V1 migration previously failed or data was missed, do not click it.
{% endhint %}

## Choose a path

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Destructive update reminder</strong></td><td>First confirm data incompatibility, re-migration, and rollback limitations.</td><td><a href="/docs/en-us/cherry-studio/installation/v2-breaking-update-notice.md">Warning for Destructive Updates</a></td></tr><tr><td><strong>Feature differences</strong></td><td>Learn about changes to the interface, Agents, knowledge base, and other items that need to be reviewed after upgrading.</td><td><a href="/docs/en-us/cherry-studio/installation/v1-v2-feature-differences.md">Feature Differences</a></td></tr><tr><td><strong>Upgrade V1 to V2</strong></td><td>Back up V1 data, then use V2.0.2 directly to complete the migration.</td><td><a href="/docs/en-us/cherry-studio/installation/v1-to-v2-migration.md">Upgrade from V1 to V2</a></td></tr><tr><td><strong>Downgrade V2 to V1</strong></td><td>Return to the original V1 data, and learn when you actually need to handle the V2 database.</td><td><a href="/docs/en-us/cherry-studio/installation/v2-to-v1-downgrade.md">Downgrade from V2 to V1</a></td></tr></tbody></table>

## Preparations before switching

1. Finish any running conversations, Agents, knowledge base imports, and file processing tasks.
2. Create a new full backup for the current version and store it outside the application data directory.
3. Record the current application data directory; when using a custom directory or external disk, make sure the path is accessible.

{% hint style="warning" %}
Do not manually delete application data in the name of a 'complete uninstall.' Database handling applies only when you explicitly give up all V2 data or need to re-migrate; see [\[Downgrade V2 to V1\]](/docs/en-us/cherry-studio/installation/v2-to-v1-downgrade.md).
{% endhint %}

## Download entry

* [Cherry Studio V2 official download](https://cherryai.com.cn/download)
* [Cherry Studio V1 official download](https://cherryai.com.cn/download/v1)
* V2.0.2 release page:[GitCode](https://gitcode.com/CherryHQ/cherry-studio/releases/v2.0.2) · [GitHub](https://github.com/CherryHQ/cherry-studio/releases/tag/v2.0.2)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cherryai.com.cn/docs/en-us/cherry-studio/installation/upgrade-downgrade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.