migrate supports two migration modes:
- Run a local structured migration for LangChain, LangGraph, ADK, Strands, or Bedrock AgentCore projects and generate an AgentKit app.
- Start a remote migration job for a Dify export or another type of agent project, then download the generated VeADK project when the job finishes.
migrate
A local structured migration analyzes the entry object, generates the service entry point, deployment configuration, and migration plan in the source project, and updates project dependencies. The command reports the files it creates, updates, or overwrites. Use --dry-run to inspect the plan only.
This command modifies the source project. --force overwrites existing generated files. Commit or back up existing changes and inspect the plan with --dry-run first.
migrate create
Create a remote migration job for a Dify export or another agent project. The command uploads the source directory, creates a remote sandbox, returns the job ID, and leaves the job running in the background. If an active job already has the same workspace, source directory, and migration configuration, the command reuses it.
This operation uploads the source directory to a remote sandbox and may create billable cloud resources. Remove credentials, user data, and other files that must not be uploaded. The generated result must use a dedicated sibling directory; it cannot overwrite the source directory or be placed inside it.
migrate list
List locally stored Dify or Any migration job metadata for the selected workspace. This action does not query other workspaces or create cloud resources.
migrate status
Query a remote job. After a job succeeds, partially succeeds, or fails, this command downloads the result or failure report to the output directory selected at creation time. Later invocations reuse a local terminal result.
--overwrite replaces files that have already been downloaded to the result directory. Use it only when local changes do not need to be preserved.