Migration
Migration
Soviez↔Soviez migration (--migration-*)
Migration (Soviez → Soviez)
Move a Production ERP environment from one Soviez-managed server to another with controlled cutover, rollback, and verification steps.
Overview
Migration is a multi-step workflow:
discover source → prepare destination → pair servers → readiness checks
→ domain/DNS/TLS → data transfer → activate destination → cutover
→ stabilization → archive source (operator-controlled)
Source data is never deleted automatically. Retiring the old server is always your explicit decision.
Migration command family
A single-flag migrate-in shortcut was never implemented. Use the --migration-* command family documented below and in CLI_REFERENCE.md.
Typical workflow
1. Discover and prepare
On the source server:
soviez.sh --migration-discover <production-id>
On the destination server:
soviez.sh --migration-bootstrap-destination [--confirm]
2. Pair servers
soviez.sh --migration-pair <production-id> --destination-code CODE [--confirm]
soviez.sh --migration-readiness <pair-id>
Readiness reports show blockers (DNS, disk, entitlement, Stage selection) before transfer starts.
3. Domain, DNS, and TLS
Migration includes dedicated steps for DNS validation, landing pages, and TLS on the destination. Follow --migration-dns-* and --migration-tls-* prompts for your domains.
4. Transfer data
soviez.sh --migration-transfer-start <pair-id> [--confirm]
soviez.sh --migration-transfer-status <operation-id>
Transfer is resumable. Use pause, resume, retry, and recover commands if interrupted.
5. Activate and cut over
soviez.sh --migration-activate-destination <pair-id> [--confirm]
soviez.sh --migration-cutover-start <pair-id> [--confirm]
Cutover switches traffic to the destination. A rollback window remains open until you close it explicitly.
6. Stabilize and retire source
After confirming the destination is stable:
soviez.sh --migration-rollback-window-close <cutover-id> [--confirm-phrase PHRASE]
soviez.sh --migration-source-archive-start <source-id>
Archive and retirement steps are operator-initiated. The source server is not purged without your confirmation.
Untrusted paths
Backups or data from untrusted sources may require quarantine and security scans before cutover. See RESTORE.md and SECURITY.md.
Status and recovery
soviez.sh --migration-status <operation-id>
soviez.sh --migration-reattach <operation-id>
soviez.sh --migration-recover <operation-id>
soviez.sh --migration-cutover-rollback <operation-id> [--confirm]
Detailed guides
| Step | Document |
|---|---|
| Destination setup | MIGRATION_DESTINATION_SETUP.md |
| DNS | MIGRATION_DNS_SETUP.md |
| Data transfer | MIGRATION_DATA_TRANSFER.md |
| Cutover | MIGRATION_CUTOVER.md |
| Authorization | MIGRATION_AUTHORIZATION.md |
Related
Source: canonical operator documentation · Permalink