Tweaks

Author: KumarVivek

powerapps-docs/developer/common-data-service/cds-odata-dataflows-migration.md

@@ -1,13 +1,13 @@
 ---
 title: Migrate data between Common Data Service instances with dataflow OData connector
-author: demora
+author: denisem-msft
 ms.reviewer: "nabuthuk"
 description: Migrate data between Common data Service instance using Power Platform OData connector.
 no-loc: [Title, Document]
 ms.date: 05/05/2020
 ms.service: powerapps
 ms.topic: "article"
-manager: "kvivek" # MSFT alias of manager or PM counterpart
+ms.author: demora
 search.audienceType: 
   - developer, maker
 search.app: 
@@ -22,30 +22,19 @@ In this article, we walk you through how to migrate data between Common Data Ser
 
 ## Prerequisites
 
-1. System Administrator or System Customizer security role permission on both source and the target environments.
+- System Administrator or System Customizer security role permission on both source and the target environments.
 
-1. Premium Power Apps, Power Automate, or Common Data Service license (per app or per user)
+- Premium Power Apps, Power Automate, or Common Data Service license (per app or per user)
 
-1. Two environments with Common Data Service instances provisioned.
+- Two environments with Common Data Service instances provisioned.
 
 ## Scenarios
 
  - A one-time cross-environment or cross tenant migration is needed (for example, geo-migration)
 
  - Developer needs to update an app that is being used in production. Test data is needed in their development environment to easily build out changes. 
 
-## Steps
-
-The following steps are required to migrate data:
-
-1. [Plan out the dataflow](#plan-out-the-dataflow)
-1. [Get the OData endpoint](#get-the-odata-endpoint)
-1. [Create a new OData dataflow](#create-a-new-odata-dataflow)
-1. [Select and transform data with the Power Query experience](#select-and-transform-data-with-the-power-query)
-1. [Configure destination environment settings](#configure-destination-environment-settings)
-1. [Run the dataflow](#run-the-dataflow)
-
-## Plan out the dataflow
+## Step 1: Plan out the dataflow
 
 1. Identify the source and target environments.
 
@@ -64,7 +53,7 @@ The following steps are required to migrate data:
 > [!NOTE]
 > The words to describe a Common Data Service `instance` and `environment` are used interchangeably in this article. Each environment in the Power Platform can have 0 or 1 Common Data Service instance(s). More information: [Create Common Data Service database](https://docs.microsoft.com/power-platform/admin/create-database).
 
-## Get the OData endpoint 
+## Step 2: Get the OData endpoint 
 
 Common Data Service provides an OData endpoint that does not require any additional configuration to authenticate with the dataflows connector. It is relatively easy process to connect to the source instance. 
 
@@ -87,7 +76,7 @@ From the **source** environment, get the [OData endpoint](https://docs.microsoft
     > [!div class="mx-imgBorder"]
     > ![Copy the service root URL in the developer resources](./media/get-odata-endpoint-url.png)
  
-## Create a new OData dataflow
+## Step 3: Create a new OData dataflow
 
 In the **target** environment, create a new dataflow with the OData connector.
 
@@ -124,7 +113,7 @@ In the **target** environment, create a new dataflow with the OData connector.
     
 1. Select **Next** in the bottom right.
 
-## Select and transform data with the Power Query 
+## Step 4: Select and transform data with the Power Query 
 
 Use the Power Query, which allows to select the tables and also allows the transformation of data.
 
@@ -149,11 +138,11 @@ First, select the entities that need to be transferred. You can browse all entit
 
 1. Select **Next** in the bottom right.
 
-## Configure destination environment settings
+## Step 5: Configure destination environment settings
 
 This section describes how to define the target instance settings.
 
-### Map entities 
+### Step 6: Map entities 
 
 For each entity chosen, select the behavior for importing that entity in these settings and select **Next**.
 
@@ -180,11 +169,11 @@ For each entity chosen, select the behavior for importing that entity in these s
 
 - There is an option to **Do not load**, but do not include entities in the dataflow that are not being loaded. You can select **Back** from this menu to return to the Power Query menu and remove the entities that are not needed.
 
-### Refresh settings
+### Step 7: Refresh settings
 
 Select **Refresh manually** since this is a one-time migration ad select **Create**. 
 
-### Run the dataflow
+### Step 8: Run the dataflow
 
 The initial dataflow load initiates when you select the **Create** button.