Amazon RDS & Aurora Migration Tools

Move schema and data between AWS-managed relational databases and on-premises or cloud systems. Choose the tool by database engine, not by cloud provider alone.

Choose the AWS service and database engine

RDS and Aurora use different engine sets even though both are managed through Amazon RDS.

Choose the AWS target family

The same installer works with RDS and the compatible Aurora edition.

Several database pairs? View Studio

RDS / Aurora MySQL ↔ RDS / Aurora PostgreSQL

One MySQL–PostgreSQL pair tool covers either direction and same-family endpoints.

DBConvert

One-time schema-and-data migration, test loads, or export from AWS.

DBSync

Scheduled row comparison; trigger-based modes depend on engine features and RDS privileges.

$179 one-time license per DBConvert or DBSync pair tool. Products are licensed separately; the Windows trial is time-unlimited with record and feature limits.

Prepare the AWS connection

DBConvert connects as a normal database client; it does not configure the VPC or RDS instance for you.

Use the correct AWS endpoint

Amazon RDSAmazon Aurora
EndpointDB instance endpointCluster/writer endpoint
Write targetSelected DB instanceCurrent primary instance
EnginesMySQL, MariaDB, PostgreSQL, SQL Server, Oracle, Db2MySQL- or PostgreSQL-compatible
AvoidStale or incorrect instance hostnameReader endpoint for migration writes
Aurora writer endpoint documentation

Connection checklist

  1. 1.Copy the endpoint, port, database name, username, and password.
  2. 2.Allow the Windows client through the VPC security group, VPN, bastion, or approved network path.
  3. 3.Configure SSL/TLS with the current AWS RDS CA certificate when required.
  4. 4.Grant the required read, write, and object-creation privileges, then test representative tables.

Managed-service boundaries

  • Review data types, defaults, indexes, keys, collations, extensions, and engine-version differences.
  • Plan stored procedures, functions, triggers, jobs, server logins, and infrastructure as separate work.
  • Managed accounts can restrict administrative operations available on self-managed servers.