Migration between Regions

Migrate an Environment Between Regions

Environment migration allows an existing project to be moved from its current region to another available region. This can help optimize infrastructure cost, improve performance, or relocate a production-ready application to more suitable hardware.

In this article

Migration Overview

When several environment regions are available, an existing environment can be relocated without rebuilding the project from the beginning. A common use case is to use cost-efficient hardware during development and testing, then move the finalized application to a higher-performance region before production release.

!

Migration availability depends on the provider

The migration feature and the list of available target regions are controlled by the hosting provider. Some accounts or regions may not support migration.

Environment regions migration overview
An environment can be moved between available infrastructure regions.

Open the Migration Settings

The migration window can be opened in either of the following ways.

Topology wizardClick Change Environment Topology, open the region list and select Migrate.
Environment settingsClick the Settings button for the required environment and open the Migration section.
1

Select the environment

Locate the environment that needs to be relocated.

2

Open Migration

Use either the topology wizard or the environment settings menu to open the migration panel.

Open environment migration settings
Open Migration from the topology wizard or environment settings.

Choose the Target Region

The migration panel displays the environment’s current region and provides a selector for the target region.

1

Review the current region

Confirm the source region shown in the migration window.

2

Select the target region

Choose the infrastructure region where the environment should be moved.

3

Review the migration mode

Check whether live migration is available for the selected region or whether offline migration will be used.

i

Review regional pricing before migration

Resource pricing may vary between regions. The target region’s pricing is applied automatically after migration, so review the available cost information before proceeding.

Select target region for environment migration
Select the target region and review the available migration mode.

Live Migration

Regions that support live migration are typically marked with an LM label. When such a region is selected, the live migration switch is normally enabled by default.

Application availabilityContainers are relocated without a full restart, helping users avoid service interruption.
Manual reconfigurationAdditional configuration is generally not required after completion.
Typical availabilityUsually offered between supported regions within the same data center.
Live migration switch for target region
The live migration switch appears for compatible target regions.
!

Do not use live migration for every workload

Avoid live migration for heavily loaded environments, active database containers or data-intensive systems. Short interruptions may occur, and freezing network or disk operations can risk data loss or corruption for active transactional workloads.

When live migration is not suitable, turn off the switch and use offline migration instead.

Offline Migration

Offline migration is used when live migration is unavailable, when the destination is in another data center, or when live migration has been disabled manually.

DowntimeThe entire environment is stopped and remains unavailable throughout the relocation process.
AvailabilityCan be used between any regions that support environment migration.
Possible changesNode IP addresses and, in some cases, the assigned domain name may change.
Post-migration workManual updates may be required for DNS, integrations, allowlists or application settings.
✓

Plan offline migration during a maintenance window

Because the environment is unavailable during relocation, schedule the operation during a low-traffic period and inform users in advance.

Complete and Verify Migration

1

Review all conditions

Confirm the target region, selected migration mode and any pricing or downtime implications.

2

Click Verify & Migrate

Start the validation process and review the confirmation message.

3

Confirm the migration

Approve the action in the confirmation dialog to begin relocation.

4

Verify the completed environment

After migration, confirm that the region label has changed, the application is accessible and all services operate correctly.

Confirm environment migration
Confirm the migration after reviewing the selected settings.

When migration is complete, the dashboard displays a notification and updates the environment’s region label. A confirmation email may also include migration duration, container-level details and any configuration changes caused by the relocation.

Expected Result

The environment is relocated to the selected target region. The dashboard reflects the new region, and the application resumes operation according to the chosen migration method.

Important Notes

  • Confirm that migration is supported for both the source and target regions.
  • Review the target region’s pricing before starting the process.
  • Use live migration only for workloads that can safely tolerate brief I/O or network pauses.
  • Prefer offline migration for active databases and high-load environments.
  • Plan a maintenance window when offline migration is required.
  • After migration, verify IP addresses, domain bindings, DNS records and external integrations.
  • Keep a recent backup before moving a production environment.

Common Issues and Solutions

Migration option is not visibleThe feature may be disabled by the hosting provider or unavailable for the selected environment.
Target region is missingConfirm that your account has access to the region and that migration is supported between the selected locations.
Live migration is unavailableThe target may be in another data center or may not support live migration. Use offline mode.
Application is briefly unavailableHigh load can cause a short interruption even during live migration. Retry during a lower-traffic period or use offline migration.
Application fails after offline migrationReview changed IP addresses, domain names, DNS records, firewall rules and external service configurations.
Unexpected cost after migrationCompare regional pricing and resource rates before moving the environment.

Related Guides