Migrate from Supabase to Clicbase without resetting passwords
Import your schema, data, accounts, storage and realtime from Supabase. Your users keep their passwords, a step-by-step guide, with the technical details.
Switching platforms is scary, mostly because of user accounts. Good news: migrating to Clicbase preserves existing passwords. Here's how, and why it works.
What gets imported
- The full schema (tables, views, functions, constraints, RLS).
- The data.
- User accounts, with their password hashes.
- The storage content.
- The realtime configuration.
Why passwords aren't reset
A password is never stored in plain text: only its hash is. The migration copies that hash as-is. On the first login, Clicbase verifies it, and if the original algorithm differs, it re-hashes the value transparently. The user sees nothing and changes nothing.
The technical detail, If an account is recreated through a SQL operation, the hash is computed with bcrypt; on the next login, Clicbase can re-hash it to its current algorithm. You have nothing to manage: it's transparent.
The steps
- Grab the Postgres connection URL of your Supabase project.
- Start the import from Clicbase: schema and data first.
- Import the accounts (the auth table) and the storage.
- Verify a few test logins, then switch your domain over.
Before you switch, Test the login of an existing account before pointing your domain at Clicbase. That's your guarantee the hashes were properly carried over.
What's next?
Once the database is in place, you get the extras: mailboxes at your domain, Google login on your subdomain, automatic daily backups, and the option to isolate the project in a dedicated container.
Ready to try? Start the migration or create an account.
What gets migrated: in short
| Item | Migrated? |
|---|---|
| Schema & tables | Yes, automatically |
| Data | Yes |
| Accounts + passwords | Yes, no reset |
| Storage & realtime | Yes |
Frequently asked questions
How do I migrate from Supabase to Clicbase?
Migration is automatic: schema, data, user accounts, storage and realtime are all carried over. You point your front end at the new API and key.
Do my users have to reset their passwords?
No. Existing passwords are preserved (transparently re-hashed on first login) — no forced reset, your users won't notice the switch.
Launch your backend in minutes
Postgres database, API, auth, storage, realtime, plus your emails and domain. Free to start.