Cargando...
Cargando...
Centralized tracking and orchestration for every migration across AWS and partner tools
AWS Migration Hub provides a single place to discover existing servers, plan migrations, and track the status of each application migration across multiple AWS and partner migration tools. It does NOT perform migrations itself — it aggregates status from tools like AWS Application Migration Service (MGN), AWS Database Migration Service (DMS), and partner solutions into one unified dashboard. Think of it as the air traffic control tower: it sees everything but flies nothing.
Provide a single pane of glass for tracking migration progress across heterogeneous tools, teams, and environments without replacing those tools
Use When
Avoid When
Centralized migration tracking dashboard
Aggregates status from all connected migration tools into a single view
Application grouping
Group discovered servers into logical applications (e.g., a 3-tier web app) for holistic tracking
AWS Application Discovery Service integration
Automatically ingests discovery data when ADS is enabled in the same Home Region
Migration Hub Strategy Recommendations
Analyzes app data and recommends 7Rs migration strategies (Rehost, Replatform, Refactor, etc.)
Migration Hub Refactor Spaces
Provides infrastructure scaffolding for incremental application modernization
Migration Hub Orchestrator
Automates and orchestrates migration workflows using predefined or custom templates
Partner tool integration
Supports AWS Partner Network migration tools that have built Migration Hub connectors
Direct migration execution
Migration Hub does NOT move data or replicate servers — it only tracks
Cost optimization recommendations
Use AWS Trusted Advisor or Compute Optimizer for post-migration optimization
Compliance monitoring
Use AWS Config for compliance and configuration drift detection
Schema conversion
Use AWS Schema Conversion Tool (SCT) for database schema conversion; DMS handles data migration
Cross-account migration tracking
Can track migrations across accounts when properly configured with the Home Region
Progress percentage tracking
Shows per-server and per-application migration completion percentages
API access
Migration Hub API allows programmatic status updates from custom migration tools
Discover → Group → Track
high freqApplication Discovery Service (ADS) collects server inventory and dependency data from on-premises environments. This data flows automatically into Migration Hub (when both are in the same Home Region), where servers are grouped into logical applications and tracked throughout migration. This is the canonical pre-migration discovery pipeline.
Lift-and-Shift Tracking
high freqAWS Application Migration Service (MGN) performs the actual server replication and cutover (Rehost strategy). MGN automatically reports migration status back to Migration Hub, allowing teams to see replication progress, test instances, and cutover status in the unified dashboard. MGN is the successor to CloudEndure Migration.
Database Migration Tracking
high freqDMS performs the actual database migration (full load + CDC for ongoing replication). DMS task status is reported to Migration Hub, giving a unified view of both server and database migrations. Note: DMS migrates data; AWS Schema Conversion Tool (SCT) converts the schema — these are separate tools.
Post-Migration Operational Handoff
high freqAfter Migration Hub confirms a migration is complete, Systems Manager takes over for ongoing operational management (patch management, inventory, run commands). Migration Hub is a migration-phase tool; Systems Manager is the operational-phase tool. Exam questions often test whether you know where Migration Hub's role ends.
Compliance Validation Post-Migration
high freqMigration Hub tracks migration progress; AWS Config monitors configuration compliance of migrated resources. They are complementary but serve different phases. Config does NOT provide migration tracking, and Migration Hub does NOT provide compliance monitoring. Exam questions frequently mix these up.
Migration Health and Optimization Guidance
high freqTrusted Advisor provides real-time guidance on service limits, cost optimization, security, and fault tolerance — critically important DURING large migrations to avoid hitting service quotas. Migration Hub tracks WHERE you are in the migration; Trusted Advisor warns you WHAT might go wrong. Both are needed in large-scale migrations.
Automated Migration Workflow
medium freqMigration Hub Orchestrator provides workflow templates (e.g., SAP migration, VMware migration) that automate the sequencing of migration tasks. It integrates with MGN, DMS, Systems Manager, and other tools to execute migrations in a defined order, with Migration Hub providing the tracking overlay.
7Rs Strategy Planning
medium freqStrategy Recommendations analyzes your application portfolio data (from ADS or manual import) and recommends one of the 7Rs strategies (Retire, Retain, Rehost, Relocate, Replatform, Repurchase, Refactor/Re-architect). This is the planning phase before actual migration tracking begins.
Migration Hub TRACKS migrations — it does NOT perform them. If a question asks how to migrate servers, the answer is MGN or DMS, not Migration Hub. If a question asks how to get a unified view of migration progress, the answer IS Migration Hub.
The Home Region must be selected BEFORE any data is stored and CANNOT be changed. All migration data — from ADS, MGN, DMS, and partner tools — must be sent to the Home Region. Exam scenarios about 'where is migration data stored' always point to the Home Region concept.
AWS Trusted Advisor is critical DURING migrations for monitoring service limits (e.g., EC2 instance limits, VPC limits). A common exam scenario: a large migration is failing because of service quota exhaustion — the answer involves Trusted Advisor for monitoring limits, NOT Migration Hub.
Know the 7Rs of migration and which AWS service executes each: Rehost = MGN, Replatform = DMS/Elastic Beanstalk, Refactor = re-architecture using native services, Repurchase = SaaS replacement, Relocate = VMware Cloud on AWS, Retire = decommission, Retain = keep on-premises. Migration Hub TRACKS all of these but executes none.
Migration Hub TRACKS, not MIGRATES: Always distinguish between 'how to get visibility into migration progress' (Migration Hub) vs. 'how to actually migrate servers/databases' (MGN for servers, DMS for databases). This distinction determines the correct answer on ~40% of Migration Hub exam questions.
Home Region is permanent: The Migration Hub Home Region cannot be changed after data is stored. Exam scenarios testing multi-region migration architecture expect you to know this constraint and plan accordingly upfront.
Trusted Advisor monitors SERVICE LIMITS during migrations — not just costs. When an exam scenario describes a large migration hitting resource quota errors, the monitoring solution is Trusted Advisor (Service Limits checks), not Migration Hub, Config, or CloudWatch alone.
AWS Config monitors configuration COMPLIANCE of existing resources — it does NOT provide migration recommendations or optimization suggestions. If an exam question asks about 'ensuring migrated resources comply with security policies,' the answer is Config. If it asks about 'cost optimization recommendations,' the answer is Trusted Advisor or Compute Optimizer, NOT Config or Migration Hub.
Application Discovery Service (ADS) has two collection methods: (1) Agentless — VMware vCenter only, uses the ADS Agentless Collector; (2) Agent-based — Discovery Agent installed on each server, works for physical servers and non-VMware hypervisors. Exam questions about physical server discovery require the agent-based approach.
DMS migrates DATA; AWS Schema Conversion Tool (SCT) converts the DATABASE SCHEMA. These are separate tools. A question about migrating an Oracle database to Aurora PostgreSQL requires BOTH SCT (schema conversion) AND DMS (data migration). Migration Hub tracks the DMS task but has no visibility into SCT activities.
Migration Hub Orchestrator provides pre-built workflow TEMPLATES for common migrations (SAP, VMware). If an exam question mentions automating the sequencing and coordination of migration steps, Orchestrator is the answer — not Step Functions (though Step Functions could theoretically do it, Orchestrator is the purpose-built answer).
Migration Hub Strategy Recommendations is a PLANNING tool that uses the 7Rs framework to recommend what to do with each application. It is NOT a tracking tool and NOT a migration execution tool. Exam scenarios about 'determining the best migration strategy for a portfolio of applications' point to Strategy Recommendations.
AWS Application Migration Service (MGN) replaced CloudEndure Migration as the primary AWS rehost service. If you see CloudEndure Migration in an exam question, treat it as functionally equivalent to MGN for the purposes of the question. MGN reports status to Migration Hub automatically.
Common Mistake
AWS Migration Hub can be used to migrate servers and databases — it's an all-in-one migration service.
Correct
Migration Hub is ONLY a tracking and visibility tool. It aggregates status from actual migration tools (MGN for servers, DMS for databases) but performs zero migration actions itself. Think of it as a flight tracker app — it shows where planes are but doesn't fly them.
This is the #1 misconception. Exam questions are designed to trick candidates into selecting Migration Hub when the question asks HOW to migrate, not HOW to track migrations. Always ask: 'Does this question want tracking/visibility or actual migration execution?'
Common Mistake
AWS Trusted Advisor is only useful for cost optimization recommendations.
Correct
Trusted Advisor provides checks across FIVE pillars: Cost Optimization, Performance, Security, Fault Tolerance, and SERVICE LIMITS. During large migrations, the Service Limits pillar is critically important — it warns you when you're approaching EC2, VPC, EBS, or other service quotas that could block your migration.
Exam questions about 'a migration is failing because of resource limits' expect you to know that Trusted Advisor monitors service limits in real time. Candidates who only associate Trusted Advisor with cost optimization will choose the wrong answer.
Common Mistake
AWS Config provides optimization recommendations and migration guidance for migrated workloads.
Correct
AWS Config is a COMPLIANCE and CONFIGURATION HISTORY tool. It records resource configurations over time and evaluates them against rules — it does NOT recommend optimizations or guide migrations. For optimization recommendations, use Trusted Advisor (broad) or Compute Optimizer (compute-specific). For migration guidance, use Migration Hub Strategy Recommendations.
This misconception causes candidates to confuse Config's 'evaluation' capability with active recommendations. Config tells you 'this resource is non-compliant with rule X' — it does not say 'you should switch to a smaller instance to save money.'
Common Mistake
DMS handles both schema conversion and data migration for heterogeneous database migrations.
Correct
DMS handles DATA migration (full load and/or change data capture for ongoing replication). For heterogeneous migrations (e.g., Oracle to Aurora PostgreSQL), you ALSO need AWS Schema Conversion Tool (SCT) to convert the database schema, stored procedures, and application code. They are separate tools that work together.
Exam questions about heterogeneous database migrations (different source and target engines) always require BOTH SCT + DMS. Missing SCT means the schema won't exist on the target database. Homogeneous migrations (e.g., MySQL to MySQL) do NOT require SCT.
Common Mistake
You can change the Migration Hub Home Region at any time if your requirements change.
Correct
The Home Region is selected ONCE and is PERMANENT for that AWS account. All migration data is stored in the Home Region. If you need to change it, you would need to start with a new AWS account. This is a hard architectural constraint, not a soft preference.
Exam scenarios about multi-region migration strategies may tempt candidates to think they can have multiple Home Regions or change it mid-migration. The correct answer always involves careful upfront planning of the Home Region selection.
Common Mistake
Migration Hub provides ongoing operational recommendations and monitoring after migration is complete.
Correct
Migration Hub's role ends when the migration is complete. For post-migration operations, use: AWS Systems Manager (patch management, inventory, run commands), AWS Trusted Advisor (ongoing cost/security/performance guidance), AWS Compute Optimizer (right-sizing recommendations), and AWS Config (compliance monitoring). Migration Hub is a migration-phase tool only.
Exam questions about 'what to use AFTER migration is complete' are traps for candidates who think Migration Hub is a permanent operational tool. Once the migration is done, Migration Hub's value is historical — operational tools take over.
TRACK not ACT: Migration Hub TRACKs migrations, it doesn't ACT on them — for action, use MGN (servers) or DMS (databases)
HOME is FOREVER: The Home Region is like your permanent address — you choose it once and you're locked in
7Rs in order of effort: Retire → Retain → Relocate → Rehost → Repurchase → Replatform → Refactor (Think: 'Really Relaxed Robots Rarely Run Poorly Refactored')
Config = Compliance Cop (records and evaluates), Trusted Advisor = Wise Advisor (recommends improvements across 5 pillars), Migration Hub = Mission Control (tracks progress) — three different roles, three different tools
DMS + SCT = Complete Database Migration: DMS moves the DATA, SCT converts the SCHEMA — you need BOTH for heterogeneous migrations
CertAI Tutor · SAA-C03, SAP-C02, DEA-C01, SCS-C02, CLF-C02 · 2026-02-22