Migrate from Postgres to Supabase
Migrate your existing Postgres database to Supabase.
This is a guide for migrating your Postgres database to Supabase. Supabase is a robust and open-source platform. Supabase provide all the backend features developers need to build a product: a Postgres database, authentication, instant APIs, edge functions, realtime subscriptions, and storage. Postgres is the core of Supabase—for example, you can use row-level security and there are more than 40 Postgres extensions available.
This guide demonstrates how to migrate your Postgres database to Supabase to get the most out of Postgres while gaining access to all the features you need to build a project.
Retrieve your Postgres database credentials
- Log in to your provider to get the connection details for your Postgres database.
- Click on PSQL Command and edit it adding the content after
PSQL_COMMAND=
.
Example:
_10%env PSQL_COMMAND=PGPASSWORD=RgaMDfTS_password_FTPa7 psql -h dpg-a_server_in.oregon-postgres.provider.com -U my_db_pxl0_user my_db_pxl0
Retrieve your Supabase connection string
-
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.
-
Go to the Database settings for your project in the Supabase Dashboard.
-
Under Connection string, make sure
Use connection pooling
is enabled. Copy the URI and replace the password placeholder with your database password.
Migrate the database
The fastest way to migrate your database is with the Supabase migration tool on Google Colab. Alternatively, you can use the pg_dump and psql command line tools, which are included in a full PostgreSQL installation.
- Set the environment variables (
PSQL_COMMAND
,SUPABASE_HOST
,SUPABASE_PASSWORD
) in the Colab notebook. - Run the first two steps in the notebook in order. The first sets the variables and the second installs PSQL and the migration script.
- Run the third step to start the migration. This will take a few minutes.
-
If you're planning to migrate a database larger than 6 GB, we recommend upgrading to at least a Large compute add-on. This will ensure you have the necessary resources to handle the migration efficiently.
-
For databases smaller than 150 GB, you can increase the size of the disk on paid projects by navigating to Database Settings.
-
If you're dealing with a database larger than 150 GB, we strongly advise you to contact our support team for assistance in provisioning the required resources and ensuring a smooth migration process.
Enterprise
Contact us if you need more help migrating your project.