...
Alternatively, the Data Migration Toolkit now supports a multi-environment transfer option. If you are planning to utilize this option, it is important to inform the support team prior to your cutover day.
Open the below to see full instructions.
| Expand |
|---|
| title | Multi-Environment Transfer Instructions |
|---|
|
First you will create a JSON file to define the environment ID, which is called a DeploymentGuid and the name of the environment (folder name) on your local system EnvironmentName. Example of JSON [ { "DeploymentGuid": "c999ab9d-be99-9999-b99c-d99f99f99999", "EnvironmentName": "Environment1" }, { "DeploymentGuid": "c888ab9d-be99-8888-b99c-d99f99f88888", "EnvironmentName": "Environment2" }, { "DeploymentGuid": "c777ab9d-be99-7777-b99c-d99f99f77777", "EnvironmentName": "Environment3" } ]
To migrate multiple environments to the cloud-based storage, use the CopyEnvironmentToDropzone command but instead of -e you use -c. It's recommended to perform this operation when your system is under minimal load and has sufficient free RAM (at least 4GB). .\CHILI.Migration.CLI CopyEnvironmentToDropzone -d "C:\chili_data\Environments\" -c "C:\MyFolder\EnvironmentsToMigrate.json"
-d is the base path to the environments directory -c is the path to the configuration json |
Step 3: Notify the Customer Success team when the transfer is complete
...