Supabase Migration and Export Tools
Move data into Supabase, and get it back out again
Getting data into Supabase means Postgres, a CSV file, or a third-party command-line tool. Getting it out means Postgres or nothing - there is no route from Supabase to MySQL, SQL Server or Oracle. DBConvert covers both directions.
Download the Converter for Your Other Database
Pick the engine on the other side of Supabase. Each converter runs both directions - the same download loads data into Supabase and pulls it back out, so there is nothing separate to fetch for the return trip.
MySQL to Supabase
MySQL or MariaDB into Supabase, and Supabase back out to MySQL.
SQL Server to Supabase
SQL Server into Supabase with type mapping handled, and Supabase back out to SQL Server.
Oracle to Supabase
Oracle into Supabase including schema and keys, and Supabase back out to Oracle.
Access to Supabase
Microsoft Access into Supabase, and Supabase back out to Access.
PostgreSQL ↔ Supabase (same engine)
Move an existing PostgreSQL database into Supabase - or export Supabase back to self-managed PostgreSQL. Both are Postgres-to-Postgres, handled by DBConvert Studio.
Complete PostgreSQL Migration Solutions
Review PostgreSQL-compatible migration tools, configuration guides, and common data movement paths.
What Supabase Can Move, and What It Cannot
Supabase is Postgres, so it moves Postgres. Everything else is a command-line tool or nothing at all.
| Route |  What Supabase gives you |
 DBConvert |
|---|---|---|
| PostgreSQL → Supabase | pg_dump and psql, on the command line. |
Same job with a table picker and no terminal. |
| CSV → Supabase | Dashboard import, capped at 100 MB. | No cap. |
| MySQL or SQL Server → Supabase | Nothing native - the docs send you to pgloader, a command-line tool that only loads inwards. | Yes, and the same converter goes back out. |
| Oracle, Access or FoxPro → Supabase | Nothing. | Yes. |
| Supabase → PostgreSQL you run yourself | supabase db dump, on the command line. |
Same job, plus a schedule. |
| Supabase → MySQL, SQL Server or Oracle | Nothing. | Yes - this is the row nothing else on the list covers. |
Supabase is an open-source backend on top of a standard Postgres database - auth, realtime, storage and generated APIs over ordinary PostgreSQL. That is why a Postgres converter reaches it at all: it takes a normal PostgreSQL connection string. Which of Supabase's three endpoints answers from a desktop machine, and the two errors you get if you pick the wrong one, are in Connect Supabase.
Looking for supabase migration new?
Then you want a different thing with the same name. In Supabase, a migration is a versioned SQL file that changes your schema - supabase migration new, up, repair, squash - and that lives in the Supabase CLI docs. This page is about moving the data itself between Supabase and another database engine.
Getting Your Data Out of Supabase
There is no button in the dashboard that hands you your database. There is a command line, and there is a restore you cannot download.
What Supabase backups actually give you
Daily backups cover Pro, Team and Enterprise projects, with 7, 14 and 30 days of retention. They restore into the project through the dashboard. Point-in-time recovery is a paid add-on, and its backups cannot be downloaded once you turn it off.
On the Free plan there are none. The dashboard says so itself, on the Backups page: "Free Plan does not include project backups." Until you upgrade, the only copy of your data is the one you take yourself.
A copy you hold, in a database you run
DBConvert writes the tables straight into PostgreSQL, MySQL, SQL Server or Oracle that you control - not into an archive you have to restore somewhere else first. Point it at your own server, run it, and the data is out. It can also save to a local dump file if what you want is simply a copy on disk.
Put it on a schedule and the same job repeats, so the copy stays current instead of ageing from the day you took it. Each run brings the destination up to date, which is also what makes a phased cutover work - and what lets a run cut short by a dropped VPN simply be started again.
Coming from Lovable
Lovable Cloud is built on Supabase, but it does not hand external tools a Postgres connection - so DBConvert cannot reach it directly. Follow Lovable's own path first and move the project onto a Supabase project of your own. From that point it is ordinary Postgres, and everything on this page applies, including the export to MySQL, SQL Server or Oracle that neither Lovable nor Supabase offers.
Need log-based, real-time replication?
The tools on this page copy and sync on demand or on a schedule. If you need every committed change as it happens, that is DBConvert Streams - a separate product that reads the Postgres write-ahead log directly, with Supabase on both its source and target list.
Ready to Move Data In or Out of Supabase?
Supabase speaks the standard PostgreSQL protocol, so the PostgreSQL converters reach it. Free trial, Windows.