Skip to content

Commit fb11c0e

Browse files
author
Sandeep Nair
committed
fixed language
1 parent 7a5489a commit fb11c0e

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/cosmos-db/mongodb/pre-migration-steps.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -34,10 +34,9 @@ Your goal in pre-migration is to:
3434

3535
Follow these steps to perform a thorough pre-migration
3636

37-
1. [Discover your existing MongoDB resources and create a data estate spreadsheet to track them](#pre-migration-discovery)
38-
2. [Assess the readiness of your existing MongoDB resources for data migration](#pre-migration-assessment)
39-
3. [Map your existing MongoDB resources to new Azure Cosmos DB resources](#pre-migration-mapping)
40-
4. [Plan the logistics of migration process end-to-end, before you kick off the full-scale data migration](#execution-logistics)
37+
1. [Discover your existing MongoDB resources and Assess the readiness of your existing MongoDB resources for data migration](#pre-migration-assessment)
38+
2. [Map your existing MongoDB resources to new Azure Cosmos DB resources](#pre-migration-mapping)
39+
3. [Plan the logistics of migration process end-to-end, before you kick off the full-scale data migration](#execution-logistics)
4140

4241
Then, execute your migration in accordance with your pre-migration plan.
4342

@@ -49,11 +48,13 @@ When you plan a migration, we recommend that whenever possible you plan at the p
4948

5049
## Pre-migration assessment
5150

52-
The first pre-migration step is to discover your resources and assess the readiness of resources in your data estate for migration.
51+
The first pre-migration step is to discover your existing MongoDB resources and assess the readiness of your resources for migration.
52+
53+
Discovery involves creating a comprehensive list of the existing resources (databases or collections) in your MongoDB data estate.
5354

5455
Assessment involves finding out whether you're using the [features and syntax that are supported](./feature-support-42.md). It also includes making sure you're adhering to the [limits and quotas](../concepts-limits.md#per-account-limits). The aim of this stage is to create a list of incompatibilities and warnings, if any. After you have the assessment results, you can try to address the findings during rest of the migration planning.
5556

56-
There are 3 ways to complete the pre-migration steps, we recommend you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension).
57+
There are 3 ways to complete the pre-migration assessment, we recommend you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension).
5758

5859
### Azure Cosmos DB Migration for MongoDB extension
5960

@@ -78,6 +79,8 @@ Here are some tools you can use for discovering resources:
7879
* [MongoDB Shell](https://www.mongodb.com/try/download/shell)
7980
* [MongoDB Compass](https://www.mongodb.com/try/download/compass)
8081

82+
Go through the spreadsheet and verify each collection against the [supported features and syntax](./feature-support-42.md), and [Azure Cosmos DB limits and quotas](../concepts-limits.md#per-account-limits) in detail.
83+
8184
### Database Migration Assistant utility (legacy)
8285

8386
> [!NOTE]

0 commit comments

Comments
 (0)