Umbraco Cloud
CMSHeartcoreDXPMarketplace
  • What is Umbraco Cloud?
  • Frequently asked questions
  • Security
    • Web Application Firewall
  • Sustainability Best Practices
  • Getting Started
    • Explore Umbraco Cloud
    • The Cloud Portal
      • Organizations
      • Sustainability Dashboard
    • Project Overview
    • Environments
    • Flexible Environments (beta)
    • Baselines
      • Baseline Merge Conflicts
      • Break Reference between Baseline and Child Project
      • Handling configuration files
      • Pushing Upgrades to a Child Project
    • Plans
    • Migrate to Umbraco Cloud
    • Repositories in a Cloud Project
    • Best Practice for Working in Teams
    • Migrate between regions
  • Set up
    • Ready to Set Up Your Project?
    • Working with a Local Clone
      • Legacy Umbraco Visual Studio Setup
    • Manage Environments
    • Project Settings
      • Managing Transport Security
      • CDN Caching and Optimizations
      • Dedicated Resources
      • Upgrade your Plan
      • Public Access
      • Managing Hostnames
        • New Certificate Authority for custom hostnames
        • Rewrite rules
        • Custom Certificates
      • Management API Security
      • Umbraco CI/CD Flow
        • Cloud API For CI/CD Flow
        • Configuring a CI/CD pipeline
          • Azure DevOps
          • GitHub Actions
        • Troubleshooting
        • Known Limitations and Considerations
      • External Services
      • Usage
        • Bandwidth
      • Availability and Performance
      • Team Members
        • Technical Contact
      • Secrets Management
      • Project History
    • Private NuGet Feed on Umbraco Cloud
    • Going Live
    • Media
    • External Login Providers
    • Azure Blob Storage
      • Connect to Azure Storage Explorer to upload files manually
      • Connect and Upload Files Programmatically to Azure Blob Storage
    • Users
    • Multi-Factor Authentication
    • Application Insights
    • Config Transforms
    • SMTP Settings
    • Payments
      • Subscription migration information and FAQ
    • Power Tools (Kudu)
      • View the Files on your Cloud Environments
      • Generate UDA files
      • Manually run Extractions on your Cloud Environments
  • Deployments
    • Deployment
    • Deploying between environments
    • Transferring Content, Media, Members, and Forms
    • Deploying Deletions
    • Deployment Webhook
    • Deploying Changes
    • Umbraco Forms on Cloud
    • Deploy Dashboard
    • Hotfixes
      • Apply hotfix by manually moving files
      • Apply hotfix by using Git
    • Restoring Content
      • Partial Restores
  • Databases
    • Keep Your Data Secure and Accessible
    • Working with databases
    • Database backups
    • Database
      • Connecting to the Database on Mac
    • Working with a Cloud database locally
  • Product Upgrades
    • Stay Up to Date with Umbraco Cloud
    • Product Upgrades
    • Major Upgrades
    • Minor Upgrades
    • Version Specific Upgrades
      • Migrate from Umbraco 8 to the latest version
      • Migrate from Umbraco 7 to Umbraco 8 on Umbraco Cloud
    • Upgrade your projects manually
      • Manual upgrade of Umbraco CMS
      • Manual upgrade of Umbraco Deploy
    • Dependencies on Umbraco Cloud
  • Troubleshooting
    • Resolve Issues Quickly and Efficiently
    • Troubleshooting FAQ
    • Log files
    • The Umbraco Backoffice
    • The Frontend
    • The Umbraco Cloud Portal
    • Site Performance checklist
    • Troubleshooting deployments
      • Extraction error: Config transforms failing
      • Extraction error: Data Type collisions
      • Dependency Exception
      • Merge Conflicts on Flexible Environments
      • Troubleshooting deployments failing with no error message
      • Troubleshooting duplicate dictionary items
      • Troubleshooting language mismatches
      • Path too long Exception
      • Schema Mismatches
      • How to resolve collision errors
      • Extraction error: "Type not found! "
    • Cloud Errors
  • Release Notes
    • Overview 2025
      • April 2025
      • March 2025
      • February 2025
      • January 2025
    • Overview 2024
      • December 2024
      • November 2024
      • October 2024
      • September 2024
      • August 2024
      • July 2024
      • May 2024
      • April 2024
      • March 2024
      • February 2024
      • January 2024
    • Overview 2023
      • December 2023
      • October 2023
      • September 2023
      • August 2023
      • June 2023
      • May 2023
      • April 2023
      • March 2023
      • February 2023
      • January 2023
    • Overview 2022
      • December 2022
      • November 2022
      • September 2022
      • August 2022
      • June 2022
      • May 2022
      • April 2022
      • March 2022
      • February 2022
      • January 2022
Powered by GitBook
On this page
  • Prerequisites
  • Prepare your projects
  • Migrate the project
  • Step 1: Create and Restore Database Backup
  • Step 2: Migrate Files
  • Step 3: Push the Migrated Project to Cloud
  • Step 4: Migrate Media Items
  • Related articles

Was this helpful?

Edit on GitHub
Export as PDF
  1. Getting Started

Migrate between regions

In this article you learn how to move a project from one region to another on Umbraco Cloud.

PreviousBest Practice for Working in TeamsNextReady to Set Up Your Project?

Last updated 4 months ago

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.

Prerequisites

  • 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.

If you want to migrate an Umbraco 8 project, you will need to upgrade to the latest supported version of Umbraco CMS.

Prepare your projects

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.

Migrate the project

The following steps will guide you through the migration process.

Step 1: Create and Restore Database Backup

  1. Go to Configuration > Backups on the West EU Cloud project.

  2. Create a backup of the projects database.

  3. Download the backup to your local machine.

  4. Go to the East US project.

  5. Go to Configuration > Backups.

  6. Upload the database backup that you created in the previous step to the project.

  7. Restore the backup to your environment

    • Optional: Create a backup of the environment before restoring the backup.

  8. Run Export Schema from the Deploy Dashboard in the Settings section of the East US project.

  9. 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

Step 2: Migrate Files

In this step, we will migrate our files and media items from our project in the EU region.

  1. Clone down both the projects to your local machine.

  2. Run the local East US project and restore the content.

  3. Open both the project folders for West EU and East US.

  4. 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.

  5. 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

  6. Move custom code (Models, Controllers and other relevant code) from the West EU to the East US project

  7. 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.

Step 3: Push the Migrated Project to Cloud

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.

Step 4: Migrate Media Items

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.

Download AzCopy Portable Binary

  1. Extract the binary to a directory on your local machine and ensure you can run it from the command line.

Locate the Shared Access Signature (SAS) URLs

  1. Access the Umbraco Cloud Portal for the West EU project.

  2. Open the Connections page found under Configuration.

  3. Locate the SAS URLs.

  4. Ensure the SAS tokens can read from the West EU container.

  5. Access the Umbraco Cloud Portal for the East US project.

  6. Open the Connections page.

  7. Locate the SAS URLs and ensure the tokens can write to the East US container.

Copy the Media Files

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 File Transfer

  1. Verify the files in the East US container using AzCopy: azcopy list "<East-US-SAS-URL>"

  2. Check that all expected media files have been successfully transferred.

  3. 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.

Recommendation It is highly recommended that the migrated site be thoroughly reviewed to ensure all media items function as expected.

## 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.

Related articles

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 .

Upgrades
Deploying Changes
Transferring Content, Media, Members, and Forms
official Microsoft AzCopy page
contact@umbraco.com
Manage hostnames
Team Members
Certificates
prepared for migration
Requirements
Long-Term-Supported (LTS)
Select the East US region