Migrate between regions
In this article you learn how to move a project from one region to another on Umbraco Cloud.
Last updated
Was this helpful?
In this article you learn how to move a project from one region to another on Umbraco Cloud.
Last updated
Was this helpful?
Creating a project on Umbraco Cloud, you can choose to host the project in different regions: East US, West EU, South UK, or East Australia.
In some cases, you might want to migrate your project(s) from one region to another. This article will outline the steps to do this.
The East US and West EU regions will be used as examples in this article.
Admin access and deployment rights on the project that is to be migrated.
A clone of both East US and West EU projects.
A local setup that can run an Umbraco instance. Learn more about this in the article.
The first step in this process is to create a new Umbraco Cloud project in the region you want to migrate your existing project to. In this case that will be the East US region.
This is done by selecting East US from the Region dropdown when creating the Cloud project.
The new project in the US region will run the latest version of Umbraco CMS, Umbraco Forms, and Umbraco Deploy. You will need to ensure that the project you are migrating is running the exact same version of each product before initiating the migration process.
The following steps will guide you through the migration process.
Go to Configuration > Backups on the West EU Cloud project.
Create a backup of the projects database.
Download the backup to your local machine.
Go to the East US project.
Go to Configuration > Backups.
Upload the database backup that you created in the previous step to the project.
Restore the backup to your environment
Optional: Create a backup of the environment before restoring the backup.
Run Export Schema from the Deploy Dashboard in the Settings section of the East US project.
Run Update Umbraco Schema from the Deploy Dashboard in the Settings section of the East US project.
Once you have restored the database to your environment, go to the backoffice of the project you are migrating to. In the backoffice, you should now see your content in the Content section, Document Types, and Data Types in the Settings section.
Taking a closer look at the templates, stylesheets, scripts and media, you will notice that it is not there. In the next step we will migrate those over to our new project
In this step, we will migrate our files and media items from our project in the EU region.
Clone down both the projects to your local machine.
Run the local East US project and restore the content.
Open both the project folders for West EU and East US.
Move the view files located in the view folder from West EU to the view folder in the East US project.
When prompted replace the existing files.
Move the CSS and Script files located in the wwwroot folder from the West EU folder to the wwwroot folder in the East US project.
Optional: Move files from App_Plugins if you have extended the Umbraco Backoffice
Move custom code (Models, Controllers and other relevant code) from the West EU to the East US project
Run the East US project locally.
Once you have started the project, it should show your content as it was on the West EU project. The only thing missing is the media items, as they have not been migrated yet. Before we can migrated our media items, we need to push the migrated files to the Cloud project.
In the following steps, we will push the migrated local East US project back up to the project on Cloud.
Verify that all schemas, files, and content have been successfully deployed to your new US project after the transfer.
In the following steps, we will migrate media items from the West EU blob storage container to the East US blob storage container using AzCopy.
Extract the binary to a directory on your local machine and ensure you can run it from the command line.
Access the Umbraco Cloud Portal for the West EU project.
Open the Connections page found under Configuration.
Locate the SAS URLs.
Ensure the SAS tokens can read from the West EU container.
Access the Umbraco Cloud Portal for the East US project.
Open the Connections page.
Locate the SAS URLs and ensure the tokens can write to the East US container.
Use the following AzCopy command to transfer the media files from the West EU container to the East US container:
azcopy copy "<West-EU-SAS-URL>" "<East-US-SAS-URL>" --recursive
Replace <West-EU-SAS-URL> with the SAS URL of the West EU blob storage container.
Replace <East-US-SAS-URL> with the SAS URL of the East US blob storage container.
The --recursive flag ensures that all files and subfolders are copied.
Verify the files in the East US container using AzCopy: azcopy list "<East-US-SAS-URL>"
Check that all expected media files have been successfully transferred.
Reload the front end and backoffice of the East US project to confirm the images are displayed correctly.
The migration process is complete when the media files have been migrated to the East US environment.
## Post-migration tasks
Following the steps above you have migrated your Umbraco project from one Cloud environment to another.
The following will need to be reconfigured on the new project after the initial migration:
All Team Members added through the Cloud Portal on the EU project also need to be invited to the migrated project
Hostnames, certificates, and other related settings must be re-added and reconfigured on the migrated project.
Once everything has been configured and set up you can safely delete the EU project which will also cancel the running subscription on the project.
Find more details on how to upgrade your project in the documentation.
Make sure that your projects are before continuing the process.
Follow the article to push the Views, CSS and JavaScript files to the Cloud environment.
Follow the article to transfer the media items to the cloud project.
Download AzCopy Portable Binary from the .
If you need help or have any questions regarding this process, please contact our support using .
