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.

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

Password hashes aren't portable 1:1 — the first login securely resets the password, invisibly to users.

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 doesn't export password hashes directly. Plan a reset or lazy-migration flow — it's standard and stays invisible to users until first login.

FAQ

Firebase migration — frequently asked questions

No. You export your users from Firebase and import them into Tuurio ID; the first login lazily resets each password in a secure, invisible way.
Firebase doesn't export password hashes directly, so plan a lazy-migration or reset flow. This is standard practice and doesn't disrupt your users.
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

Ready to migrate from Firebase Auth?

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