Migrate from Amazon RDS to Supabase

This guide aims to exhibit the process of transferring your Amazon RDS database from any of these engines Postgres, MySQL or MS SQL to Supabase's Postgres database. Although Amazon RDS is a favored managed database service provided by AWS, it may not suffice for all use cases. Supabase, on the other hand, provides an excellent free and open source option that encompasses all the necessary backend features to develop a product: a Postgres database, authentication, instant APIs, edge functions, real-time subscriptions, and storage.

Supabase's core is Postgres, enabling the use of row-level security and providing access to over 40 Postgres extensions. By migrating from Amazon RDS to Supabase, you can leverage Postgres to its fullest potential and acquire all the features you need to complete your project.

Retrieve your Amazon RDS database credentials [#retrieve-rds-credentials]

Log in to your Amazon RDS account.
Select the region where your RDS database is located.
Navigate to the Databases tab.
Select the database that you want to migrate.
In the Connectivity & Security tab, note down the Endpoint and the port number.
In the Configuration tab, note down the Database name and the Username.
If you do not have the password, create a new one and note it down.

Retrieve your Supabase host [#retrieve-supabase-host]

If you're new to Supabase, create a project. Make a note of your password, you will need this later. If you forget it, you can reset it here.
On your project dashboard, click Connect
Under the Session pooler, click on the View parameters under the connect string. Note your Host ($SUPABASE_HOST).

Migrate the database

The fastest way to migrate your database is with the Supabase migration tool on Google Colab.

Alternatively, you can use pgloader, a flexible and powerful data migration tool that supports a wide range of source database engines, including MySQL and MS SQL, and migrates the data to a Postgres database. For databases using the Postgres engine, we recommend using the pg_dump and psql command line tools, which are included in a full Postgres installation.

<Tabs scrollable size="small" type="underlined" defaultActiveId="colab" queryGroup="migrate-method"

Select the Database Engine from the Source database in the dropdown
Set the environment variables (HOST, USER, SOURCE_DB,PASSWORD, SUPABASE_URL, and SUPABASE_PASSWORD) in the Colab notebook.
Run the first two steps in the notebook in order. The first sets engine and installs the necessary files.
Run the third step to start the migration. This will take a few minutes.

</TabPanel> <TabPanel id="MySQL" label="Migrate from MySQL with pgloader">

Install pgloader.

Create a configuration file (e.g., config.load).

For your destination, use your Supabase connection string with Use connection pooling enabled, and the mode set to Session. You can get the string from your Database Settings.

sql

load database
  from mysql://user:password@host/source_db
  into postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres
alter schema 'public' owner to 'postgres';
set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB';

Run the migration with pgloader
bash
```
pgloader config.load
```

</TabPanel> <TabPanel id="MS SQL" label="Migrate from MSSQL">

Install pgloader.

Create a configuration file (e.g., config.load).

sql

LOAD DATABASE
    FROM mssql://USER:PASSWORD@HOST/SOURCE_DB
    INTO postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:6543/postgres
ALTER SCHEMA 'public' OWNER TO 'postgres';
set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB';

Run the migration with pgloader
bash
```
pgloader config.load
```

</TabPanel> </Tabs>

<$Partial path="migration_warnings.mdx" />

Retrieve your Amazon RDS database credentials [#retrieve-rds-credentials]

Retrieve your Supabase host [#retrieve-supabase-host]

Migrate the database

Enterprise