How to export your data from Auth0

Auth0 lets you bulk-export user profile data (not credentials or tenant config) as CSV or NDJSON via the Dashboard's Import/Export Users screen or the Management API's export-users job endpoint; the download link is only valid for 60 seconds and the job expires after 24 hours.

Formats: CSV, JSON (NDJSON)Plan: Not available on the Auth0 Free plan; requires a paid plan (Essentials or higher)Role: Dashboard role of Admin, Editor - Users, or Dashboard Viewer - Users, OR a Management API token with the export-users job scope

✓ Verified against Auth0's official documentation, September 2026

Step by step

1Log in to the Auth0 Dashboard and go to User Management > Users
2In the top right corner, select 'Import/Export Users' to open the Import/Export Users page
3Select 'Export Users' to go to the Export Users page
4Under Export Settings, choose the database Connection to export from and pick the Export Format: JSON or CSV
5In Export Fields, toggle 'Include default fields' for the normalized user profile schema, or use 'Add Fields' to add specific user/metadata attributes
6Optional: check 'Export as Sample' to limit the test export to 10 users
7Select 'Export Users' to submit the job
8Return to the Import/Export Users page, use 'Check Status' to monitor progress, then 'Download export' once it's done (link is valid 60 seconds; you have 24 hours before the job/file expires)

What the export includes

✓User profile fields defined in Auth0's normalized user profile schema (e.g. user_id, email, name, identities/connection info)
✓Custom user_metadata and app_metadata fields you explicitly select
✓Data scoped to one database connection per export job (or all connections if you omit connection_id via the Management API)

What it doesn't include

✗Password hashes, MFA secrets, or other credentials (export is limited to 'supported user profile data', not auth secrets)
✗Tenant configuration: connections, Applications/APIs, Roles/Permissions, Rules/Actions, branding, logs
✗Full user_metadata/app_metadata as a single nested object in CSV format (must be listed as individual sub-fields, or exported as JSON instead)

Before you start

⚠Bulk export is not available on the Free plan at all
⚠CSV exports are capped at 30 fields
⚠CSV can't export app_metadata/user_metadata as whole objects — you must specify each sub-field, or switch to JSON format
⚠CSV string values are escaped per OWASP CSV-injection rules (extra quote characters prepended), which can affect how the file looks when reimported elsewhere
⚠All job-related data (including the export file) is automatically deleted 24 hours after the job completes
⚠The download URL itself is only valid for 60 seconds each time you access it, though you can re-request it within the 24-hour window
⚠Export as Sample limits a test run to 10 user records to validate structure before running the full export

Where to take your data

Free and cheaper tools that can take a Auth0 export. See all Auth0 alternatives →

Clerk

Map the exported user fields (email, user_id, metadata) to Clerk's user import format and bulk-create users via Clerk's Backend API or dashboard import; passwords/MFA won't carry over since Auth0 doesn't export them, so plan for a password-reset flow post-migration.

Supabase Auth

Use the exported CSV/NDJSON as input to script bulk user creation against Supabase's Admin API (auth.admin.createUser), mapping email and metadata fields; as with Clerk, users will need to reset passwords since Auth0 doesn't export credential hashes.

Exporting from Auth0: common questions

Can I export my Auth0 users if I'm on the Free plan?+

No. Bulk user export is explicitly not available on the Auth0 Free plan — you need a paid plan to use the Export Users feature.

What file formats does Auth0 export to?+

CSV or JSON. The JSON export is actually NDJSON (newline-delimited JSON) because export files can be large.

Does the export include user passwords?+

No. The feature exports 'supported user profile data' — profile fields and metadata — not password hashes or MFA secrets.

How long do I have to download my export before it expires?+

The generated download link is valid for 60 seconds at a time, and all job data (including the file) is deleted 24 hours after the job finishes, so you have a 24-hour window to grab it.

Can I export users from all connections at once?+

Through the Dashboard, export is per database connection. Via the Management API, you can omit connection_id in the export job request to export users across all connections.

Who is allowed to run a user export?+

In the Dashboard, you need the Admin, Editor - Users, or Dashboard Viewer - Users role. Via the Management API, you need a token with the scopes for the Create export users job endpoint.