Migration From Auth0
This document will help you migrate off of Auth0. If you are looking to compare FusionAuth and Auth0, this document may help.
This guide assumes you have installed FusionAuth. If you have not, please view our installation guides and install FusionAuth before you begin. For more general migration information, please view the FusionAuth migration guide.
There are a number of different ways applications can be integrated with Auth0, and it would be difficult to cover them all. This guide mentions the typical parts of a bulk migration and focuses on migrating user data from an Auth0 managed user database into FusionAuth.
Obtaining User Data
You can use either the Auth0 management API or the Auth0 user interface to export user data. This guide uses the user interface, but if you have a large number of users, the management API is recommended. Auth0 also has a high level export guide worth reviewing.
If you are using the user interface, usernames, email addresses and other data can be obtained by installing an extension and downloading the data. The password hashes can be obtained by opening a support ticket.
Here’s a brief video walking through the export process, which is further documented below.
Mapping User Attributes
The attributes of the User object in FusionAuth are well documented.
If there is an attribute in your Auth0 user which cannot be directly mapped to a FusionAuth attribute, you can place it in the
user.data field. This field can store arbitrary JSON values and will be indexed and searchable.
Auth0 also provides integrations with other social login providers such as Twitter, Google or Facebook. Review the supported FusionAuth Identity Providers to ensure your social providers are supported.
If not supported explicitly, a provider may work with an OIDC or SAML connection. Otherwise, please open a feature request.
When migrating social logins, you may need to modify the switches of the Auth0 import script. See Use the Script for more.
Migrating users with social logins such as Apple or Facebook requires that you have an existing user Id for that provider. What this unique user Id looks like depends on the particular social identity provider. The unique Id may be an email address, an integer, UUID, or a random string.
Configure the appropriate FusionAuth Identity Provider with the same values (
client_id, etc) as the original user management system you are migrating away from.
Import users with the Import API, assigning each user with a social login a random password such as a UUID.
Your next step depends on whether the social login provider’s unique identifier is available as part of your migration data. If you have the social login provider’s unique identifier, for each user, use the Link API to create a link with the appropriate User Id, Identity Provider Id and Identity Provider User Id.
The User Id is the Id of the recently created FusionAuth User.
The Identity Provider Id is found on the corresponding Identity Provider API documentation. Look for identityProvider.id.
The Identity Provider User Id is the existing social provider user identifier exported or otherwise extracted from the original system.
You do not need to migrate the social network token, which may or may not be accessible. During the first login of a newly migrated user, FusionAuth finds the unique user in the social login provider based on the migrated Identity Provider User Id, and completes the login. During this process, FusionAuth stores a token on the Link, if the social provider returns one. Depending on the configuration of the social provider, users may see a prompt asking if they want to allow FusionAuth to have access to user data such as email address.
IdP Linking Strategies are available since version 1.28.0. Before that version, users were linked on email.
If you do not have the social login provider’s identifier, you need to decide if you want to transparently link the two accounts, which is easier for the end user, or if you want to ask the user to manually link the accounts, which is more accurate, but may be confusing.
To transparently link the accounts, choose a linking strategy of
Link On Email or
Link On Username, which will create the user if they don’t exist. However, if the user has an email address at their social provider which differs from the email address that was used to sign up for your application and which you imported to FusionAuth, then two accounts will be created.
For example, if the user has a Google account
email@example.com, but signed up for your application with
firstname.lastname@example.org, then if you use the
Link On Email strategy, two different accounts will be created, since FusionAuth is trying to match on email address and they don’t. The same holds true for usernames with the
Link on Username strategy.
To prompt the user to link the accounts, choose a linking strategy of
Pending, which will prompt the end user to sign into FusionAuth after they sign into the social provider, authoritatively linking the two accounts.
Here’s more information about IdP Linking Strategies.
There are often other important entities, such as connections or roles, that need to be migrated. There are usually fewer of these, so an automated migration may not make sense, but plan to move this configuration somehow.
Be aware that functionality may not be the same between Auth0 and FusionAuth. This is different from user data; as long as you can somehow migrate a login identifier (a username or email) and a password hash, a user will be authenticated and successfully migrated. You can download FusionAuth before you begin a migration and build a proof of concept to learn more about the differences.
A partial list of what may need to be migrated for your application to work properly includes the following:
Tenants are a high level construct which groups other entities such as users and applications together. FusionAuth calls these Tenants as well. FusionAuth supports multi-tenant configuration by default.
For Auth0, Roles and Permissions provide information about what your users can do in your custom or off the shelf applications. FusionAuth has Roles and they are defined on an Application by Application basis.
Refresh tokens allow JWTs to be refreshed without a user logging in. These can be migrated using the Import Refresh Tokens API.
In FusionAuth, users are explicitly mapped to applications with a Registration.
Auth0, in contrast, gives users access to all Auth0 applications in a tenant by default.
When creating an object with the FusionAuth API, you can specify the Id. It must be a UUID.
This works for users, applications, and tenants, among others.
If you have external dependencies on an Id stored in Auth0, port the same Id over to FusionAuth.
Auth0 provides Universal Login. This is a complex, configurable login component that works with SPAs, native applications and web applications.
FusionAuth’s login experience is less complicated. You can choose to build your own login pages or use FusionAuth’s hosted login pages. Read more about these choices.
Once you’ve planned your migration, the next step is to export your user data from Auth0.
To export users with the user interface, log in and navigate to your dashboard. You’ll perform the following steps:
Add the User Import/Export extension, if not present
Run the extension
Download the exported file
Add the Extension
Auth0 provides an extension that allows you to both import and export users to and from Auth0. Add the extension by navigating toand searching for it.
After you find the extension, install it:
The next step is to run the extension.
Run the Extension
Next, run the extension. The first time you run it, you’ll be asked to grant needed permissions. Then, choose the export tab.
This will bring up a screen with information such as what fields you want to export, which connections to pull users from, and the export file format.
For this guide, export user information as JSON. Choose the default user database. Finally, if you have special fields to include, configure their export as needed. Then begin the export.
Depending on how many users you have in your database, it may take a while for this to complete.
Download the File
After the export finishes, download the file provided. At the end of the process, you’ll end up with a JSON file like this:
This is half of the data you’ll need to migrate your users. The other half is the password hashes.
Exporting Password Hashes
Because password hashes are considered sensitive information, Auth0 does not export them as part of the general export process. You must file a support ticket to get the hashes and other password related information.
During this migration, passwords are never exposed in plaintext. Neither FusionAuth, Auth0, nor you ever have access to the password.
However, once you’ve exported the password hashes from Auth0 and imported them into FusionAuth, your users will be able to log in to FusionAuth with the same password they used previously.
If you are not able to export the hashes, due to the plan you are on or the migration timelines, one alternative is to have every user change their password using the forgot password flow. You can still import all the user data.
To start the process of obtaining the hashes, open a support ticket. From your dashboard, navigate to, and then open a ticket by scrolling to the bottom of the support page.
Select the issue and details of your request. Choose
I have a question regarding my Auth0 account and then pick the
I would like to obtain an export of my password hashes option.
You’ll receive an automated message after this ticket is submitted. View progress on the ticket screen.
Auth0 requires you to be on a paid plan to export your password hashes. You cannot export them otherwise.
Additionally, Auth0 makes no commitments about the processing time for a password hash request. In the author’s experience, it took approximately one week.
After your request is processed, you’ll download a JSON file containing password hashes, related information and user ids. It will look like this:
Now that you have both the user data and the password hashes, you can import your users.
Next up, import the user data. Here are the steps we need to take.
Set Up FusionAuth
Get the Script
Install Needed Gems
Use the Script
Verify the Import
The Final Destination of Imported Users
Set Up FusionAuth
You need to set up FusionAuth so migrated user data can be stored. As mentioned above, this guide assumes you have FusionAuth installed.
If you don’t, view our installation guides and install it before proceeding further.
Create a Test Tenant
It is best to create a separate tenant for migration testing. Tenants logically isolate configuration settings and users. If a migration goes awry or you need to redo it after tweaking settings, you can delete the test tenant and start with a clean system. To add a tenant, navigate toand choose the green plus sign.
Give it a descriptive name like
Auth0 import test. You shouldn’t need to modify any of the other configuration options to test importing users.
Save the tenant.
Record the Id of the tenant, which will be a UUID. It will look something like
25c9d123-8a79-4edd-9f76-8dd9c806b0f3. You’ll use this later.
Create a Test Application
Applications are anything a user can log in to. In FusionAuth there’s no differentiation between web applications, SaaS applications, APIs and native apps. To add an application, navigate to
Select your new tenant, created above, in the dropdown for the Tenant field.
Navigate to the Authorized redirect URLs. Use a dummy value such as
https://fusionauth.io. Later, you’ll need to update this to be a valid redirect URL that can take the authorization code and exchange it for a token. Learn more about this in the FusionAuth OAuth documentation.
You shouldn’t need to modify any of the other configuration options to test importing users. Save the application.
Next, view the application by clicking the green magnifying glass and note the OAuth IdP login URL. You’ll be using it to test that users can log in.
Add an API Key
The next step is to create an API key. This will be used by the import script. To do so, navigate toin the administrative user interface.
This key needs to have the permission to run a bulk import of users. In the spirit of the principle of least privilege, give it only the following permissions:
/api/identity-provider/linkendpoint (not shown below).
Record the API key string, as you’ll use it below.
Get the Script
FusionAuth provides an import script under a permissive open source license. It requires ruby (tested with ruby 2.7). To get the script, clone the git repository:
git clone https://github.com/FusionAuth/fusionauth-import-scripts
Navigate to the
Install Needed Gems
The following gems must be available to the import script:
Most likely all of these will be on your system already, except the
If you have
bundler installed, run
bundle install in the
auth0 directory. Otherwise install the needed gems in some other way.
Use the Script
You can see the output of the script by running it with the
ruby ./import.rb -h
The output will be similar to this:
Usage: import.rb [options] -l, --link-social-accounts Link social accounts, if present, after import. This operation is slower than an import. -r APPLICATION_IDS, A comma separated list of existing applications Ids. All users will be registered for these applications. --register-users -o, --only-link-social-accounts Link social accounts with no import. -u, --users-file USERS_FILE The exported JSON user data file from Auth0. Defaults to users.json. -f FUSIONAUTH_URL, The location of the FusionAuth instance. Defaults to http://localhost:9011. --fusionauth-url -k, --fusionauth-api-key API_KEY The FusionAuth API key. -t TENANT_ID, The FusionAuth tenant id. Required if more than one tenant exists. --fusionauth-tenant-id -s, --secrets-file SECRETS_FILE The exported JSON secrets file from Auth0. Defaults to secrets.json. -m, --map-auth0-id Whether to map the auth0 id for normal imported users to the FusionAuth user id. -h, --help Prints this help.
For this script to work correctly, set the following switches, unless the defaults work for you:
-ushould point to the location of the user export file you obtained, unless the default works.
-sneeds to point to the location of the password hash export file you received, unless the default works.
-fmust point to your FusionAuth instance. If you are testing locally, it will probably be
-kneeds to be set to the value of the API key created above.
-tshould be set to the Id of the testing tenant created above.
-l switches will attempt to create links for any social users (where the user authenticated via Google or another social provider) found in the users data file.
If you are loading social users, you must create the social providers in FusionAuth beforehand, or the links will fail. Additionally, creating a link is not currently optimized in the same way that loading users is. So it may make sense to import all the users in one pass (omitting the
-l switch). Then, after the users are imported, create the links using the
-o switch in a second pass.
The social account linking functionality will only work with FusionAuth versions above or equal to 1.28. The
fusionauth_client library must be >= 1.28 as well.
You may or may not want to use the
-m switch, which takes the Auth0 Id for users without a social login and uses the same value for the FusionAuth user Id. If you have external systems reliant on the Auth0 user identifier, set this. Doing so ensures imported users have the same Id as they did in Auth0. Otherwise, you can omit this switch.
When you run the script, you’ll see output like:
$ ruby ./import.rb -f http://localhost:9011 -k '...' -s secrets.json -u user-data.json FusionAuth Importer : Auth0 > User file: user-data.json > User secrets file: secrets.json > Call FusionAuth to import users > Import success Duplicate users 0 Import complete. 2 users imported.
Enhancing the Script
You may also want to migrate additional data. Currently, the following attributes are migrated:
the password hash and supporting attributes, if available
registrations, if supplied
The migrated user will have the Auth0 tenant Id and original user Id stored on the
user.data object. If you have additional user attributes to migrate, review and modify the
You may also want to assign Roles, or associate users with Groups, by creating the appropriate JSON data structures in the import call. These are documented in the Import User API docs. This will require modifying the
Verify the Import
Next, log in to the FusionAuth administrative user interface. Review the user entries to ensure the data was correctly imported.
You can manage the user by clicking on the black button to the right of the
Created date in the list to review the details of the imported user’s profile.
If you have a test user whose password you know, open an incognito window and log in to ensure the hash migration was successful. You recorded the URL to log in to the example application in Create a Test Application.
After the test login, the user will be redirected to a URL like
https://fusionauth.io/?code=FlZF97WIYLNxt4SGD_22qvpRh4fZ6kg_N89ZbBAy1E4&locale=fr&userState=Authenticated. This happens because you haven’t set up a web application to handle the authorization code redirect.
That is an important next step but is beyond the scope of this document. Consult the 5 minute setup guide for an example of how to do this.
The Final Destination of Imported Users
After you are done testing, you can choose to import users into the default tenant or a new tenant. Whichever you choose, make sure to update the
-t switch to the correct value before running the import for the final time.
If you aren’t keeping users in the test tenant, delete it.
If you need to start over because the import failed or you need to tweak a setting, delete the tenant you created. This will remove all the users and other configuration for this tenant, giving you a fresh start. To do so, navigate toand choose the red trash can icon.
Confirm your desire to delete the tenant. Depending on how many users you have imported, this may take some time.
Your users may have MFA enabled. If so, you will want to port that over.
The first thing to do is to look at the MFA methods available to your users. Here’s the list of Auth0 supported factors. You may not have enabled all of these. Here’s Auth0 documentation to see which you’ve enabled in the dashboard.
The method field of the Two-Factor API lists the MFA methods supported by FusionAuth. FusionAuth also supports recovery codes.
You can determine which type of MFA is used by each user by retrieving their data using the management API.
If a user uses email or SMS verification, you can port the data over to FusionAuth using the user update API or by adding the twoFactor fields to your import JSON. The former will trigger an MAU increment, while the latter will not.
While you can’t generate a fixed set of recovery codes, once MFA has been enabled for a user, you can retrieve the recovery codes.
If your user uses TOTP, where they provide a one time code provided by an application like Google Authenticator, you’ll need to request the initial secret for your users from Auth0 by opening a support ticket with them.
If your users use a different method unsupported by FusionAuth, then you should map the Auth0 method to a FusionAuth method.
Push Notifications: It is possible a Generic Messenger would work, but this would require some investigation and custom coding.
What to Do Next
You now have your users migrated, or a plan to do so. Congratulations! What is next?
You need to migrate additional configuration, as mentioned in Other Entities. Since the type of configuration varies, it is hard to provide a full list of how to import these items, but the general pattern will be:
Identify corresponding FusionAuth functionality.
Update your application configuration to use the new FusionAuth functionality.
Make sure you assign your users to the appropriate FusionAuth applications. You can do this either:
As part of your import process by adding registrations at import time.
After users have been migrated with the Registrations API.
You’ll also need to modify and test each of your applications, whether custom, open source, or commercial, to ensure:
Users can successfully log in.
The authorization code redirect is handled correctly.
Users receive appropriate permissions and roles based on the JWT.
The look and feel of the hosted login pages matches each application’s look and feel.
If your application uses a standard OAuth, SAML or OIDC library to communicate with Auth0, the transition should be relatively painless.
If you need support in your migration beyond that provided in this guide, you may: