Good Morning!
I am attempting to implement lazy migration for Auth0 tenants using the following github code:
The issue I am running into, is that this code was last updated 9 years ago and the readme instructions for configuration within the Auth0 Management Dashboard for the new and old accounts no longer apply. Is there any advice you can give me on how to configure my accounts for use with this code?
Thanks
T
You are attempting to implement lazy migration for Auth0 tenants using a 9-year-old GitHub repository (auth0-account-migration), but the configuration instructions in the README no longer match the current Auth0 Management Dashboard interface. You want to know how to configure your old and new Auth0 tenants to work with this code.
Lazy migration is still a fully supported Auth0 feature, but the Dashboard interface has changed significantly since that code was written. You will need to update the configuration steps to match the current Dashboard UI. The core mechanism — custom database connections with login scripts — remains the same, but the specific steps and settings locations have changed.
[Root Cause]
The GitHub repository was last updated 9 years ago, and Auth0's Management Dashboard has undergone significant UI redesigns and feature updates since then. The configuration steps in the README reference Dashboard locations and settings that no longer exist or have been moved. Additionally, the Node.js runtime and Auth0 API versions may have changed, potentially requiring updates to the code itself.
Current Lazy Migration Architecture (Still Supported):
Auth0 lazy migration works by:
Current Configuration Steps:
For the Old Tenant (Source of Users):
Step 1: Create a custom database connection
Navigate to Auth0 Dashboard → Connections → Database.
Click "Create DB Connection" or select an existing custom database.
Name it something like "Legacy-Database" or "Migration-Source".
Step 2: Configure the connection to your legacy database
In the connection settings, enable:
Step 3: Write the login script
Click the "Custom Database" tab → "Login" script.
Replace the template with a script that:
Example structure (update with your database details):
function login(email, password, callback) {
// Connect to your legacy database
// Query for user by email
// Validate password
// Return user profile: { user_id, email, ... }
// On error: callback(new WrongUsernameOrPasswordError(email))
}Step 4: Write the getUser script (optional but recommended)
Click the "Custom Database" tab → "Get User" script.
This script is called when Auth0 needs to fetch user information without a password. It should:
Step 5: Test the scripts
Click the "Try Connection" button.
Enter test credentials from your legacy database.
Verify that:
Step 6: Enable the connection for your application
Navigate to Applications → Your Application → Connections.
Enable the custom database connection you just created.
Disable or deprioritize the default "Username-Password-Authentication" connection (optional, depending on your migration strategy).
For the New Tenant (Destination of Users):
Step 1: Verify the default database connection
Navigate to Connections → Database.
Ensure "Username-Password-Authentication" exists and is enabled.
Step 2: Enable the connection for your application
Navigate to Applications → Your Application → Connections.
Enable "Username-Password-Authentication".
This is where migrated users will be stored.
Step 3: Configure post-migration (optional)
Once users are migrated, you can:
Important Configuration Notes:
1. Connection must be enabled for the application
Common issue: Users get "connection is not enabled" error.
Solution: Ensure the custom database connection is explicitly enabled for your application in Applications → Your Application → Connections.
2. Script return values must be correct
The login script must return:
callback(null, {
user_id: "string", // Must be a string, not an integer
email: "user@example.com",
// ... other profile fields
});3. "Import users to Auth0" must be enabled
Without this setting, users are not migrated — they are only authenticated against the legacy database.
4. Username vs. email
If your legacy database uses usernames instead of emails:
username field in the profileRegarding the 9-Year-Old GitHub Code:
The code may need updates for:
tedious@1.11.0 for SQL Server)Recommended Approach:
Option 1: Use the GitHub code as a reference, not a template
Option 2: Update the GitHub code for current environments
Option 3: Use Auth0's official migration tools
If lazy migration is not critical, consider:
Next Steps:
1. Review the current Auth0 documentation
Read: Configure Automatic Migration from Your Database
This is the official, current guide for lazy migration.
2. Identify your legacy database type
Determine whether you're migrating from:
3. Write or update the login script
Use the GitHub code as a reference, but write a script specific to your database.
4. Test in a development tenant
Before using in production, test the entire flow:
5. Contact Auth0 Support if needed
If you encounter issues with:
Create a support ticket with:
Bottom line: Lazy migration is still fully supported by Auth0. The 9-year-old GitHub code provides a valid pattern, but you will need to update the configuration steps to match the current Dashboard UI and potentially update the code itself for current Node.js and database library versions. Start with the official Auth0 documentation linked above, use the GitHub code as a reference for the script logic, and test thoroughly in a development environment before deploying to production.
Kind Regards,
Nik