# Migrating SQL Server
In your journey to the cloud, you have multiple options for migrating your SQL Server environments to AWS. A successful [migration](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/welcome.html) is based on generating a detailed inventory of your SQL Server workloads and their dependencies, identifying your authentication scheme, capturing your high availability and disaster recovery (HADR) requirements, assessing your performance targets, and evaluating your [licensing options](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/SQLServer.Concepts.General.Licensing.html). This inventory helps you determine the target database platform and define your migration options.
You have many options to consider when migrating your SQL Server workloads to AWS, each resulting in optimized price/performance, a more intuitive user experience, and a lower TCO. You can choose to deploy SQL Server on the following: [Amazon EC2](https://docs.aws.amazon.com/sql-server-ec2/latest/userguide/create-sql-server-on-ec2-instance.html), [Amazon RDS for SQL Server](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.CreatingConnecting.SQLServer.html), or [Amazon RDS Custom for SQL Server](https://aws.amazon.com/blogs/database/launch-an-amazon-rds-custom-for-sql-server-instance-using-aws-cloudformation/).
## Assess
To implement a successful migration, it's important to evaluate your existing infrastructure and understand the key features required for your environment. We recommend that you review the following key areas before choosing a migration plan:
+ **Review existing infrastructure** – Review your existing SQL Server infrastructure by using data collected in the discovery phase of your migration. You can use [AWS Migration Evaluator](https://aws.amazon.com/migration-evaluator/) to automatically collect detailed information about server configurations, SQL Server deployments, resource utilization, and application dependencies. For VMware-based environments, the [AWS Transform discovery tool](https://docs.aws.amazon.com/transform/latest/userguide/discovery-tool.html) provides agentless, on-premises discovery without requiring cloud connectivity. Its output feeds directly into an AWS Transform assessment for TCO analysis and business case generation. We recommend that you use the Microsoft prescribed sizing for SQL Server infrastructure on AWS. Understanding current utilization of your on-premises SQL Server instance, including memory, CPU, IOPS, and throughput, is important to right size your SQL Server instance on AWS.
+ **Review existing licensing** – You can take advantage of the complementary [AWS Optimization and Licensing Assessment (AWS OLA)](https://aws.amazon.com/optimization-and-licensing-assessment/) to build a migration and licensing strategy on AWS. AWS OLA provides you with a report that models your deployment options using existing licensing entitlements. These results can help you explore available cost savings across flexible AWS licensing options. If you already run SQL Server workloads on AWS, [AWS Compute Optimizer](https://docs.aws.amazon.com/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/sql-server-compute-optimizer.html) provides automated licensing recommendations, including identifying opportunities to downgrade SQL Server editions based on actual feature usage.
+ **Review existing SQL Server architecture** – If you're using a SQL Server failover cluster with shared storage or SQL Server Always On Availability Group architecture, then understanding your current high availability architecture requirements will help you define the [SQL Server deployment options](https://docs.aws.amazon.com/sql-server-ec2/latest/userguide/sql-server-on-ec2-options.html) on AWS.
SQL Server Always On Availability Groups support both synchronous and asynchronous commit modes, and you can use them for high availability within a single AWS Region (across Availability Zones) or for disaster recovery across Regions. SQL Server Always On Failover Cluster Instances (FCIs) require shared storage, which can be provided by using [Amazon FSx for Windows File Server](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html) or [Amazon FSx for NetApp ONTAP](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/what-is-fsx-ontap.html). For a full comparison of high availability and disaster recovery options, see [Choose a high availability and disaster recovery solution](https://docs.aws.amazon.com/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/sql-server-hadr.html) on AWS Prescriptive Guidance.
+ **Develop backup strategies** – For Amazon RDS for SQL Server, you can use automated backups with point-in-time recovery, manual snapshots, and native backup and restore. For SQL Server on Amazon EC2, you can use native SQL Server backup and restore, use a snapshot approach, or back up databases to Amazon EBS, Amazon FSx for Windows File Server, Amazon FSx for NetApp ONTAP, or Amazon S3. You can use [AWS Backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/whatisbackup.html) to orchestrate and centralize backups across Amazon RDS for SQL Server and SQL Server on Amazon EC2.
SQL Server 2022 on Amazon EC2 with Amazon FSx for NetApp ONTAP supports [T-SQL snapshot backups](https://aws.amazon.com/blogs/modernizing-with-aws/mastering-sql-server-backups-with-t-sql-snapshots-and-amazon-fsx-for-netapp-ontap/) for near-instant, consistent backups with minimal impact on the primary host. SQL Server 2025 extends this further by enabling native database backups from secondary replicas in Always On Availability Groups. For more information, see [What's new in Microsoft SQL Server 2025 on AWS](https://aws.amazon.com/blogs/modernizing-with-aws/whats-new-in-microsoft-sql-server-2025-on-aws/) (AWS blog post).
For more information about backup strategies, see [Backup and restore strategies for Amazon RDS for SQL Server](https://aws.amazon.com/blogs/database/backup-and-restore-strategies-for-amazon-rds-for-sql-server/) (AWS blog post) and [Backup and restore options for SQL Server on Amazon EC2](https://docs.aws.amazon.com/prescriptive-guidance/latest/sql-server-managing-on-aws/welcome.html) (AWS Prescriptive Guidance).
+ **Understand disaster recovery (DR) needs** – For Amazon RDS for SQL Server, cross-Region automated backups and read replicas provide managed DR options without requiring SQL Server-level replication configuration.
For SQL Server on Amazon EC2, you can use a secondary AWS Region connected through [AWS Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html) or [AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html), which allows replication to occur. DR options include SQL Server distributed availability groups for multi-Region deployments, log shipping for a cost-effective option with RTO and RPO within minutes, and [AWS Elastic Disaster Recovery](https://docs.aws.amazon.com/drs/latest/userguide/what-is-drs.html) for continuous block-level replication as an active/passive DR implementation. For more information, see [Choose a high availability and disaster recovery solution](https://docs.aws.amazon.com/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/sql-server-hadr.html) on AWS Prescriptive Guidance and [Architect a disaster recovery for SQL Server on AWS: Part 1](https://aws.amazon.com/blogs/database/part-1-architect-a-disaster-recovery-for-sql-server-on-aws/) on the AWS Database Blog.
## Mobilize
There are [SQL Server database migration strategies](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/strategies.html) that we recommend you consider for your SQL Server workloads:
+ **Rehosting (lift and shift)** – This involves migrating your on-premises SQL Server databases to SQL Server on an Amazon EC2 instance in the AWS Cloud. This approach is useful if a faster migration to AWS is your priority. You can bring your existing SQL Server licenses using the bring your own license (BYOL) model, or you can purchase license-included (LI) instances from AWS. You can also use [AWS Launch Wizard for SQL Server](https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sql.html) to guide you through the sizing, configuration, and deployment of SQL Server on Amazon EC2. It supports both single-instance and high availability deployments.
+ **Replatforming (lift and reshape)** – This involves migrating your on-premises SQL Server databases to a managed database service on AWS. This approach offloads undifferentiated tasks, such as installation, configuration, patching, upgrades, and high availability setup. Choose between two managed options:
+ [Amazon RDS for SQL Server](https://aws.amazon.com/rds/sqlserver/) – This is a fully managed option that is best when you want to offload all database infrastructure management.
+ [Amazon RDS Custom for SQL Server](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/working-with-custom-sqlserver.html) — This is a managed service with retained operating system and database-level access. This option is well suited for legacy or packaged applications with custom deployment requirements. Amazon RDS Custom supports the bring your own media (BYOM) option, which enables you to use your existing SQL Server licenses in compliance with Microsoft's License Mobility terms.
For a feature comparison of SQL Server on Amazon EC2, Amazon RDS, and Amazon RDS Custom, see [Choosing between Amazon EC2 and Amazon RDS](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/comparison.html) on AWS Prescriptive Guidance.
+ **Refactoring (re-architect)** – This typically involves application changes and modernizing by using open source databases or databases built for the cloud. By moving away from SQL Server, you can reduce licensing costs and avoid vendor lock-in and licensing audits. You can modernize your SQL Server databases to:
+ [Amazon RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MySQL.html) or [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html) – Fully managed open-source database offerings.
+ [Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html) – A cloud-native relational database with full MySQL and PostgreSQL compatibility that delivers the performance and availability of commercial-grade databases at a fraction of the cost.
+ [Babelfish for Aurora PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/babelfish.html) – Enables applications originally written for SQL Server to work with Aurora PostgreSQL with minimal code changes, accelerating migration and reducing refactoring risk.
To convert your SQL Server schema and code, you can use [AWS DMS Schema Conversion](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_SchemaConversion.html), which is a fully managed schema conversion feature of AWS Database Migration Service (AWS DMS).
## Migrate
As you migrate your SQL Server workloads to AWS, the following sections describe the available tools and approaches for each migration strategy.
### Rehosting
Rehosting is a [homogeneous migration approach](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/homogeneous-migration.html). Choose this option when you want to migrate your SQL Server database as-is without changing the database software or configuration. This is a common choice for large-scale legacy migrations where speed is the priority.
#### Migrating SQL Server using Amazon EC2
If you migrate to Amazon EC2, you can bring your existing SQL Server licenses by using the BYOL model, or you can purchase LI instances from AWS. [AWS License Manager](https://docs.aws.amazon.com/license-manager/latest/userguide/license-manager.html) helps you control the allocation of your available licenses when deploying SQL Server on Amazon EC2 and helps you comply with licensing rules.
For a BYOL approach, you can rehost SQL Server to shared-tenancy (default) Amazon EC2 instances only if you have [Microsoft Software Assurance (SA)](https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-default). If you don't have SA on your SQL Server licenses, you can rehost to [Amazon EC2 Dedicated Hosts](https://aws.amazon.com/ec2/dedicated-hosts/) if the licenses were purchased prior to October 1, 2019 or if you have added your licenses as a true-up under an active Enterprise Enrollment that is effective prior to that date. For more information, see [Microsoft Licensing on AWS](https://aws.amazon.com/windows/resources/licensing/).
You can migrate a SQL Server database to an Amazon EC2 instance by using SQL Server features or AWS services. These options are appropriate if you're migrating a single database or set of databases to a new SQL Server instance on Amazon EC2. In addition to the database migration, you might also need to migrate objects such as logins, jobs, database mail, and linked servers.
The following approaches are available for rehosting your SQL Server databases on AWS:
+ Server rehosting using [AWS Application Migration Service](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html)
+ [SQL Server backup and restore](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases?view=sql-server-ver16)
+ [SQL Server transactional replication](https://docs.microsoft.com/en-us/sql/relational-databases/replication/transactional/)
+ [Extending your availability group to the cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-sql-server-to-aws-using-distributed-availability-groups.html)
+ [AWS Database Migration Service (AWS DMS)](https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html)
+ [Log shipping](https://aws.amazon.com/blogs/architecture/extend-sql-server-dr-using-log-shipping-for-sql-server-fci-with-amazon-fsx-for-windows-configuration/)
You could also use [AWS Launch Wizard for SQL Server](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/launch-wizard.html) to guide you through the sizing, configuration, and deployment of Microsoft SQL Server on Amazon EC2, which supports both single instance and high availability deployments.
#### Migrating SQL Server using AWS Application Migration Service
[AWS Application Migration Service](https://aws.amazon.com/application-migration-service/) is well suited if you want to lift and shift one or more large-scale machines from an on-premises environment to AWS without changing the SQL Server version, operating system, or code in the databases with near-zero or minimal downtime. You can use AWS Application Migration Service to quickly lift and shift physical, virtual, or cloud servers without compatibility issues, performance impact, or long cutover windows. For guidance on migrating a SQL Server database from an on-premises environment to an Amazon EC2 instance using Application Migration Service, see [Migrating Microsoft SQL Server databases to the AWS Cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/welcome.html) on AWS Prescriptive Guidance. You can also refer to [best practices](https://aws.amazon.com/blogs/mt/best-practices-for-migrating-microsoft-sql-server-databases-to-amazon-ec2-using-cloudendure/) when you use Application Migration Service to migrate Microsoft SQL Server database workloads to AWS.
#### SQL Server on Linux
The SQL Server database engine runs in a similar way on both Windows Server and Linux. However, there are some changes to certain tasks when using Linux. [AWS Launch Wizard](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/launch-wizard.html) can help you adjust to these changes and configure highly available solutions. If you have in-house Linux administration expertise, rehosting to Amazon EC2 Linux is a good choice to save on Windows Server licensing costs. SQL Server on Linux is supported starting with SQL Server 2017. For more information, see [Migrate an on-premises Microsoft SQL Server database to Microsoft SQL Server on Amazon EC2 running Linux](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-an-on-premises-microsoft-sql-server-database-to-microsoft-sql-server-on-amazon-ec2-running-linux.html) on AWS Prescriptive Guidance.
### Replatforming
Replatforming is a [homogeneous](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/homogeneous-migration.html) approach that's best suited for reducing the time you spend managing database instances by using a fully-managed database offering. A fully-managed database in Amazon RDS for SQL Server limits you from accessing the underlying operating system, system volume, or installation of custom drivers. For more information, see [Amazon RDS for Microsoft SQL Server](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SQLServer.html). If OS-level access or existing SQL Server licenses are required,** **consider replatforming to [Amazon RDS Custom](https://aws.amazon.com/rds/custom/) for SQL Server.
Amazon RDS Custom for SQL Server supports the BYOM licensing model, which enables you to use your own installation media and licenses. Your licenses must comply with the Microsoft [License Mobility](https://aws.amazon.com/windows/resources/licensemobility/) terms. You can either replatform SQL Server to Amazon RDS for SQL Server or to Amazon RDS Custom for SQL Server. The choice depends on the customization level you need on the underlying operating system, whether the features you need are supported in Amazon RDS for SQL Server, or whether you want to use your existing SQL Server licenses by using BYOM.
The following options are available for migrating SQL Server to Amazon RDS for SQL Server or Amazon RDS Custom for SQL Server:
+ **Custom log shipping** – Requires custom scripts for Amazon RDS for SQL Server and Amazon RDS Custom. For a reference implementation, see [Automate on-premises or Amazon EC2 SQL Server to Amazon RDS for SQL Server migration using custom log shipping](https://aws.amazon.com/blogs/database/automate-on-premises-or-amazon-ec2-sql-server-to-amazon-rds-for-sql-server-migration-using-custom-log-shipping/) on the AWS Database Blog.
+ **SQL Server backup and restore** – For backup and restore for Amazon RDS for SQL Server, see [Migrating SQL Server to Amazon RDS using native backup and restore](https://aws.amazon.com/blogs/database/migrating-sql-server-to-amazon-rds-using-native-backup-and-restore/). For Amazon RDS Custom, see [Migrate on-premises SQL Server to Amazon RDS Custom for SQL Server using native backup and restore and Amazon S3](https://aws.amazon.com/blogs/database/migrate-on-premises-sql-server-to-amazon-rds-custom-for-sql-server-using-native-backup-and-restore-and-amazon-s3/).
+ [Transactional replication](https://aws.amazon.com/blogs/database/part-3-migrating-to-amazon-rds-for-sql-server-using-transactional-replication-with-native-backup-and-restore/)
+ [AWS Database Migration Service (AWS DMS)](https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html)
For more information, see the [SQL Server migration methods](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/methods.html) in AWS Prescriptive Guide.
To replatform your SQL Server databases to run on Amazon RDS for SQL Server, consider using the approaches provided in [Amazon RDS for SQL Server resources](https://aws.amazon.com/rds/sqlserver/resources/). For information about how to migrate end-of-support workloads, see [Migrate end of support Microsoft SQL Server databases to Amazon RDS for SQL Server confidently](https://aws.amazon.com/blogs/database/migrate-end-of-support-microsoft-sql-server-databases-to-amazon-rds-for-sql-server-confidently/) on the AWS Database Blog. For information about migrating on-premises databases to Amazon RDS Custom for SQL Server, see [Migrating an on-premises database to Amazon RDS Custom for SQL Server](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-migrating.html) in the Amazon RDS documentation.
### Refactoring
Refactoring is [heterogeneous](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/heterogeneous-migration.html). Choose this approach if you're ready to restructure, rewrite, and rearchitect your database and application to take advantage of open source and built-for-the-cloud database offerings. If you're open to refactoring your database and respective applications, you can modernize your SQL Server workloads to either Amazon RDS for MySQL, Amazon RDS for PostgreSQL, [Amazon Aurora MySQL-Compatible Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.html), or [Amazon Aurora PostgreSQL-Compatible Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html). You can refactor depending on many modernization timelines and performance requirements.
Amazon RDS for MySQL and Amazon RDS for PostgreSQL are fully-managed database offerings for their respective open-source databases. Amazon Aurora is a relational database management system (RDBMS) that is built for the cloud with full MySQL and PostgreSQL compatibility. Aurora features a fault-tolerant storage system and gives you the performance and availability of commercial-grade databases at one-tenth the cost.
You can also use [Amazon Aurora Serverless](https://aws.amazon.com/rds/aurora/serverless/) to run your database on AWS without managing database capacity. Amazon Aurora Serverless v2 scales instantly to hundreds of thousands of transactions in a fraction of a second. You pay only for the capacity your application consumes, and you can save up to 90% on database costs compared to the cost of provisioning capacity for peak load.
To refactor your SQL Server databases to one of these offerings, consider using one of the following:
+ [AWS Transform for SQL Server Modernization](https://docs.aws.amazon.com/transform/latest/userguide/sql-server-modernization.html) automates the full-stack modernization of SQL Server databases and their associated .NET applications to Amazon Aurora PostgreSQL. It orchestrates the entire migration journey, including schema conversion, stored procedure transformation (T-SQL to PL/pgSQL), data migration through AWS DMS, and application code updates (Entity Framework, ADO.NET, connection strings). It also provides human-in-the-loop checkpoints at critical stages. For more information about the supported SQL Server versions, sources, and targets, see [Supported versions and project types](https://docs.aws.amazon.com/transform/latest/userguide/sql-server-modernization.html#supported-versions-project-types) in the AWS Transform documentation.
+ For schema-only conversions or migrations to Amazon RDS for MySQL, Amazon RDS for PostgreSQL, or other Aurora targets, consider using [AWS DMS Schema Conversion](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_SchemaConversion.html).
+ If your goal is to accelerate your application and database migrations to AWS, consider using [Babelfish for Aurora PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/babelfish.html). Babelfish enables applications that were originally written for SQL Server to work with Amazon Aurora with minimal code changes. As a result, the effort required to modify and move to Babelfish for Aurora PostgreSQL applications developed for SQL Server 2019 or older is reduced, leading to faster, lower-risk, and more cost-effective refactoring.
Consider the following resources for migrating with Babelfish:
+ [Migrate from SQL Server to Amazon Aurora using Babelfish](https://aws.amazon.com/blogs/database/migrate-from-sql-server-to-amazon-aurora-using-babelfish/) (AWS Database Blog)
+ [Prepare for Babelfish migration with the AWS SCT assessment report](https://aws.amazon.com/blogs/database/prepare-for-babelfish-migration-with-the-aws-sct-assessment-report/) (AWS Database Blog)
+ [Migrate from SQL Server to Aurora PostgreSQL using SSIS and Babelfish](https://aws.amazon.com/blogs/database/migrate-from-sql-server-to-aurora-postgresql-using-ssis-and-babelfish/) (AWS Database Blog)
+ [Using Babelfish as a target for AWS Database Migration Service](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.Babelfish.html) (AWS Database Migration Service documentation)
For more information, see [Tools for heterogeneous database migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/heterogeneous-migration-tools.html) on AWS Prescriptive Guidance.
## Additional resources
+ [Migrating Microsoft SQL Server databases to the AWS Cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/welcome.html) (AWS Prescriptive Guidance)
+ [Migration and modernization strategies for your SQL Server workloads on AWS](https://aws.amazon.com/blogs/modernizing-with-aws/migration-modernization-strategies-sql-on-aws/) (AWS Blogs)
+ [SQL Server database migration methods](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/methods.html) (AWS Prescriptive Guidance)