Docs · Migrate

Import from Supabase

Import copies an existing Supabase project onto your Da8a server. The copy runs server to server, and your Supabase project isn’t changed.

What gets copied

• Your tables with their data, plus database functions, triggers, Row Level Security policies and extensions, from the schemas you choose.
• Your users and their logins (optional), so people sign in with the same credentials.
• Your storage files (optional). Very large files (over 50 MB each) are listed in the import report instead of copied; move those yourself with supabase-js.

Before you start

From your Supabase project, you’ll need:

• The project URL, like https://abcd1234.supabase.co.
• The database connection string from Connect → Session pooler (port 5432), with your database password filled in. Use the session pooler: the direct db.<ref>.supabase.co address is IPv6-only.
• To copy storage files: the service_role key, used to read files.

Run the import

1. In your Da8a project, open Import and choose Import from Supabase.
2. Enter the project URL and connection string, and list the schemas to copy (comma-separated).
3. Choose the options: Users and their logins, Storage files, and whether to replace tables that already exist in your Da8a project.
4. Type the server name to confirm, and start. Progress is shown for the database and storage parts separately.
5. Review the result in the Table editor and SQL editor.

After the import

1. Update your app: replace the Supabase project URL and anon key with your Da8a project URL and anon key. supabase-js works unchanged.
2. Edge functions: recreate them in Functions and set their secrets again. Secret names starting with SUPABASE_ are reserved, so rename any that do. See Edge functions.
3. Auth providers: enable the same providers under Auth, enter the new callback URL in each provider’s console, and add your site URLs to the redirect allow-list.
4. Frontend on Chapong? Link the site to your Da8a project and its URL, anon key and redirect URLs are set for you.