How to export your data from FullStory

FullStory lets you pull data out in two ways: a quick one-click 'Export as CSV' of up to 10,000 users from any search/segment, or a full Segment/Data Export (CSV, JSON, or NDJSON, gzipped) containing user, session, page, and event-level fields, available to Advanced/Enterprise customers.

Formats: CSV, JSON, NDJSONPlan: Basic 'Export as CSV' works on any plan; full Segment Export / Data Export module requires an Advanced or Enterprise planRole: Admin or Architect role to configure Data Export / Segment Export

✓ Verified against FullStory's official documentation, September 2026

Step by step

1Open the Segment (saved search) you want to export, or run a search to build one
2Above the session playlist, click 'Create Export' (for the full Segment Export) or 'Export as CSV' (for a quick user list)
3For Segment Export: name the export and confirm the time range, which defaults to the segment's time range
4Choose a download type: CSV, JSON, or NDJSON
5Click Export - this creates a job in the Data Exports table at the bottom of the sidebar
6Wait for the job status to change from 'In Progress' to 'Completed' (a few seconds up to 5-10 minutes depending on data volume)
7Download the file, then unzip the .gz archive (Windows needs 7-Zip or similar; Mac OS can unzip natively)
8Open the file in Excel, Numbers, Google Sheets, or process it with R/Python

What the export includes

✓User/session identifiers (IndvId, UserId, SessionId, PageId, UserAppKey, UserDisplayName, UserEmail, IP address)
✓Page-level fields (PageName, PageUrl, PageDuration, ActivePageDuration, referrer, scroll depth, screen/viewport size)
✓Event-level fields (EventType, EventSubType, EventCategory, custom event names, event target text/selector, event duration)
✓Behavior heuristics (rage clicks, dead clicks, error clicks, suspicious/SQLi/XSS flags)
✓Any custom user, page, or event variables you passed in via FS.identify, FS.setUserVars, or FS.event
✓For the simple 'Export as CSV': user name, email, uid, last page, session counts/durations, last browser/device

What it doesn't include

✗Segment Export / full Data Export is not available on plans below Advanced/Enterprise - those accounts are limited to the basic 10,000-row 'Export as CSV'
✗Data for individuals already deleted from FullStory before the export runs (exports are generated on-demand from live data, so deleted users are simply absent)
✗Anything older than your account's Product analytics retention window - once data ages out and is deleted, it cannot be recovered or exported
✗Console statistics and some derived metrics may be incomplete if the export is run too soon after events occur

Before you start

⚠Events are generally available in Data Export about 30 minutes after they occur, but FullStory recommends waiting 24 hours (or a minimum of 3 hours) for values to fully settle before treating an export as final
⚠Data Export download files expire and are only available for 7 days from when the export completed
⚠The basic 'Export as CSV' from search results is capped at the most recent 10,000 users matching your search
⚠Windows users need an extra tool like 7-Zip to open the gzipped export files; Mac users can unzip natively
⚠If you plan to store exports long-term, remember that a later user-deletion request in FullStory means you're responsible for deleting that person's data from your own downstream storage too
⚠The legacy HTTP Data Export API is deprecated in favor of the newer Segment Export API

Where to take your data

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

PostHog

Alternatives

There's no native FullStory importer. Map the exported CSV/JSON/NDJSON event and user fields (UserId, SessionId, EventType, timestamps, custom vars) to PostHog's event schema and load historical events via PostHog's HTTP capture/batch API or the Python/Node client.

LogRocket

LogRocket doesn't support bulk import of historical FullStory sessions or events; treat the FullStory export as a cold-storage archive and start fresh session capture in LogRocket going forward.

Microsoft Clarity

Clarity has no import mechanism for third-party export files either; keep the FullStory CSV/JSON export for historical reporting/analytics while switching new session recording to Clarity.

Exporting from FullStory: common questions

Can I export my FullStory data if I'm not on an Advanced or Enterprise plan?+

You can still use the one-click 'Export as CSV' on any search or segment, which downloads up to 10,000 matching user rows. The full Segment Export / Data Export module (CSV, JSON, NDJSON with page- and event-level detail) requires an Advanced or Enterprise plan.

What file formats does FullStory export data in?+

Segment Export offers three download types - CSV, JSON, and NDJSON - all delivered as a gzipped file that you need to unzip before opening in a spreadsheet or scripting tool.

How far back can I export historical data?+

Export availability matches your account's Product analytics retention length - if you're on 12 months of retention, you can export up to 12 months of history; once data ages out it's permanently deleted and can't be exported.

How long do I have to download a finished export?+

Completed Data Export files remain available for download for 7 days from when the export job finished.

Who is allowed to run a full Data Export?+

Configuring Segment Export / Data Export requires an admin or architect role; the simpler 'Export as CSV' on search results is available to regular users.

Does the export include the actual session replay recordings?+

No. FullStory's documented export contents are structured fields - user, session, page, and event data (IDs, timestamps, URLs, click text, custom variables, etc.) - not the visual session replay itself.