Add migration info

Author: Lori Krell

guides/v2.1/cloud/live/sens-data-over.md

@@ -24,10 +24,6 @@ It provides the following benefits:
 These new methods are optional but strongly recommended. The process ensures faster deployments and consistent configurations across your environments.
 </div>
 
-<div class="bs-callout bs-callout-info" markdown="1">
-If you used configuration management in 2.1, this process is similar in 2.2. The name of the file has changed to `config.php` and updating the file changed. You can [migrate](#migrate) your `config.local.php` settings to a new `config.php`.
-</div>
-
 ## Feature availability {#release}
 Configuration management was released in `magento-cloud-configuration` 101.4.1 on {{site.data.var.ece}} 2.1.4 and later. The options and functions differ in {{site.data.var.ece}} 2.2. We provide recommendations for {{site.data.var.ece}} deployments in this section.
 
@@ -187,18 +183,5 @@ To complete extensive changes:
 While you can manually edit `config.local.php` in Staging and Production, we don't recommend it. The file helps keep all of your configurations consistent across all of your environments.
 </div>
 
-## Migrate config.local.php to config.php {#migrate}
-If you upgrade to {{site.data.var.ece}} 2.2 or later, you may want to migrate settings from `config.local.php` to your new `config.php` file. If the configuration settings in your Magento Admin match the contents of the file, you can follow the instructions to generate and add `config.php`.
-
-If they differ, you can append content from `config.local.php` to your new `config.php` file:
-
-1. Follow instructions to generate the `config.php` file using the [recommended method](#cloud-config-specific-recomm).
-2. Open `config.php`and delete the last line.
-3. Open `config.local.php`and copy the contents.
-4. Paste the contents into `config.php`, save, and complete adding it to Git.
-5. Deploy across your environments.
-
-You only need to complete this migration once. When you need to update the file, you will always update the new `config.php`.
-
 #### Next step
 [Example of managing system-specific settings]({{ page.baseurl }}cloud/live/sens-data-initial.html)

guides/v2.2/cloud/live/sens-data-over.md

@@ -26,6 +26,10 @@ It provides the following benefits:
 These new methods are optional but strongly recommended. The process ensures faster deployments and consistent configurations across your environments.
 </div>
 
+<div class="bs-callout bs-callout-info" markdown="1">
+If you used configuration management in 2.1, this process is similar in 2.2. The name of the file has changed to `config.php` and updating the file changed. You can [migrate](#migrate) your `config.local.php` settings to a new `config.php`.
+</div>
+
 ## Feature availability {#release}
 Configuration management was released in `magento-cloud-configuration` 101.4.1 on {{site.data.var.ece}} 2.1.4 and later. The options and functions differ in {{site.data.var.ece}} 2.2. We provide recommendations for {{site.data.var.ece}} deployments in this section.
 
@@ -187,5 +191,18 @@ To complete extensive changes:
 While you can manually edit `config.php` in Staging and Production, we don't recommend it. The file helps keep all of your configurations consistent across all of your environments.
 </div>
 
+## Migrate config.local.php to config.php {#migrate}
+If you upgrade to {{site.data.var.ece}} 2.2 or later, you may want to migrate settings from `config.local.php` to your new `config.php` file. If the configuration settings in your Magento Admin match the contents of the file, you can follow the instructions to generate and add `config.php`.
+
+If they differ, you can append content from `config.local.php` to your new `config.php` file:
+
+1. Follow instructions to generate the `config.php` file using the [recommended method](#cloud-config-specific-recomm).
+2. Open `config.php`and delete the last line.
+3. Open `config.local.php`and copy the contents.
+4. Paste the contents into `config.php`, save, and complete adding it to Git.
+5. Deploy across your environments.
+
+You only need to complete this migration once. When you need to update the file, you will always update the new `config.php`.
+
 #### Next step
 [Example of managing system-specific settings]({{ page.baseurl }}cloud/live/sens-data-initial.html)