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: ConstraintModels/MigrationTools/README.md
-67Lines changed: 0 additions & 67 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,73 +65,6 @@ The **Multi Cloud Data Migrator** is a comprehensive tool for migrating Insuranc
65
65
- Support for complex product hierarchies
66
66
- Validation to ensure data integrity post-migration
67
67
68
-
#### How to Use the Multi Cloud Data Migrator
69
-
70
-
1. Install the Multi Cloud Data Migrator Plugin: ```sf plugins install sf-mcdm/multi-cloud-data-migrator```
71
-
1. Authorize the source org and target org:
72
-
```
73
-
sf auth:web:login --instance-url https://<source-instance>.salesforce.com -a srcOrg
74
-
sf auth:web:login --instance-url https://<target-instance>.salesforce.com -a tgtOrg
75
-
```
76
-
1. Check the connection: ```sf org list```
77
-
1. Open the Web App user interface: ```sf multi-cloud-data-migrator:ui```
78
-
1. Choose **Deep Clone Migration Plan** and **Revenue-Cloud-Advanced-Product**
79
-
1. Input your source and target org, and the root product's Stock Keeping Unit (SKU). You can enter multiple SKUs separated by commas.
80
-
1. Click **View Plan** and make sure all Key fields in the SObject are populated. **NOTE**: This is very important for clean product structure migration. See the **SObject Keys Reference**.
81
-
1. Click **Start Migration**, you can monitor the progress in the **Job Monitor** tab, and view issues in the **Failure and Skipped Files** tab.
82
-
83
-
#### SObject Keys Reference
84
-
85
-
For a successful migration, it's critical to ensure your data is clean and properly prepared.
86
-
87
-
- Check Your Keys: Use the **View Plan** button to review the migration strategy.
88
-
- Ensure Uniqueness: Verify that all Key fields and composite key combinations are populated and unique in the source data.
89
-
- Validate Data: Duplicate or missing keys will cause records to be skipped or linked incorrectly.
90
-
91
-
The migration will not run as expected if the underlying data quality is poor.
0 commit comments