Updated Migrating regions cloud article to use new backup feature and import/export features on cloud and deploy.

umbraco-cloud/getting-started/migrate-between-regions.md

@@ -6,7 +6,7 @@
 
 # Migrate between regions
 
-When creating a project on Umbraco Cloud, you can choose to host the project in different regions: East US, EU West, South UK, or East Australia.
+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.
 
@@ -15,11 +15,11 @@
 ## Prerequisites
 
 * Admin access and deployment rights on the project that is to be migrated.
-* Git is installed locally as well as a Git client like _Git Bash_.
+* 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 [Requirements](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements) article.
 
 {% hint style="info" %}
-To follow this guide, it is highly recommended that you have experience with Git and running git commands through a command line tool.
+If you want to migrate a Umbraco 8 project, you will need to upgrade to the latest supported [Long-Term-Supported (LTS)](https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/) version of Umbraco CMS.
 {% endhint %}
 
 ## Prepare your projects
@@ -42,81 +42,70 @@
 Make sure that your projects are [prepared for migration](migrate-between-regions.md#prepare-your-projects) before continuing the process.
 {% endhint %}
 
-{% tabs %}
-{% tab title="Umbraco 10+" %}
-1. Clone down the project that you want to migrate - the _EU project_.
-2. Restore content and media through the Umbraco backoffice.
-3. Clone down the new Cloud project created in the US region - the _US project_.
-4. Replace the `src/UmbracoProject/umbraco-cloud.json` file in the _EU project_ with the one from the _US project_.
-
-{% hint style="info" %}
-The `umbraco-cloud.json` file contains details about each environment on the Cloud project.
-
-By replacing the one on the _EU project_ with the one from the _US project_, content, and media transfers will point to the environments on the _US project_ instead of the _EU project_.
-{% endhint %}
-
-5. Commit the change through git, but do not push it yet.
-6. Use the following git commands to connect your local _EU project_ to the live environment on the _US project_:
+### Step 1: Creating and restore database backup
 
-```
-git remote rm origin
-
-git remote add origin https://scm.umbraco.io/useast01/name-of-us-live-site.git
-
-git fetch
-
-git branch --set-upstream-to=origin/master
-```
+{% tab title="Umbraco 10+" %}
+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 a **Export Schema** and then **Update Umbraco Schema** from the **Deploy Dashboard** in the settings section of the **East US** project.
 
-7. Push the schema and files from the _EU project_ to the _US project_ using the following git command:
+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, and Document Types and Data Types in the settings section.
 
-```
-git push origin master -f
-```
 
-8. Verify that the schema and files have been merged into the live environment on the _US project_.
-9. Transfer content and media from the local _EU project_ to the _US project_.
-10. Verify that all the content and media have been transferred to the _US project_.
-{% endtab %}
+Taking a closer look at the templates, stylesheets, scripts media, you will notice that it is not there. In the next step we will migrate those over to our new project
 
-{% tab title="Umbraco 8" %}
-1. Clone down the project that you want to migrate - the _EU project_.
-2. Restore content and media through the Umbraco backoffice.
-3. Clone down the new Cloud project created in the US region - the _US project_.
-4. Replace the `Config/UmbracoDeploy.config` file in the _EU project_ with the one from the _US project_.
 
-{% hint style="info" %}
-The `UmbracoDeploy.config` file contains details about each environment on the Cloud project.
+### step 2: Migrate files
 
-By replacing the one on the _EU project_ with the one from the _US project_, content, and media transfers will point to the environments on the _US project_ instead of the _EU project_.
-{% endhint %}
+In this step, we will migrate our files and media items from our project on the EU region. 
 
-5. Commit the change through git, but do not push it yet.
-6. Use the following git commands to connect your local _EU project_ to the live environment on the _US project_:
+1. Clone down both project to your local machine.
+2. Run the local East US project and restore the content.
+3. Open project folders from both **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 promted 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.
+6. **Optional:** Move files from App_Plugins if you have extended the Umbraco Backoffice
+7. Run the **East US** project locally.
 
-```
-git remote rm origin
+Once you have started the project up, the project should show your content as it was on the **West EU** project. The only thing missing will be the media items, as they have not been migrated over yet.
 
-git remote add origin https://scm.umbraco.io/useast01/name-of-us-live-site.git
+### Step 3: Migrate Media Items
 
-git fetch
+In the following step we will migrate our media items from our **West EU** project to our **East US** project.
 
-git branch --set-upstream-to=origin/master
-```
+1. Run the **West EU** on your local machine
+2. Go to the media section on the **West EU** project.
+3. Click on the 3 dots in the top of the media section.
+4. Click **Export** in the side-menu.
+5. Click the button to export the media items located in the media section.
+6. Click **Download** to download the zip file with the media items to your local machine.
+7. Run the **East US** project on your local machine.
+8. Navigate to the media section.
+9. Click the 3 dots in the top of the media section.
+10. Click **Import** in the side menu.
+11. Click **Select ZIP file**.
+12. Select the ZIP file, that you downloaded from the **East US** project.
+13. Click **Import**.
+
+Once the import has finished refresh your media section, and clicking on an image, you should be able to see it. Navigate to the front end of your local **East US** project and the images will be shown on the front end as well now.
 
-7. Push the schema and files from the _EU project_ to the _US project_ using the following git command:
+Now that we have sorted everything out, it is time to push the changes back up to our **East US** environment.
 
-```
-git push origin master -f
-```
+### Step 4: Pushing migrated project to Cloud
 
-8. Verify that the schema and files have been merged into the live environment on the _US project_.
-9. Transfer content and media from the local _EU project_ to the _US project_.
-10. Verify that all the content and media have been transferred to the _US project_.
-{% endtab %}
-{% endtabs %}
+In the following steps we will show, how you can push the migrated local **East US** project back up to the project on Cloud.
 
-Once you have verified that all schema and files as well as content and media have successfully been deployed and transferred to your new _US project_ the migration process is complete.
+1. Follow the [Deploying Changes](https://docs.umbraco.com/umbraco-cloud/deployments/local-to-cloud) article to push the Views, CSS and JavaScript files to the Cloud environment.
+2. Follow the [Transferring Content, Media, Members, and Forms](https://docs.umbraco.com/umbraco-cloud/deployments/content-transfer#media-items)article to transfer the media items to the cloud project.
+
+Once the media items, Views and styling has been transfered, verified that all schema and files as well as content and media have successfully been deployed and transferred to your new _US project_ the migration process is complete.
 
 It is highly recommended to thoroughly go through everything on the migrated site to ensure that everything works as expected.