Ctrlk
官网GitHub
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Upgrade and downgrade

Choose the 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.

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.

Upgrading and migrating to V2.0.2

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.

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.

[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.

Choose a path

Destructive update reminder

First confirm data incompatibility, re-migration, and rollback limitations.

Feature differences

Learn about changes to the interface, Agents, knowledge base, and other items that need to be reviewed after upgrading.

Upgrade V1 to V2

Back up V1 data, then use V2.0.2 directly to complete the migration.

Downgrade V2 to V1

Return to the original V1 data, and learn when you actually need to handle the V2 database.

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.

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].

Download entry

PreviousLinuxNextDestructive update reminder

Last updated

Was this helpful?