Migrate from Render to Supabase
Render is a popular Web Hosting service in the online services category that also has a managed Postgres service. Render has a great developer experience, allowing users to deploy straight from GitHub or GitLab. This is the core of their product and they do it really well. However, when it comes to Postgres databases, it may not be the best option.
Supabase is one of the best free alternative to Render Postgres. 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 from Render to Supabase to get the most out of Postgres while gaining access to all the features you need to build a project.
Retrieve your Render database credentials #
- Log in to your Render account and select the project you want to migrate.
- Click Dashboard in the menu and click in your Postgres database.
- Scroll down in the Info tab.
- Click on PSQL Command and edit it adding the content after
_10%env PSQL_COMMAND=PGPASSWORD=RgaMDfTS_password_FTPa7 psql -h dpg-a_server_in.oregon-postgres.render.com -U my_db_pxl0_user my_db_pxl0
Retrieve your Supabase Host #
- If you're new to Supabase, create a project.
- Go to the Database settings for your project in the Supabase Dashboard.
- Under Connection Info, note your Host (
- Save your password or reset it if you forgot it.
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 (
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 plan on migrating a database larger than 6 GB, we recommend contacting support to ensure that you'll have the proper disk size pre-provisioned. You can read more about how the disk is managed on Supabase on the Database usage.
- We also recommend upgrading to at least a Large instance for the migration (you can downgrade later) to avoid running out of IO-Budget.