My current version has been upgraded from 0.15 to 1.0.0. I am now upgrading to 1.9.2. How should I proceed? I want to keep my current data unaffectedGeneral Discussion

[gongchangping]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

My current version has been upgraded from 0.15 to 1.0.0. I am now upgrading to 1.9.2. How should I proceed? I want to keep my current data unaffected

[dosubot[bot]]

You can upgrade directly from 1.0.0 to 1.9.2—no need for intermediate steps. To keep your data safe, stop all Dify services and make full backups of your database, Redis, vector DB, and any persistent storage before starting. Update your codebase and Docker images to 1.9.2, and update your .env file to match the latest .env.example for compatibility.

Run all database migrations using Alembic (e.g., uv run flask db upgrade), then run the plugin migration commands: uv run flask extract-plugins --workers=20, uv run flask install-plugins --workers=2, and uv run flask migrate-data-for-plugin. After migration, restart all services and verify that everything works as expected in the UI. If you use Weaviate as a vector DB, upgrade both the server and client, open the new gRPC port, and follow the Weaviate migration guide.

If you hit migration errors (like missing columns or duplicate tables), you may need to manually clean up the database or retry the migration. For large version jumps, the safest backup is to archive the entire /docker/volumes directory after stopping all services. Dify does not support live migration—downtime is required for a consistent backup.

For more details and troubleshooting, see the official migration guide and community upgrade discussions.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[gongchangping]

Can you provide more specific upgrade steps

[dosubot[bot]]

Here’s a step-by-step guide for upgrading Dify from 1.0.0 to 1.9.2 while keeping your data safe (reference, reference, reference):

1. Back up everything: Stop all Dify services. Back up your database, Redis, vector DB, and all persistent storage (for Docker: archive the entire ./volumes directory, your .env, and docker-compose.yaml). This is essential for recovery if anything goes wrong.

2. Update your code and images: Pull the latest code for Dify 1.9.2 and update your Docker images:

   docker compose pull
   

   Replace your docker-compose.yaml with the new version and migrate any customizations.

3. Sync your environment: Compare your .env file with the new .env.example and add/update any new variables required by 1.9.2.

4. Start new containers:

   docker compose up -d
   

5. Run database and plugin migrations inside the API container:

   docker compose exec api uv run flask db upgrade
   docker compose exec api uv run flask extract-plugins --workers=20
   docker compose exec api uv run flask install-plugins --workers=2
   docker compose exec api uv run flask migrate-data-for-plugin
   

   If you use plugins, make sure you can access https://marketplace.dify.ai/ before running the plugin install command.

6. (If needed) Adjust permissions: From v1.10.1, the API container runs as UID 1001. On the host, run:

   sudo chown -R 1001:1001 ./volumes/app/storage
   

7. Restart all services:

   docker compose down
   docker compose up -d
   

8. Verify the upgrade: Log in to Dify, check plugins, tools, models, workflows, and data. Monitor logs for errors.

Special notes:

• If you use Weaviate as a vector DB, upgrade both the server and client, open the new gRPC port, and follow the Weaviate migration guide.
• If you hit migration errors (e.g., missing columns/tables), you may need to manually clean up problematic schema elements or comment out failing migration steps, then repeat the upgrade command until it succeeds (reference).
• There are known bugs in 1.9.2 with workflow request history, but these are not caused by the upgrade process itself (reference).
• For large version jumps or server migration, you can stop all Dify Docker services, archive /docker/volumes, transfer it to the new server, update codebase/configs, and start Dify. Then run plugin migration commands and verify data integrity in the UI (reference).

For more details, see the official migration guide and community upgrade discussions.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}