01 / Current cluster
Connect your current installation
This pack is prepared for . The wizard checks the current installation and loads its settings. The installation stays running.
Current cluster access is included in your pack. Checking the connection…
This older download does not include current cluster access. Download a new migration pack from Settings after updating the installation, or use an existing access file below.
Already started a migration elsewhere? Reopen its original launcher or installation folder to keep the saved progress.
02 / Destination
Prepare the new home
Use an existing, fresh Kubernetes cluster. We check access before pausing the source. The domain, image registry, object store and backup repository stay the same.
What the destination needs
Linux amd64 nodes, Kubernetes 1.35 or newer, Cilium, suitable storage and a gateway load balancer. Several nodes need shared ReadWriteMany storage. The installer checks the supported environment before restoring.
This move creates a fresh bundled PostgreSQL database. External databases used by your applications need their own migration arrangements.
03 / Source backup
Pause and back up the source
Both clusters passed the connection checks. Active work will finish, then Software House and its applications will pause while their data is backed up.
The source stays paused until the destination takes over. You can cancel and resume the source until a destination claims this backup.
04 / Restore
Restore into the destination
The source stays paused. The installer creates fresh storage and restores the database, shared files, accounts and application volumes.
After the destination claims the backup, finish the move there. Cancellation back to the source is no longer available.
An interrupted restore uses the same verified snapshots and volumes when you retry.
05 / Traffic
Switch traffic and activate
Restored services stay paused until you activate them. Update the base and wildcard DNS records with your DNS provider.
The source remains stopped. Activation runs application and platform readiness checks.
06 / Verification
Verify the destination
The destination is running. Back it up, test recovery, then check the installation. These checks run automatically when selected.
Migration verified
The destination is ready
The installation evidence reports complete with no remaining actions. The source stays stopped. Keep it and the recovery material until the responsible owners make the retention decision.
The source has been resumed
The source is running with its old data. Point your base and wildcard DNS records back to the source and verify it before returning it to service. The destination remains stopped.
Progress and recovery
Operations will appear here as you move through the wizard.
| Operation | Result | Started |
|---|
Cancel this migration
The installer resumes the original workloads only if no destination has claimed this backup.
Protected files and resuming
The migration descriptor contains encryption keys and application credentials. It stays in the source state directory and is never downloaded through this page.
To reopen the wizard, run the same downloaded launcher. If you started with the command line installer, use the same configuration file with --migration-ui. Installer admission checks remain in force. An interrupted operation may require inspection of the retained Jobs or locks before it can continue.