I'm planning to move my database that's currently hosted on Supabase over to Railway, where my backend runs. It's just the database that's on Supabase, nothing else, and I'm a bit worried about losing data during the process. Has anyone here made a similar migration? I haven't done it before, so any tips would be appreciated!
3 Answers
I've done this migration a few times and it's actually pretty straightforward! The key is to use pg_dump to export your Supabase database, and then pg_restore on Railway. Just double-check your connection strings, and if you're feeling nervous, test everything out with a dry run on a copy first. Watch out for any Supabase-specific extensions or authentication methods—if it's just basic Postgres tables, you should be good. Railway's setup is solid, so you can create a new database there and import the dump directly. For extra safety, keep Supabase in read-only mode for a day or two after the switch. By the way, what's the size of your database?
Do you need to do this live while your users are using your app? If it’s not a big deal, you can just use pg_dump for the export.
I do have to do it live, but I can take it down for about an hour if needed. I'll look into pg_dump more.
Supabase is basically managed Postgres, so this process should be pretty smooth, right? Just create a new Postgres instance on Railway, export your database with pg_dump, and then import it using psql or pg_restore. I recommend doing a test migration first on a temporary Railway database, and make sure to put your app in maintenance mode during the final migration to avoid any new writes happening.
Absolutely, I'm going to do that! Thanks for the tip, and I'll just switch the site to maintenance mode for an hour, which should work fine.
Thanks for the advice! I'm a bit paranoid about it, but since I've built my backend to rely on Supabase just for Postgres, I think it will be simple. Plus, my database size is pretty small!