Migration guide

Migrate from Firebase Authentication to Tuurio ID

This guide takes you from Firebase Authentication to Tuurio ID in under a day — without losing your users. You stay on standard OpenID Connect and only swap the provider.

Start migration Why switch

Under a day

A standard OIDC migration for most apps.

Keep your users

User export plus lazy password migration.

Safe rollback

Run Firebase in parallel until the cutover is confirmed.
Before you start

Prerequisites

  • A Tuurio ID tenant.
  • Admin access to your Firebase project.
  • Your app codebase.
Step by step

From Firebase Auth to Tuurio ID in six steps

1

Export users from Firebase

Export your accounts using the Firebase Admin SDK or CLI.

2

Create an OIDC client in Tuurio ID

Create the client and add your redirect URIs.

3

Import users with lazy migration

Import Firebase SCRYPT hashes with their project hash parameters; the first successful login verifies and promotes the password invisibly.

4

Point your app's auth to Tuurio OIDC

Switch your auth calls to the standard OIDC flow with PKCE.

5

Verify, then cut over

Verify with a test tenant, then switch production traffic over.

6

Keep a rollback path

Run Firebase in parallel until the migration is confirmed.

Firebase password users can keep their password when the export includes passwordHash/passwordSalt and the project hash parameters are available. Accounts without an exportable password hash need SSO linking or a reset flow.

FAQ

Firebase migration — frequently asked questions

No. You export your users from Firebase and import them into Tuurio ID. For password users with Firebase SCRYPT hashes, the first login verifies the old password and stores it in Tuurio ID's current password format.
Yes, for Firebase SCRYPT password users when passwordHash, passwordSalt, signer key, salt separator, rounds, and memory cost are available. Users without an exportable password hash need SSO linking or a reset.
For most apps a few hours to a few days. You can run Firebase in parallel until you confirm the cutover.
No major rework. Tuurio ID uses standard OpenID Connect with PKCE, so you keep your existing flow and just point it at the new provider.

Keep exploring

Firebase Auth alternative

Why teams move to an EU-hosted identity provider.

Security & EU hosting

Encryption, OAuth + PKCE, Schrems II and EU data residency.

Ready to migrate from Firebase Auth?

Create your tenant and run a standard OIDC migration today — EU-hosted and GDPR-compliant.

Start migration Why switch