system migration

See the workflow guide for examples. Global flags such as --json go before the command; see global options.

openship system migration

Team-mode migration lifecycle

openship system migration [options] [command]

Subcommand	Purpose
`preflight [options]`	Read-only readiness check for the own-server migration
`start [options]`	Migrate this instance onto your own server
`start-cloud [options]`	Migrate this instance to Openship Cloud
`start-tunnel [options]`	Expose this instance via an edge tunnel
`switch-back [options]`	Reverse migration back to single-user (teammates lose access)

Read-only readiness check for the own-server migration

openship system migration preflight [options]

Option	Meaning
`--server-id <id>`	Target server id
`--hostname <host>`	Custom domain pointing at the server
`--slug <slug>`	Free <slug>.opsh.io subdomain

Migrate this instance onto your own server

openship system migration start [options]

Option	Meaning
`--server-id <id>`	Target server id
`--hostname <host>`	Custom domain pointing at the server
`--slug <slug>`	Free <slug>.opsh.io subdomain

Migrate this instance to Openship Cloud

openship system migration start-cloud [options]

Option	Meaning
`--allow-non-empty-target`	Proceed even if the cloud org already has projects

Expose this instance via an edge tunnel

openship system migration start-tunnel [options]

Option	Meaning
`--slug <slug>`	Tunnel slug

Reverse migration back to single-user (teammates lose access)

openship system migration switch-back [options]

Option	Meaning
`--abandon-remote`	Skip pulling remote data; keep the local DB as-is
`-y, --yes`	Skip the confirmation prompt