How to export your data from Okta
Okta has no single 'export all my data' button. Users are exported as CSV by downloading the Okta Password Health report from Admin Console > Reports; applications and groups have no built-in export and must be pulled via the unofficial Rockstar Chrome extension or the Okta Management API (JSON, converted to CSV).
✓ Verified against Okta's official documentation, September 2026
Step by step
- 1In the Okta Admin Console, go to Reports.
- 2Select the Okta Password Health report link to download it as a CSV file — this is the report Okta's own documentation points to for getting a user list.
- 3Open the CSV and filter the Status column (e.g. to 'Active') to get the working user list you need.
- 4For applications, go to Applications > Applications — Okta has no built-in function to export the app list, so use either the community Rockstar extension or the API.
- 5If using Rockstar: open its menu in the browser, select 'Export Apps (custom)', choose the properties to export, optionally add a filter like filter=status eq "ACTIVE", then click Export.
- 6If using the API instead: call GET /api/v1/apps (or /api/v1/users with a filter) with an admin API token via a client like Postman.
- 7Add ?limit=200 to pull up to 200 records per call, and follow the 'next' link in the response's Link header to page through the rest — the default page size is only 20.
- 8Save the JSON response and run it through a JSON-to-CSV converter to get a spreadsheet; repeat the Rockstar or API steps for Groups if you also need group membership.
What the export includes
- ✓User records from the Password Health CSV report, filterable by status (e.g. Active)
- ✓Application list (name, status, and other selected properties) via Rockstar export or the /api/v1/apps endpoint
- ✓Group and group-membership lists via the equivalent Rockstar/API export flow
What it doesn't include
- ✗No single combined 'all my Okta data' archive — users, apps, and groups must each be exported separately
- ✗Passwords, password hashes, and MFA factor secrets — these are never exposed through the Admin Console, Reports, or the API
- ✗Okta's System Log / audit trail, which is a separate feature not covered by the user, app, or group export methods above
- ✗Authentication policies, workflows, and third-party app integration configuration
Before you start
- ⚠There is no built-in function to list all applications in an Okta tenant — you must use the unofficial Rockstar extension or the API
- ⚠Rockstar is a community-built Chrome extension not created by Okta; Okta Support cannot troubleshoot it if it breaks
- ⚠The API returns JSON only, so exporting to CSV always requires an extra conversion step with a separate tool
- ⚠The default API page size is 20 results; you must raise it to a max of 200 with the limit parameter and paginate via the Link header for larger orgs
- ⚠The 'export users' CSV method is really just downloading the Password Health report and manually filtering it — it isn't a purpose-built users export
- ⚠Required admin role differs by method: Reports Admin for the Admin Console CSV, Read-Only Administrator with People tab access for Rockstar
Where to take your data
Free and cheaper tools that can take a Okta export. See all Okta alternatives →
Auth0 Free
Reformat the exported Okta user CSV/JSON into Auth0's bulk user import JSON schema, then run it through the Auth0 Dashboard's user import job or Management API; passwords will need to be reset since Okta doesn't export password hashes.
Map the exported Okta user list to WorkOS's User Management Admin API and create users via API calls; use the exported app/group data to recreate SSO connections and directory groups manually since config isn't included in Okta's exports.
Convert the exported Okta user CSV/JSON to match Clerk's user import format and use Clerk's backend API or migration scripts to bulk-create users, having them reset passwords on first login.
Exporting from Okta: common questions
Can I export all my Okta data in one click?+
No. Okta has no single full-account export. You export users via the Password Health CSV report, and applications/groups via the unofficial Rockstar extension or the Management API — there's no built-in function to export the full app list at all.
What format does Okta export data in?+
CSV, via the Admin Console Reports section or the Rockstar extension, or JSON from the Management API (which you then convert to CSV yourself).
Is the Rockstar extension an official Okta tool?+
No. It's a community-built, unofficial Chrome extension. Okta explicitly says it did not create it and Okta Support cannot troubleshoot it if it stops working.
How many users or apps can I pull per API request?+
The default is 20 records per call. You can raise this to a maximum of 200 with the limit parameter, and must follow the Link header's 'next' URL to page through additional results.
Can I export passwords or MFA secrets from Okta before switching providers?+
No. None of Okta's documented export methods (Admin Console reports, Rockstar, or the API) expose passwords or MFA factor secrets — users will need to reset credentials on whatever platform you migrate to.
Do I need a paid or Enterprise Okta plan to export data?+
No. Okta's documentation doesn't gate any of these export methods behind a specific plan — access is controlled by admin role (Reports Admin, Read-Only Administrator, or API token permissions), not subscription tier.
Sources
This guide was written from Okta's own documentation and checked against it in September 2026. If a step has changed, the official page wins.
Okta head-to-head
More Security tools people are leaving
All Security alternatives →What would you save without Okta?
Pick your team size and see the yearly number.