Skip to content

migrate

github-actions[bot] edited this page Feb 12, 2026 · 1 revision

fm migrate

Migrate Frappe Manager to current version.

Migration operates at two levels:

  • FM Infrastructure: CLI config + global database services (always checked and migrated if needed)
  • Benches: Individual bench environments (you choose which ones to migrate)

Without arguments, migrates only FM infrastructure. Specify a benchname to migrate that bench, or use --all-benches to migrate all benches. Use --auto-proceed to skip confirmation prompts. Control failure handling with --on-failure: prompt (ask), archive (save failed), or rollback (revert all).

Usage:

$ fm migrate BENCHNAME [OPTIONS]

Arguments:

  • BENCHNAME: Bench name to migrate

Options:

  • --all-benches: Migrate all benches
  • --skip-all-backup: Skip all backups (DANGEROUS - use only if backups fail)
  • --skip-backup-for: Skip backup for specific benches (comma-separated)
  • --exclude-bench: Exclude specific benches from migration (only with --all-benches)
  • --auto-proceed: Skip migration confirmation prompt (proceed automatically)
  • --on-failure: What to do if migration fails: prompt (ask user), archive (save failed benches), rollback (revert all)

Examples:

Migrate FM infrastructure only (safe)

fm migrate

Migrate specific bench

fm migrate

Migrate all benches

fm migrate --all-benches

Skip confirmation prompt

fm migrate --all-benches --auto-proceed

Auto-proceed with auto-rollback on failure

fm migrate --all-benches --auto-proceed --on-failure=rollback

Auto-proceed, archive failed benches (partial success OK)

fm migrate --all-benches --auto-proceed --on-failure=archive

Skip all backups (dangerous)

fm migrate --all-benches --skip-all-backup

Exclude specific benches

fm migrate --all-benches --exclude-bench mybench1,mybench2

Clone this wiki locally