Migration paths the Dify docs describe for self-hosted deployments, beyond moving apps as DSL files: storage moves inside a running Dify.
Preparing a Docker Compose Dify for production or Kubernetes by moving uploaded files and private keys to object storage and knowledge vectors from the bundled Weaviate to Qdrant or Milvus with the documented flask commands, with backup and validation steps.
Moving apps from Dify Cloud into your own deployment: exporting app DSL, rebuilding knowledge bases from source documents, re-entering provider and tool credentials, recreating MCP servers and API keys, and cutting over API clients.
Moving from a Docker Compose Community install to Enterprise on Kubernetes: what carries over, license activation tied to a namespace, SSO and SCIM setup, and planning the move of PostgreSQL, storage and vector data.
Relocating a Compose deployment to new hardware or another cloud: stopping services cleanly, copying volumes with permissions intact, keeping SECRET_KEY unchanged, updating public URLs and verifying plugins after the move.
Switching the vector store under existing knowledge bases with flask vdb-migrate: choosing pgvector to reuse PostgreSQL or Qdrant for scale, re-embedding cost, the dataset index type that overrides VECTOR_STORE, and validation.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.