Arkinu
AWS service comparison

AWS Transform MGN vs AWS DMS: differences and when to use each

AWS Transform MGN
AWS DMS

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Migration and Transfer

AWS Transform MGN

On the radar· Application Migration Service is now AWS Transform MGN

Automates the migration of physical, virtual, or other-cloud servers to AWS (rehosting) by continuously replicating them at the block level and converting them so they boot on AWS. As a result, the final cutover usually takes minutes. It was formerly called AWS Application Migration Service.

Exam phrases that point here

  • «migrate the servers as they are (lift-and-shift) to Amazon EC2»

    AWS Transform MGN (formerly AWS Application Migration Service) does rehosting: it replicates physical, virtual, or other-cloud servers and converts them so they boot as EC2 instances, without redesigning the application. It is the same service under its current name; in older questions it appears as Application Migration Service.

    When not: If you only need to move the data of a database, or change engines, it points to AWS DMS. If the goal is to redesign the application (for example, to containers or serverless) instead of moving it as is, MGN would only be a first step.

  • «migrate hundreds of servers with minimal downtime during cutover»

    Continuous block-level replication keeps an up-to-date copy of each disk in AWS; the cutover only launches the instances from that copy, which is why it usually takes minutes.

    When not: If what needs to move is files (not entire servers), the clue points to AWS DataSync; if it is databases that must keep receiving changes, to AWS DMS with CDC.

  • «test the migrated servers in AWS without affecting the source environment»

    MGN launches test instances from the replica while the source server keeps running and replicating; you can test as many times as needed before the cutover.

    When not: If the scenario is about testing changes to an application already in AWS with little risk (for example, blue/green deployments), the answer is in the deployment tools, not in MGN.

  • «move EC2 instances to another Region or to another AWS account»

    The sources MGN supports include EC2 instances themselves, to move them between Regions or accounts.

    When not: If the goal is a backup or disaster recovery across Regions, AWS Backup or AWS Elastic Disaster Recovery fits, not a migration with MGN.

  • «replicate the servers to AWS without using the public internet»

    MGN replication can go over a VPN, AWS Direct Connect, or another private connection, using private IPs to the staging subnet.

    When not: The private connection is a networking requirement, not a feature of the service: the same clue can appear with DataSync or DMS. What decides the answer is what is being moved: entire servers, files, or databases.

Often paired with

  • Amazon EC2
Study AWS Transform MGN →

Migration and Transfer

AWS DMS

On the radar· DMS Fleet Advisor is no longer supported

Service for migrating relational databases, data warehouses, NoSQL databases, and other data stores to AWS, or between the cloud and on-premises environments. It can perform a one-time migration or replicate ongoing changes to keep the source and target in sync, including between different engines.

Exam phrases that point here

  • «migrate the database to AWS with minimal downtime while the source database stays in use»

    AWS DMS does a full load and then replicates the ongoing changes (CDC), so the source database keeps serving the application and the cutover only waits for the target to catch up.

    When not: If what is being migrated is entire servers (operating system and application), it points to AWS Transform MGN (formerly AWS Application Migration Service). If the database is huge and there is not enough bandwidth, think of a physical transfer for the initial load and DMS only for the changes.

  • «migrate from Oracle or SQL Server to Amazon Aurora PostgreSQL»

    It is a heterogeneous migration: you first have to convert the schema and the code (procedures, functions) with DMS Schema Conversion or with AWS SCT, and then DMS moves the data.

    When not: If the target engine is the same as the source, there is no need to convert the schema: you use the engine's native tools or DMS homogeneous migrations.

  • «continuously replicate the changes from one database to another»

    A DMS task with CDC only, or with full load and CDC, can keep running indefinitely to keep source and target in sync.

    When not: If source and target are both Amazon RDS or Aurora of the same engine and the goal is high availability or read scaling, the service's own read replicas or Multi-AZ fit, not DMS. And DMS does not support replicating from on premises to on premises: one endpoint must be in AWS.

  • «load data from an operational database into Amazon Redshift or Amazon S3 for analytics»

    DMS supports S3 and Redshift as targets, in addition to relational databases, so it can feed a data lake or a data warehouse from a transactional database.

    When not: If the data does not come from a database but from files, the clue points to AWS DataSync; if it has to be transformed along the way, to AWS Glue.

  • «assess which parts of the schema will not be converted automatically to the new engine»

    DMS Schema Conversion generates an assessment report that separates what it converts on its own from what needs manual work, to estimate the effort before committing.

    When not: Schema conversion does not move data; that takes a DMS task. And to inventory which databases exist before choosing, another piece is used, such as AWS Migration Evaluator or the database discovery in AWS Transform. DMS Fleet Advisor, which played that role, reached end of support on May 20, 2026.

Often paired with

  • Amazon RDS
  • Amazon Aurora
  • Amazon Redshift
  • Amazon DynamoDB
Study AWS DMS →