Skip to main content
Skip table of contents

Migrate

đź“‹ Overview

Migrate is a feature provided by Cloudamize that allows you to automate the migration of servers from groups defined in Migration Planner using the Hypercare approach. Where Migration Planner allows you to plan your cloud migration path, the Cloudamize Migrate allows you to manage the migration in full. Migrate integrates with both Migration Planner and Designer to enable you to automate and monitor the migration of groups using full CSP integrations, right-sizing provided by Cloudamize, and runbooks to assist with scheduling and planning the migration step by step.

Note: Currently, the Migrate feature is available only for AWS IAAS providers.

How to Use and Access the Migrate option:

How to Use and Access the Migrate option:

To access the Migrate option, please log in to the Cloudamize Console at https://console.cloudamize.com. Select Migrate on the Cloudamize Landing page.

image-20250106-095935.png

Once you click the Migrate option, you will land on the screen below.

image-20241016-092225.png

On this screen, you will be asked to add an AWS account. Click on the Add button. This will take you to the next screen, where you can download the AWS CloudFormation template. On this screen, you will also see the ParamCustomerId. You will need this ID on the AWS CloudFormation details page.

image-20241016-092335.png

Once you download the AWS CloudFormation Template file, please log into your AWS account and access the AWS CloudFormation option. This will take you to the screen below. Please use the Create Stack option to upload the downloaded AWS CloudFormation Template file in YAML format.

image-20241016-092417.png

The Create Stack screen will provide you with options to upload the downloaded AWS CloudFormation Template file. To upload the template file, please follow the steps below.

1 -> Please select the Upload a template file option as highlighted in the below screenshot.

2 -> Use the Choose file option to upload the downloaded AWS CloudFormation Template file in the YAML format.

3 -> Scroll down on the page and click next.

image-20241016-092504.png

4 -> On the Next page, please enter the Stack Name and the ParamCustomerId and click Next.

image-20241016-092533.png

5 -> On the Configure Stack Option page, no changes are required, and you can scroll down and click once again on the Next option.

6 -> On the Review and Create page, please scroll down, click on the acknowledgment check box, and then click on Submit.

image-20241016-092615.png

Once you have created the stack, you will see the created stack.

image-20241016-092647.png

Once the stack is created, access the Add Account screen, enter the AWS Account name and Account number/ID, and click Finish.

image-20250604-132827.png

Once the AWS account details are verified, you can click on the Start New option under the Migrations.

image-20241016-092803.png

On the next screen, you will be asked to enter the details below,

Name: You can give a unique Name for the migration. Please click on save once you have entered the name, this will allow you to proceed to the next step.

image-20250604-130550.png

Runbook: You can also use a Runbook to execute the Migration. Please note that you will be able to proceed to the next step only once the Runbook is set up.

Machine Selection: You can use any one of the options of the Business Application, Migration Strategy, Waves, or Machine Group that you want to use for migration. The Migration groups are pulled from the Application Tagging from the Plan section.

Platform: You can select the AWS IAAS provider. Note that currently, the Migrate feature is available only for AWS IAAS providers.

Design: You can also select the Design that you want to apply for migration.

image-20250604-084615.png

The View Included Instances option will show you the list of Instances in the Machine Group that you have selected for the Migration.

image-20241016-092916.png

Once you have filled in and selected all the details on the Migration details screen, select the AWS account name that you have added and click on Continue to the next step.

image-20241016-092955.png

The next screen will provide you with the option to install the MGN Agents on the Instances that are under the Migration group that was selected. The Credentials to install the MGN Agent will be generated in your AWS account and passed through the Cloudamize agent as part of the installation. You will also see an Advanced option on the screen. This option will allow you to select a subnet to launch the instances on the cloud. You can use this option if you wish to launch the servers in a specific Subnet, else you can ignore this option and click the MGN installation option.

Please make sure the Application Migration Service is enabled in the AWS console for the region where you're migrating the machines using MGN, before proceeding with the MGN agent installation.

MGN Agent Pre-requisites: Hardware (Minimum Sizing)

  • CPU: At least 1 vCPU

  • Memory: At least 2 GB RAM

  • Disk Space: At least 500 MB of free disk space

  • Network: Internet access to communicate with AWS endpoints (either via public internet or VPC endpoints)

  • ⚠️ Note: Machines with very low specs (e.g., Nano/ Micro instances) might fail due to insufficient memory or CPU throttling. AWS recommends at least t3.small or larger for smoother operations.

image-20241112-081151.png
image-20250618-073805.png

The Advanced option also provides you option to pass additional MGN Arguments, for example --tags WAVE=wave1. This is an example of an additional argument being passed to the MGN agent during its installation. In this specific case, it's setting a tag named WAVE with a value of wave1.

You can pass multiple arguments as provided in the AWS documentation below,
Linux: https://docs.aws.amazon.com/mgn/latest/ug/linux-agent.html
Windows: https://docs.aws.amazon.com/mgn/latest/ug/windows-agent.html

Once you launch the MGN Agent installation, you can click the Check Status option to view its status. The View Details option will provide you with the status of the MGN Agent installation on the instances.

image-20241111-083925.png

Now, once the MGN Agent installation is completed, you can click the button “Continue to next step”. On the next screen, you will see an option “Apply Right-sizing“.

image-20241111-090358.png

Apply Right-Sizing

Once you apply the right sizing, the next screen will show you that the right sizing has been applied and will provide you with the link to access the AWS console.

image-20241111-091019.png

Now, let’s generate the Low-Level Design document. To generate the document, please click on the 3 dots as shown in the screenshot and click the option “Generate Design Document”.

image-20241016-093146.png

Once the design document is generated, you will get the message at the top of the screen and an option to download the document.

image-20241016-093211.png

We have attached a sample Design Document file for your review.
lld(1).docx

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.