Move your supabase.com project to NapNodes without touching the original

What moves and what doesn't

Your tables and their data move across, along with your database functions, your security policies (RLS), including those on buckets, any triggers you added on auth and storage, and your users with their passwords.

The files inside Storage don't move: the list of buckets and files arrives, but the contents are uploaded separately. Neither do your Edge Functions, which you copy in “Files”, custom roles with passwords, or function secrets.

Your project's keys will be different, so your users will have to sign in again.

1. Create your project on NapNodes

1. Pick a size similar to the one there

   In “Buy”, Supabase. Here the RAM is the whole machine's: if you have a 1 GB Micro there, the 3 GB Small gives your database a similar amount of memory. If you grow, you move to a bigger plan without losing anything.

2. Wait for it to be running

   Your project appears in “My servers”. When it says “Running”, carry on.

2. Bring your project over

1. Copy your connection string

   On supabase.com, in your project, “Connect” and then “Session pooler”. That's the one that works without IPv6. Replace [YOUR-PASSWORD] with your database password.

2. Paste it in the panel

   In your project, “Backups” → “Bring my project from supabase.com” → “Bring it over”. It carries on even if you close the tab. We save a copy first, and it only works on an empty project: if you've already tried things out, use “Start from scratch” in “Settings”.

3. Check that everything is there

   Open the Studio and look at your tables and users. Your supabase.com project stays as it was.

3. Move your files and functions

1. Storage files

   Download them there and upload them here with a short supabase-js script: go through each bucket with list, fetch each file with download and send it with upload, using the secret key on each side.

2. Edge Functions

   In “Files”, “New function”, and paste the code. Their secrets go in “Settings” → “Function secrets”.

3. What you had configured

   “Settings” has your SMTP email, sign-in with Google or GitHub and the return addresses. In each provider, change the return address to your project's followed by /auth/v1/callback.

4. Change your app

Your URL and keys are in “Connection”. Change both in your app and you're done: supabase-js works the same. If you never want to touch them again, set your own domain in “Connection” before switching.

If your app kept writing in the meantime, that data isn't here. So that nothing is lost, stop writes for a moment, use “Start from scratch”, bring the project over again and change your app.

Frequently asked questions