← Back to Blogs

CLOUD MIGRATION

Migrating On-Premises Workloads to AWS

A successful migration starts with understanding the application and its dependencies. Use a staged plan to choose the right approach, validate the target environment, and prepare your team for operations after the move.

1. Discover what you are moving

Inventory servers, databases, operating systems, application owners, and integrations. Map dependencies such as DNS, identity, scheduled jobs, certificates, file shares, and external systems. Record utilisation, data volumes, maintenance windows, and recovery requirements.

2. Choose an approach for each workload

Rehost

Move a suitable workload with limited application changes, then plan improvements after stabilisation.

Replatform

Make targeted changes, such as adopting a managed database, while retaining much of the application.

Refactor

Redesign application components when business needs justify the additional development and testing.

Retain or retire

Keep workloads in their current location when appropriate, or remove systems that are no longer needed.

3. Prepare the AWS environment

Establish accounts, access controls, networking, logging, backup policies, and cost visibility before production migration. Define connectivity to existing systems and plan how identities, secrets, and configuration will be managed.

4. Select tools against workload requirements

AWS Transform MGN, formerly AWS Application Migration Service, supports rehosting eligible physical, virtual, and cloud servers to Amazon EC2. AWS Database Migration Service can support database migration scenarios. Confirm operating system support, database compatibility, permissions, network capacity, and any schema conversion work before selecting a tool.

5. Test and migrate in waves

Begin with a representative pilot. Validate application functions, performance, integrations, permissions, backups, and monitoring in the target environment. Group dependent workloads into migration waves. Agree on a cutover window, data validation checks, rollback conditions, and the people responsible for each decision.

6. Stabilise and improve after migration

Monitor errors, response times, utilisation, and costs during the stabilisation period. Confirm backup restore procedures and operational handover. Right-size resources using observed demand, and assess modernisation opportunities once the migrated workload is stable.

Prepare for the migration conversation

Bring a server and application inventory, database details, licensing information, dependency notes, and expected timelines. Anjana Cloud9 Solutions can help assess the environment and develop a migration plan aligned with your business priorities.

Official resources

Continue reading

Windows Workloads in the Cloud

Read article →

Navigating Success with AWS Well-Architected

Read article →

Planning a similar project? Talk to our team.