When an installation exposes multiple regions, you can move a running environment from one to another without rebuilding it. This is the right tool when:
- The region you picked at creation no longer matches the workload — for example, you set up on a development-grade region and now need production-grade hardware.
- You want to relocate closer to a new user base.
- You want to consolidate environments into a single region to simplify operations.
Two modes are available:
- Live migration — no restart, no observable downtime for application users. Available only between certain region pairs (typically within the same data centre).
- Offline migration — the environment is stopped for the duration of the move. Available between any two regions the installation exposes for migration.
Migration availability depends on the installation operator’s configuration — some target regions may not be reachable from a given source.
Start a migration
Two ways to reach the migration dialog:
- Click Change environment topology and pick the Migrate option in the regions list at the top.
- Click Settings next to the environment and open the Migration menu entry.
Both surface the same dialog. It shows:
- Current region — where the environment lives now.
- Target region — where you want it to go.
- A Live migration section that varies based on the chosen target region.
Pricing in a target region may differ from the source — the dialog links out to the installation’s pricing reference so you can check before you commit.
Once you have chosen a target and a mode, click Verify & Migrate to begin. Confirm in the pop-up.
When the migration completes, the dashboard shows a status message and the region label next to the environment changes. You also receive an email with per-container migration duration and any parameter changes applied during the move.
Live migration
Regions that support live migration to your current region are marked with an LM label in the target list. Selecting such a region surfaces the Live migration toggle, enabled by default.
Live migration moves the environment without restarting any container. There is no manual configuration step on the application side. From the application user’s perspective, nothing happens — connections continue.
This is not always the right mode. Avoid live migration for:
- Heavily loaded environments and containers — under high load you can see a brief downtime (typically under 10 seconds) with a
502 - environment stoppederror. - Active database containers, big-data workloads — the freezes of network and disk IO during the move can lose or corrupt data that was in flight.
If you need to force offline mode despite the LM mark, flip the toggle off.
Offline migration
Offline migration applies when:
- The target region does not support live migration from the source (typically because it is in a different data centre).
- You disabled the Live migration toggle manually.
During an offline migration the environment is shut down for the duration of the move. Containers come back online after the migration is complete, with no manual reconfiguration needed in the normal case.
If offline migration is the only available mode, some environment settings may change as a side effect:
- Node IP addresses are reassigned.
- The auto-assigned domain name may change, depending on installation configuration.
The email you receive after the migration lists every changed parameter. If your application has any IP addresses or domains hard-coded in configuration, plan to update them as part of the move.
Choosing the mode
In a sentence: live when it is available and safe, offline when it is not. Live is the better default for stateless web tiers. Offline is the safer default for stateful workloads or any environment where the move spans data centres. The dialog will surface live as an option only when it is technically supported between the chosen regions — it is your call whether to use it from there.