Chapter 2

Cloud Migration Process and Phases (with Example)

Cloud migration refers to the process of moving data, applications, and other business
elements from an organization's on-premises infrastructure to a cloud environment.

🔁 Cloud Migration Phases

1. Assessment Phase

 Objective: Understand the current IT landscape and determine what should be moved
to the cloud.
 Activities:
o Inventory existing systems and applications.
o Analyze business goals and technical needs.
o Perform cloud readiness assessment.

📌 Example: A company evaluates its legacy customer relationship management (CRM)

software and realizes it’s outdated, costly, and hard to scale. It identifies this as a candidate
for cloud migration.

2. Planning Phase

 Objective: Develop a migration strategy and roadmap.

 Activities:
o Choose a cloud provider (e.g., AWS, Azure, GCP).
o Define migration goals (cost reduction, scalability, etc.).
o Choose migration approaches (Rehost, Refactor, etc.).

📌 Example: The company chooses AWS as the provider and decides to rehost the CRM app
using AWS EC2 virtual machines as a starting point.

3. Migration Phase (Execution)

 Objective: Migrate workloads, data, and applications to the cloud.

 Activities:
o Data migration using tools like AWS Database Migration Service.
o Application deployment on cloud infrastructure.
 o Test and validate performance.

📌 Example: The CRM database is migrated using AWS DMS, and the application is hosted
on EC2 with proper networking and security rules.

4. Testing and Validation Phase

 Objective: Ensure everything works in the cloud as expected.

 Activities:
o Conduct functionality, performance, and security testing.
o Validate integrations with other systems.
o Address issues and fine-tune configurations.

📌 Example: The company performs load testing on the new cloud-based CRM to ensure it
can handle user traffic, integrates with email services, and stores data correctly.

5. Optimization Phase

 Objective: Improve performance, cost-efficiency, and resilience.

 Activities:
o Right-size instances and services.
o Implement auto-scaling and monitoring.
o Apply security best practices.

📌 Example: After migration, the company realizes it can reduce costs by switching from on-
demand EC2 to reserved instances and enabling auto-scaling during peak sales months.

6. Operation and Maintenance Phase

 Objective: Maintain, monitor, and update cloud resources.

 Activities:
o Use tools for monitoring (e.g., CloudWatch).
o Manage patches and upgrades.
o Ensure compliance and backups.

📌 Example: The IT team sets up dashboards in AWS CloudWatch to monitor the CRM and
uses AWS Backup for daily snapshots.

✅ Summary Table
 Phase Key Activities Example
Inventory, readiness
1. Assessment Evaluate legacy CRM for migration
check
2. Planning Choose provider, strategy Select AWS, choose rehosting
3. Migration Move data/apps to cloud Use AWS DMS, deploy app on EC2
Validate performance, fix
4. Testing & Validation Run tests, fix CRM integration issues
bugs
Cost and performance Switch to reserved instances, enable
5. Optimization
tuning auto-scaling
6. Operation & Use CloudWatch, apply updates,
Monitor, patch, backup
Maintenance automate backups

Sure! Here's a clear explanation of Cloud Migration Strategies focusing on:

1. Hybrid Cloud Migration

2. Multi-Cloud Migration Approaches
3. Zero-Downtime Migration Techniques

Each includes real-world examples to aid understanding.

🌩️1. Hybrid Cloud Migration

✅ Definition:

Hybrid cloud migration involves integrating on-premises infrastructure with cloud

resources, allowing some workloads to remain on-premises while others move to the cloud.

🔧 Use Case:

 Organizations with sensitive data that must remain on-premises due to regulatory or
latency requirements.
 Businesses that want to migrate gradually rather than a full "lift-and-shift."

📌 Example:
A hospital maintains its patient records database on-premises (due to data privacy laws) but
migrates its appointment booking system to Azure cloud for better scalability and uptime.

🔄 Key Benefits:

 Flexibility in workload distribution

 Better security control for critical data
 Lower risk with phased migration

☁️2. Multi-Cloud Migration Approaches

✅ Definition:

Multi-cloud involves using two or more cloud providers (e.g., AWS, Azure, GCP) to avoid
vendor lock-in and improve redundancy, performance, or cost-efficiency.

🔧 Use Case:

 Organizations seeking best-of-breed services from multiple providers.

 Avoiding service disruption due to dependency on one vendor.

📌 Example:

A retail company hosts its web app backend on AWS for strong developer tools but uses
Google Cloud for AI-powered product recommendations because of its advanced machine
learning capabilities.

🧩 Approaches:

 Split-by-function: Different clouds for different functions (e.g., compute on AWS,

analytics on GCP).
 Split-by-region: Use different clouds in different geographic locations.
 Active-active: Apps run on multiple clouds simultaneously for high availability.

🔄 Key Benefits:

 Enhanced resilience and uptime

 Better service selection and cost control
 Compliance with data residency laws

🕒 3. Zero-Downtime Migration Techniques

✅ Definition:
Zero-downtime migration ensures the application remains available to users without service
interruption during the migration process.

🔧 Use Case:

 Critical services where even minutes of downtime can result in financial or

reputational loss (e.g., banking, e-commerce).

📌 Example:

An e-commerce website moves its product catalog system to the cloud while continuing to
serve live customer traffic. It uses blue-green deployment to switch traffic seamlessly to the
new environment.

🛠️Common Techniques:

1. Blue-Green Deployment:
Run two environments — one active (blue), one idle (green). Switch to green once it's
validated.
2. Canary Releases:
Gradually route traffic to the new system for testing in production.
3. Database Replication and Sync:
Keep data in sync between old and new systems during migration.
4. DNS Switching with TTL Control:
Gradually shift traffic using short Time-To-Live settings.

🔄 Key Benefits:

 Zero impact on end-users

 Easy rollback in case of issues
 Smooth transition with minimal risk

✅ Comparison Summary
Strategy Description Use Case Example
Gradual Hospital with on-prem
Hybrid Cloud Mix of on-prem + cloud
migration records, cloud bookings
Use of multiple cloud Avoid vendor Retailer using AWS + GCP
Multi-Cloud
vendors lock-in for app & ML
Zero-Downtime Continuous availability Critical E-commerce using blue-
Migration during migration services green deployment

Would you like this content as a presentation slide, infographic, or Word/PDF?

Certainly! Here’s a detailed explanation of Cloud Migration Strategies — including
Hybrid Cloud, Multi-Cloud, and Zero-Downtime Migration — with examples and small
code/program snippets for better understanding.

🌩️1. Hybrid Cloud Migration Program

📌 Example Scenario:

A bank stores customer financial data on its on-premise server (due to compliance) but uses
AWS to run customer-facing services like mobile banking.

🛠️Mini Program Example (Hybrid Setup):

Suppose a web app fetches data from an on-premise database but is hosted on the cloud.

Cloud-hosted Flask App (AWS EC2):

# cloud_app.py
from flask import Flask, jsonify
import requests

app = Flask(__name__)

@[Link]("/getCustomer")
def get_customer():
# Connect to on-premise API (through VPN or private connection)
response = [Link]("[Link]
return jsonify([Link]())

if __name__ == "__main__":
[Link](host='[Link]')

On-premise API (local network):

# on_prem_api.py
from flask import Flask, jsonify

app = Flask(__name__)

@[Link]("/api/customer")
def customer_data():
return jsonify({"name": "Suresh", "balance": 10000})

if __name__ == "__main__":
[Link](port=5000)
The cloud app fetches data securely from on-premises.

☁️2. Multi-Cloud Migration Approaches

✅ What is it?

Multi-Cloud Migration refers to using multiple cloud providers (e.g., AWS + Azure + GCP)
to optimize services, reduce vendor lock-in, or improve reliability.

📌 Example Scenario:

A media company uses:

 AWS S3 to store videos

 GCP Cloud Functions for AI-based thumbnail generation
 Azure SQL for user data

🛠️Mini Program Example (Multi-Cloud):

AWS S3 Upload Code (Python using boto3):

import boto3

s3 = [Link]('s3')
s3.upload_file('video.mp4', 'my-video-bucket', 'uploads/video.mp4')

GCP Cloud Function ([Link]) for Thumbnail:

[Link] = (file, context) => {

[Link](`Thumbnail generated for ${[Link]}`);
// call AI model or external tool to generate thumbnail
};

Azure SQL Insert (Python with pyodbc):

import pyodbc

conn = [Link]('DRIVER={ODBC Driver 17 for SQL

Server};SERVER=[Link];DATABASE=UserDB;UID=admin;PWD=Yo
urPassword')
cursor = [Link]()
[Link]("INSERT INTO Users (username, email) VALUES (?, ?)",
'user1', 'email@[Link]')
[Link]()

Each cloud service is used for what it's best at: storage, compute, and database.
🕒 3. Zero-Downtime Migration Techniques Program
✅ What is it?

Zero-Downtime Migration ensures that users do not experience any interruption when
systems are migrated or updated.

📌 Example Scenario:

An e-commerce website migrates its order service from a local server to AWS Lambda using
Blue-Green Deployment.

🛠️Program Example: Blue-Green Deployment Simulation

# Two versions of the same API: blue (current), green (new)

# blue_service.py (running on port 5000)

from flask import Flask
app = Flask(__name__)

@[Link]("/")
def home():
return "BLUE Version: Order Service v1.0"

[Link](port=5000)
# green_service.py (running on port 5001)
from flask import Flask
app = Flask(__name__)

@[Link]("/")
def home():
return "GREEN Version: Order Service v2.0"

[Link](port=5001)

Nginx Load Balancer Configuration:

# Switch between blue and green by changing port

server {
listen 80;
location / {
proxy_pass [Link] # Change to 5001 for green
}
}

Once the green version is tested, update Nginx to point from port 5000 (blue) to 5001 (green).
Cloud migration tools and services help organizations move their digital assets—applications,
data, and workloads—from on-premises infrastructure or one cloud to another efficiently,
securely, and with minimal disruption. These tools support various phases of migration
including assessment, planning, actual migration, and post-migration optimization.

🔧 Cloud Migration Tools and Services

1. Assessment & Planning Tools

These tools help evaluate the current environment, identify dependencies, and plan the
migration.

 Examples:
o AWS Migration Evaluator (formerly TSO Logic): (page no 11)
Analyzes on-premise infrastructure and recommends the most cost-effective
AWS services.
o Azure Migrate:
Assesses on-prem servers and provides a blueprint for moving workloads to
Azure.

2. Migration Tools

These tools perform the actual movement of data, applications, databases, and virtual
machines (VMs).

a) Data Migration Tools

 AWS DataSync: Transfers large volumes of data between on-premises storage and
AWS S3 or EFS. (page no 14)
 Google Transfer Service: Moves petabytes of data from other cloud providers or
local systems to Google Cloud Storage.
 Azure Data Box: Hardware device for transferring large data offline to Azure when
internet transfer is not feasible.

b) Database Migration Tools

 AWS Database Migration Service (DMS): (Page no 18)

Helps migrate databases like Oracle or MySQL to AWS with minimal downtime.
 Azure Database Migration Service:
Moves SQL Server, Oracle, or MySQL to Azure SQL or other Azure databases.

c) Application Migration Tools

 CloudEndure (AWS):
Continuous replication tool used for rehosting applications with minimal downtime.
  VMware HCX: Migrates VMware workloads to cloud environments like VMware
Cloud on AWS or Azure VMware Solution.

3. Post-Migration Monitoring and Optimization Tools

These tools ensure everything runs smoothly after migration and help optimize resources.

 AWS CloudWatch: Monitors cloud resources and applications on AWS.

 Azure Monitor & Application Insights: Provides performance monitoring and
diagnostics for Azure applications.
 Google Cloud Operations Suite (formerly Stackdriver): Offers observability for
Google Cloud services.

📌 Example Scenario: Cloud Migration Using Azure Tools

Company: ABC Ltd., a manufacturing firm

Need: Migrate on-premises data center to Microsoft Azure

Steps and Tools Used:

1. Assessment:
Tool: Azure Migrate
o Assessed VM performance and compatibility with Azure.
2. Database Migration:
Tool: Azure Database Migration Service
o Migrated SQL Server databases to Azure SQL Database.
3. Application Migration:
Tool: Azure Site Recovery
o Rehosted on-premises applications in Azure VMs.
4. Post-Migration Monitoring:
Tool: Azure Monitor
o Tracked application performance and resource utilization.

✅ Benefits of Using Migration Tools

 Reduced downtime
 Automated, error-free transfer
 Scalability and speed
 Cost optimization
 Minimal manual effort
If you want a comparison table of popular cloud migration tools across AWS, Azure,
and GCP, or a detailed migration plan, I can provide that as well.

AWS Migration Evaluator (formerly TSO Logic) is a cloud migration assessment tool
provided by Amazon Web Services (AWS) that helps organizations plan and optimize their
cloud migration journey. It delivers data-driven insights and cost modeling to assess the
potential benefits of moving on-premises workloads to AWS.

🔍 What is AWS Migration Evaluator?

AWS Migration Evaluator is a free service designed to help organizations understand:

 What workloads can be moved to AWS

 What the cost of running them on AWS would be
 What the optimal instance types and pricing models are
 How the on-premises environment compares to AWS cloud options

Migration Evaluator collects detailed usage data from your current environment and then uses
AWS intelligence to build a right-sized, cost-optimized migration plan.

🔄 Formerly Known As: TSO Logic

TSO Logic was a Canadian cloud migration analytics company acquired by AWS in 2019.
The TSO Logic technology was integrated into AWS and renamed Migration Evaluator.

🧰 Key Features of AWS Migration Evaluator

Feature Description
Gathers detailed server utilization data from on-premises
Automated Data Collection
systems.
Recommends optimal instance types, CPU, RAM, and
Right-Sizing Analysis
storage based on actual usage.
Provides pricing models such as On-Demand, Reserved
Cost Modeling
Instances, Savings Plans, and Spot Instances.
TCO Reports (Total Cost of Compares current infrastructure cost vs. AWS infrastructure
Ownership) cost.
Support for Hybrid Works with VMware, Hyper-V, physical servers, and even
 Feature Description
Environments partial cloud deployments.
Includes OS, licensing (e.g., Windows SQL Server), and
Detailed Recommendations
support options.

⚙️How AWS Migration Evaluator Works

Step 1: Data Collection

You deploy the Migration Evaluator Collector Agent or provide exported data (from
vCenter, CMDB, or other tools). The agent collects:

 Hardware configuration
 CPU, memory, and storage usage
 Network traffic
 Software inventory

Step 2: Upload and Analysis

The collected data is securely uploaded to AWS for analysis.

Step 3: Assessment Reports

AWS generates custom reports showing:

 AWS instance type recommendations

 Cost comparisons (On-prem vs. AWS)
 Savings opportunities
 Migration groupings

Step 4: Decision Making

You receive a Migration Assessment Report, which helps you plan your migration project
confidently.

📄 Outputs from Migration Evaluator

1. Executive Summary
o High-level cost savings and cloud-readiness insights.
2. Detailed Server Inventory
o Machine-level breakdown of utilization, specs, and recommendations.
3. TCO Model
o Monthly and yearly cost projection with various pricing models.
4. Licensing Strategy
o Guidance for BYOL (Bring Your Own License) vs. AWS licensing.
🎯 Benefits of Using AWS Migration Evaluator
✅ Data-driven decisions – reduces guesswork in cloud planning
✅ Cost optimization – helps avoid overprovisioning in AWS
✅ Accelerated migration – speeds up discovery and planning
✅ Free of charge – no cost to use, provided by AWS
✅ Supports hybrid strategies – helpful in phased migrations

💻 Use Case Example

Company A wants to migrate 500 on-prem servers (mostly VMware) to AWS. They don’t
know which instance types to use or what their AWS costs would be. Using Migration
Evaluator:

 They install the collector agent.

 Data is gathered over 1-2 weeks.
 AWS provides a report showing:
o 70% of servers are underutilized.
o Savings of $250K/year using Reserved Instances.
o Recommended EC2 types (e.g., [Link], [Link]).
o Optimal migration order and groupings.

🔐 Security and Compliance

 Data is encrypted in transit and at rest.
 You control the data shared with AWS.
 Complies with AWS security and privacy standards.

🔚 Summary

AWS Migration Evaluator (formerly TSO Logic) is a powerful, no-cost tool that helps
organizations make informed, cost-effective migration decisions. It leverages actual usage
data to recommend right-sized AWS infrastructure options, helping avoid overspending while
accelerating cloud adoption.

Would you like a sample AWS Migration Evaluator report format or diagram to visualize the
process?
✅ AWS DataSync – Detailed Explanation

AWS DataSync is a fully managed data transfer service that helps you move large-scale
data between on-premises storage, edge locations, and AWS services such as Amazon S3,
Amazon EFS, FSx, or even between AWS regions.

It automates much of the complexity involved in data migration, including scheduling,

validation, encryption, monitoring, and performance tuning.

🚀 Why Use AWS DataSync?

DataSync is ideal for:

 Data migration to the cloud

 Ongoing data transfers for hybrid workloads
 Backup or disaster recovery
 Data replication across regions or storage systems

🧰 Key Features of AWS DataSync

Feature Description
Moves data up to 10x faster than traditional tools like rsync or
🔄 High-Speed Transfer
scp.
🔐 Secure Transfers Uses TLS encryption in transit and encryption at rest in AWS.
⚙️Automated Tasks Automates data copy, validation, and metadata preservation.
📅 Scheduling Support Transfer jobs can be scheduled hourly, daily, or weekly.
🖥️Broad Storage Supports NFS, SMB, Amazon S3, EFS, FSx for Windows, and FSx
Support for Lustre.
📊 Monitoring &
Integrated with Amazon CloudWatch and AWS CloudTrail.
Logging

🛠️How AWS DataSync Works

🔁 Architecture Overview

1. Source:
o On-premises NFS/SMB file servers
o AWS services (e.g., EFS, S3)
o Other cloud providers (using S3-compatible API)
 2. DataSync Agent:
o A VM (available as VMware, Hyper-V, or EC2 AMI)
o Installed on-premises to read from your file system and push to AWS
3. AWS DataSync Service:
o Manages transfer, throttling, integrity checks, encryption
4. Destination:
o Amazon S3 (object storage)
o Amazon EFS (file system)
o Amazon FSx (Windows or Lustre)
o Another AWS Region or account

🔄 Types of Transfers
Type Use Case
🡆 On-Prem to AWS Migrate or back up data to AWS storage
🡄 AWS to On-Prem Restore data or maintain hybrid workflows
🔁 AWS to AWS Copy between regions or services (e.g., S3 to EFS)

📥 Example Use Case

Company B has 10 TB of log files stored on a NAS (NFS) that they want to move to
Amazon S3 Glacier for archival. Steps:

1. Install AWS DataSync Agent on-prem (VMware).

2. Connect DataSync to the NFS share.
3. Configure a DataSync task to send files to S3 Glacier.
4. Schedule the job or run it once.
5. Monitor the task through CloudWatch.

Benefits: They avoid writing custom scripts, get bandwidth optimization, and secure transfer.

📋 Key Components in AWS Console

Component Description
Task Defines the transfer: source, destination, filters, options.
Location Describes source/destination paths (e.g., NFS server, S3 bucket).
Agent On-prem appliance that connects to local storage.
Task Execution An instance of a transfer task, can be monitored or repeated.

🔐 Security Features
  TLS in transit
 Encryption at rest (AWS KMS integration)
 IAM role-based access
 Activity logging via CloudTrail

💲 Pricing Model
 Charged per GB transferred
Example (subject to change):
~$0.0125 per GB for data copied using DataSync (excluding AWS storage cost)

✅ No additional charge for the agent

✅ Can use DataSync for free under AWS Free Tier (up to 1 GB/month)

🆚 AWS DataSync vs Traditional Tools

Tool Speed Management Monitoring Reliability
AWS
✅ High ✅ Fully managed ✅ CloudWatch ✅ Built-in
DataSync
❌ No native AWS ❌ Requires
rsync / scp ❌ Slower ❌ Manual setup
monitoring scripting

📦 AWS Services Integrated with DataSync

 Amazon S3 – Store object data
 Amazon EFS – Elastic file storage for EC2
 Amazon FSx – Windows or high-performance file systems
 CloudWatch – Metrics and alerts
 CloudTrail – Auditing and logging
 AWS Storage Gateway – Hybrid access

✅ Summary
Feature Description
Service Name AWS DataSync
Primary Use Fast, automated data transfers to/from AWS
Deployment Via agent (on-prem) + console configuration
Destinations S3, EFS, FSx, other AWS services
Benefits Secure, fast, scalable, automated, pay-as-you-go
Would you like:

 A visual diagram of DataSync flow?

 A step-by-step guide to setting up DataSync?
 A comparison with AWS Transfer Family or Snowball for specific scenarios?

Let me know how deep you want to go!

Certainly! Here’s a detailed explanation of AWS Database Migration Service (AWS

DMS):

✅ What is AWS Database Migration Service (AWS DMS)?

AWS Database Migration Service (DMS) is a fully managed service that helps you
migrate databases quickly and securely to AWS. You can use it to migrate your on-
premises databases to AWS, between AWS services, or even between different database
engines (heterogeneous migration).
It supports both one-time migrations and ongoing replication, making it useful for real-
time data streaming, disaster recovery, and database consolidation.

🎯 Use Cases
Use Case Description
Lift-and-Shift Move entire database as-is from on-premises to AWS
Live Migration Migrate with minimal downtime using continuous replication
Heterogeneous Move from one database engine to another (e.g., Oracle to
Migration PostgreSQL)
Data Warehousing Load data into Amazon Redshift for analytics
Disaster Recovery Replicate from on-premises or between AWS regions
Consolidation Merge multiple databases into a centralized database on AWS

🛠️Key Features of AWS DMS

Feature Description
🔄 Homogeneous and Migrate between same DB engines (e.g., Oracle to Oracle)
Heterogeneous Migrations or different ones (e.g., SQL Server to MySQL)
🔁 Continuous Data Replication Real-time sync using Change Data Capture (CDC)
⚙️Schema Conversion Tool
Helps convert schema between different DB engines
(SCT)
🔐 Secure Transfers Supports encryption in transit and at rest
📊 Monitoring Integrated with Amazon CloudWatch
💰 Low Cost Pay only for compute resources used during migration

📋 Supported Source and Target Databases

✅ Supported Sources

 Oracle
 Microsoft SQL Server
 MySQL, MariaDB
 PostgreSQL
 MongoDB
 SAP ASE (Sybase)
 Amazon RDS
 Amazon S3 (for JSON/CSV data)
 Google Cloud SQL, Azure SQL

✅ Supported Targets

 Amazon RDS (MySQL, PostgreSQL, Oracle, SQL Server, MariaDB)

  Amazon Aurora (MySQL/PostgreSQL-compatible)
 Amazon Redshift
 Amazon DynamoDB
 Amazon S3 (data lake)
 Amazon Kinesis
 MongoDB
 On-premises databases

🔄 How AWS DMS Works

🔁 Step-by-Step Workflow

1. Set Up Source and Target Endpoints

Provide connection details for source (e.g., Oracle) and target (e.g., Amazon Aurora).
2. Create a Replication Instance
This instance manages the migration process; choose based on database size and load.
3. Configure Migration Task
Decide whether to migrate data once, replicate changes (CDC), or both.
4. Run the Task
DMS migrates the schema (optional) and/or data. Logs and metrics are available in
CloudWatch.
5. Monitor and Verify
Monitor task progress, data validation, and performance through AWS Console or
CLI.

🧪 Types of Database Migrations

Type Description Example
Same DB engines (e.g., Oracle →
🟩 Homogeneous Fast and simple
Oracle)
Different DB engines (e.g., Oracle →
🟨 Heterogeneous Requires schema conversion
PostgreSQL)
🟦 One-time Load Migrate full data once For new projects or testing
🟥 Ongoing For live cutover with near-zero
Keep source and target in sync
Replication downtime

🧰 AWS Schema Conversion Tool (AWS SCT)

Used alongside DMS when source and target engines differ (heterogeneous migration):

 Converts schema, tables, views, indexes, triggers

 Analyzes compatibility
 Converts application SQL (stored procedures, functions)
  Provides migration assessment reports

🔐 Security Features
 Encryption in-transit via TLS/SSL
 Encryption at-rest using AWS KMS
 IAM-based access control
 Network isolation using VPCs and security groups

📊 Monitoring & Logging

 Amazon CloudWatch for performance metrics and alerts
 DMS Console for visual task tracking
 Task Logs for diagnostics and troubleshooting

💰 Pricing Model
 Hourly cost for replication instance (based on vCPU/RAM)
 No charge for DMS software
 Storage and data transfer costs apply (if used)
 Free tier available (up to 750 hours per month for 6 months for small instances)

💻 Example: Migrating SQL Server to Amazon Aurora

1. Install AWS Schema Conversion Tool to convert schema
2. Set up source (SQL Server) and target (Aurora) in DMS
3. Create a replication instance (e.g., [Link])
4. Launch migration task: full load + CDC
5. Monitor progress and validate results

Result: Minimal downtime migration from SQL Server to a cloud-native PostgreSQL engine.

✅ Summary Table
Feature AWS DMS
Fully Managed ✅ Yes
Real-time Replication ✅ Yes
 Feature AWS DMS
Homogeneous Migration ✅ Yes
Heterogeneous Migration ✅ Yes (via SCT)
Schema Conversion ⚠️Only with AWS SCT
Monitoring ✅ CloudWatch
Downtime 🔄 Minimal (with CDC)
Use Cases Migration, sync, DR, consolidation

📌 When to Use AWS DMS vs. Other Tools

Tool Use When
AWS DMS Need fast, secure, ongoing or one-time DB migration
SCT Converting schema for heterogeneous DB migration
AWS Snowball Need petabyte-scale offline transfer
AWS Glue/Athena ETL and analytics on semi-structured data

Would you like:

 A step-by-step setup guide for AWS DMS?

 Architecture diagram?
 Use-case specific configuration (e.g., Oracle to Redshift)?

Let me know your specific interest.