wodby migrate wodby1 instance

Preview, apply, or verify a Wodby 1 instance migration

Migrate exactly one Wodby 1 app instance. The default command is a read-only preview. Add --apply to create the target and import data, then test the target using its technical route. Change DNS only after testing succeeds, and rerun the same command with --verify to validate the completed migration. Add --workspace to create an instance that uses direct Git deployment as a development workspace: its code is checked out from the linked Git repository instead of being built by CI. The preview reports why an instance cannot be one. The migration exports only the selected instance and its parent app metadata, then creates a new Wodby 2 app containing a matching app environment. Pass --target-app to add it to an existing Wodby 2 app instead; the CLI infers the app's shared stack when unambiguous and never adopts or overwrites an existing app environment. By default it imports the newest successful backup file for each required component shown in the preview. Use --source-backup BACKUP_UUID to pin all components to a different complete snapshot, or --skip-data to omit data. Changes made after the selected backup completed are not migrated. Apply is resumable and stores its plan and state in the system temporary directory, or next to --state-file when it is set. When state exists, the same --apply command preserves the saved plan and continues completed work. --apply --restart replaces the saved plan. If the migration already changed Wodby 2, the CLI first shows and confirms removal of only the resources recorded as created by this migration; pre-existing target apps and reused resources are preserved. Restart is refused after successful verification or while any target operation remains ambiguous. --rollback deletes the Wodby 2 resources this migration created and discards its state; it refuses once --verify has succeeded, because DNS then points at Wodby 2. Migrated cron schedules stay disabled until --verify confirms that DNS points to Wodby 2, so scheduled jobs do not run on both platforms.

wodby migrate wodby1 instance SOURCE_INSTANCE_UUID [flags]

export WODBY1_SOURCE_TOKEN=...
  export WODBY_API_KEY=...

  wodby migrate wodby1 instance INSTANCE_UUID --target-cluster CLUSTER [target and mapping options]
  wodby migrate wodby1 instance INSTANCE_UUID --target-app APP --target-cluster CLUSTER [target and mapping options]
  wodby migrate wodby1 instance INSTANCE_UUID --target-cluster CLUSTER [same options] --apply
  wodby migrate wodby1 instance INSTANCE_UUID --target-cluster CLUSTER [same options] --verify