Working with migration factory

Import Server list configuration to the migration factory

1. Open c:\Migrations\Scripts folder and update 0-Migration-intake-form.csv. Update rows 2 to 5 with the following fields using the information collected in Event Engine dashboard Outputs screen from previous step (step 10 in Section 3).

Repeat the process for all the servers listed in the configuration file.

Migration Intake Form Key Current Value Event Engine dashboard value
subnet_IDs subnet-xxxxxxxx SubnetTargetPrivate
securitygroup_IDs sg-yyyyy TargetSecurityGroup
subnet_IDs_test subnet-xxxxxxxx SubnetTargetPrivate
securitygroup_IDs_test sg-yyyyy TargetSecurityGroup

intake form

If you prefer, try find/replace the following values: subnet-xxxxxxxx by SubnetTargetPrivate value and sg-yyyyy by TargetSecurityGroup value.

For this specific lab, we will use the same values for subnet_IDs and subnet_IDs_test, as well as for securitygroup_IDs and securitygroup_IDs_test. On a real CloudEndure migration, it is recommended to have a subnet/security group for the test migration environment and a subnet/security group for the target production environment.

2. Open windows command prompt and go to the c:\Migrations\Scripts directory

3. Run the following command:

0-Import-intake-form.py --Intakeform 0-Migration-intake-form.csv

4. Enter your Migration Factory username and password:

intake form

The Script will import all the servers from the CSV file to the Migration Factory

intake form

5. Login to the CloudEndure Migration Factory portal and check the current status for the servers

Automation tip: Managing a centralized configuration repository with information about applications, servers and subnets the servers should be migrated to will help to increase automation and reduce human error.

Automation tip: Group applications in migration waves. That helps to organize the cutover window for multiple applications. On this lab we have 1 migration wave composed by 2 Applications and 4 servers.