You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/mongodb/pre-migration-steps.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,10 +34,9 @@ Your goal in pre-migration is to:
34
34
35
35
Follow these steps to perform a thorough pre-migration
36
36
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)
41
40
42
41
Then, execute your migration in accordance with your pre-migration plan.
43
42
@@ -49,11 +48,13 @@ When you plan a migration, we recommend that whenever possible you plan at the p
49
48
50
49
## Pre-migration assessment
51
50
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.
53
54
54
55
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.
55
56
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).
57
58
58
59
### Azure Cosmos DB Migration for MongoDB extension
59
60
@@ -78,6 +79,8 @@ Here are some tools you can use for discovering resources:
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.
0 commit comments