Discover
- Inventory of servers, databases and dependencies
- AWS Transform discovery for new AWS customers
- Existing Migration Hub data where an account already uses it
- Utilization data for sizing targets
AWS Migration
AWS migration services for apps and databases
Moving to AWS goes wrong in the details: a dependency nobody listed, a stored procedure that will not convert, a licence that does not travel. Agnotic Technologies migrates applications and databases to AWS with AWS's own tools and checks each of those details first.
Landing zone firstRehost and replatformDatabase migrationHIPAA eligibility checks
Trusted by global innovators
AWS migration
What do AWS migration services include?
AWS migration services move applications and databases into AWS using AWS's own migration tools. Agnotic Technologies discovers what you run, builds a Control Tower landing zone, rehosts servers with AWS Application Migration Service, moves databases with AWS DMS and schema conversion, and checks HIPAA eligibility before any health data moves.
This page covers AWS tooling and targets. Choosing a strategy per application, phasing and rollback planning are covered by our cloud migration and modernization service, and choosing a provider by cloud consulting.
AWS tooling changes. AWS closed Migration Hub and Application Discovery Service to new customers and points them to AWS Transform, so we confirm the current tool for each step at the start of every project.
Tooling
Which AWS tools run each migration stage?
The stages every AWS migration passes through, and the AWS service we use at each one.
Land
- AWS Control Tower landing zone
- Separate accounts per environment and workload
- Guardrails, central logging and IAM Identity Center access
- Network design and connectivity to your data centre
Replicate
- Application Migration Service agents on source servers
- Continuous block-level replication
- Test launches before cutover
- Post-launch actions such as agent installs
Move data
- AWS DMS full load plus ongoing change capture
- DMS Schema Conversion or AWS SCT for engine changes
- Row count and checksum validation
Cut over
- Final sync in a planned window
- DNS and connection string changes
- A rollback path kept until sign-off
Decision table
Which AWS target and tool fit each workload?
Typical starting points. The assessment confirms each one against your versions and licences.
| Source workload | AWS target | AWS tool | Main compatibility check |
|---|---|---|---|
| VMware virtual machine | Amazon EC2 | AWS Application Migration Service (AWS Transform MGN) | Operating system support for replication, and licence terms for software on the VM |
| Oracle database | Amazon RDS for Oracle, or Aurora PostgreSQL after conversion | AWS DMS, with schema conversion for a move to PostgreSQL | PL/SQL packages, data types and features with no PostgreSQL equivalent |
| SQL Server database | Amazon RDS for SQL Server, or SQL Server on EC2 | AWS DMS, or native backup and restore | Agent jobs, linked servers and instance-level features that RDS does not support |
| Windows or Linux file share | Amazon FSx or Amazon EFS | AWS DataSync | Permission model, file locking and the protocols clients use |
| Containerized application | Amazon ECS or Amazon EKS | Rebuilt images deployed from a CI pipeline | Persistent volumes, secrets and network policies that differ from the source cluster |
Failure points
What breaks during an AWS cutover?
Challenge
A hidden dependency, such as a nightly job calling a server nobody listed.
Agnotic approach
Dependency data from discovery plus interviews with application owners before the waves are set.
Challenge
Stored procedures that do not convert cleanly to the target engine.
Agnotic approach
Run schema conversion early and size the manual rewrite from its report, before the plan is fixed.
Challenge
Licences tied to hardware or hosts that do not carry over.
Agnotic approach
Check each vendor's cloud licence terms during discovery, before choosing EC2, RDS or a dedicated host.
Challenge
Replication lag at cutover stretches the downtime window.
Agnotic approach
Watch lag through the test launches and schedule the final sync for a low-traffic period.
Challenge
Security groups and IAM opened wide just to get things working.
Agnotic approach
Landing zone guardrails and least-privilege roles from the first account.
Health data
How do we migrate health data to AWS?
- Check every target service against the AWS HIPAA Eligible Services Reference before the design is final
- Review and accept the AWS Business Associate Addendum in AWS Artifact before any PHI moves
- Encrypt data in transit during replication and at rest with AWS KMS keys
- Log access with AWS CloudTrail from the first account in the landing zone
- Keep PHI out of test launches unless the test environment has the same controls
- Design to the list of PHI workloads your compliance lead confirms
Who do we run AWS migrations for?
Data centre exits
Racks and contracts coming to an end, with every workload needing a home on AWS.
VMware estates
Virtual machines rehosted to EC2 first, then modernized where it pays off.
Oracle and SQL Server owners
Databases moved as they are, or converted to PostgreSQL where the code allows.
Healthcare SaaS companies
Products holding PHI that need HIPAA eligible services and a BAA in place before the move.
Companies consolidating after an acquisition
Several AWS accounts and on-premises systems brought into one landing zone.
References
AWS references behind each migration
AWS Prescriptive GuidanceAWS Control TowerAWS Transform MGNAWS DMSAWS ArtifactHIPAA Eligible Services Reference
Facts and sources
Facts behind AWS migrations
From AWS's own documentation, read on 21 October 2026. Tool names and availability change, so we re-check them per project.
AWS Migration Hub has been closed to new customers since November 7, 2025, and AWS points new customers to AWS Transform for similar capabilities.
Source: AWS Migration Hub User GuideAWS Application Migration Service, now documented as AWS Transform MGN, performs continuous block-level replication of physical, virtual and cloud source servers and converts them for launch on AWS.
Source: AWS Transform MGN User GuideAWS Database Migration Service supports heterogeneous migrations between its supported database engines and encrypts data at rest with AWS Key Management Service.
Source: AWS Database Migration Service User GuideAWS Control Tower sets up and governs a multi-account AWS environment by orchestrating AWS Organizations, AWS Service Catalog and AWS IAM Identity Center to build a landing zone.
Source: AWS Control Tower User GuideCompanies subject to HIPAA typically need a Business Associate Addendum with AWS, which they review and accept in the AWS Artifact console for an account or a whole organization.
Source: AWS Artifact User Guide: managing agreements
Scope
What drives the scope of an AWS migration?
We do not publish prices or fixed timelines. These factors decide the size of the work.
Servers and databases
How many there are and how many share dependencies.
Engine changes
Moving Oracle or SQL Server as they are is smaller than converting to PostgreSQL.
Landing zone state
A new Control Tower setup, or fixing accounts that already exist.
Compliance scope
Which workloads hold PHI or other regulated data.
Cutover windows
How much downtime each system can accept, and when.
Hybrid connectivity
Systems that stay on premises and must keep talking to AWS.
Frequently Asked Questions
It depends on the number of servers and databases, any engine changes and the cutover windows each system allows. After discovery we plan in waves, and each wave gets its own test launch and cutover date.
Rehost with Application Migration Service when the application works and the goal is to leave a data centre quickly, then modernize later. The strategy per application is covered on our cloud migration and modernization page.
Yes. Schema conversion handles most objects, we rewrite the PL/SQL it cannot convert, and AWS DMS moves the data with ongoing change capture until a reconciled cutover.
AWS closed Migration Hub to new customers on November 7, 2025, and Application Discovery Service is also closed to new customers. AWS points new customers to AWS Transform, and we use whichever applies to your account.
Yes. We design the network for hybrid use, with VPN or AWS Direct Connect, and map which on-premises systems the migrated workloads still call.
AWS Transform uses AI agents for parts of discovery and planning. We treat its output as a proposal that an engineer checks, and nothing cuts over without a test launch and data reconciliation.