User accounts migration
Move your Bubble user accounts into Supabase Auth
A complete user migration, not just a data export - Supabase Auth Accounts provisioned and linked to your user's data.
Available as an add-on to your database migration project.
Why teams add this
Your database moved. Your users didn't.
Bubble's User table is just a regular data table - exporting it gives you rows, not auth accounts. This migration creates real Supabase Auth identities and connects them to each user row so sign-in works on your new stack.
Without unbubble.dev
- Migrating Bubble's User table gives you data rows, not auth accounts
- No auth.users entries exist, so your users will have to sign up again
- No connection between auth and your users table, so you'll have to manually connect each user to their data after they sign up
With unbubble.dev
- A real auth.users entry is created for every Bubble user, linked via supabase_user_id
- Accounts already exist in Supabase, so users only need to reset their password
- Each users row gets a supabase_user_id column that links it to its auth account, so your data is immediately connected
How it works
Three automated steps to move your users
Sync your users table
Your Bubble User table is synced into your Supabase database with all its fields.
Create auth accounts
A Supabase Auth account is created for every user, each with a secure random password for setup. Users can reset their password for first login on the new stack.
Link auth to user data
Each users row gets a supabase_user_id column that points to its auth account - so when a user signs in on your new system, their Bubble data is already associated.
Ready to move your users to Supabase Auth?
Add this to your database migration project and ship sign-in with real accounts and data that already points at the right users.
FAQ
Frequently asked questions
Quick answers to what people usually ask before getting started.
How are Bubble users migrated to Supabase Auth?
Each Bubble user is recreated in Supabase Auth as a real account, keyed by email. A supabase_user_id column is added to your users table linking each row to its auth account, so your app can connect sign-in to existing user data.
Will my users keep their passwords after the migration?
Bubble does not give you access to user passwords, so existing passwords cannot be migrated. We generate a secure random password for each user only to create the Supabase Auth row. On the new stack, users reset their password for their first login; the account is already linked to their migrated data.
How does my app connect sign-in to user data?
Each row in your migrated users table gets a supabase_user_id column that points to its Supabase Auth account. Your other tables still reference users through the original Bubble ID - no foreign keys are changed. The link between auth and data lives in that one column.
Do I need the database migration to use this?
Yes. User accounts migration is an add-on for the same project as your database migration. It depends on the migrated users table being present so that auth accounts can be linked back to it. The database migration must be unlocked for that project first.
What user data is included?
Email, the original Bubble user ID, creation date, and any user fields stored on your Bubble user data type (the same fields the database migration would move). Existing login passwords are not retrievable from Bubble.