How to Export Data from CrowdStrike Falcon: Hosts, alerts, policies and telemetry, route by route

CEO CSIBy Vincent Sullivan, former Technical Director, U.S. Cyber CommandUpdated October 20268 min read
The short answerThere is no single export button. Device inventory, alerts and every policy, exclusion and custom rule come out through the Falcon API, most easily with CrowdStrike's FalconPy or PSFalcon tools. Raw telemetry needs Falcon Data Replicator, a separate subscription that CrowdStrike Support enables. Users don't export, the old Detects API had a decommission date of September 30, 2025, and policies come out in Falcon's own JSON format, which you rebuild in any new product.
Where your Falcon data lives, and how it gets outData-flow map
DataExport routeLands as
Device inventoryHosts
Hosts API
JSON you saveScope: Hosts read
AlertsDetections
Alerts API
JSONDetects API decommission date Sep 30, 2025
PoliciesPrevention, sensor, device, firewall, response
API or Export-FalconConfig
Falcon JSONRebuild in any new product
ExclusionsML, IOA, sensor visibility
API or Export-FalconConfig
Falcon JSONReview before rebuilding
Custom IOAs and IOCsYour detection logic
Custom IOA and IOC APIs
Falcon JSONTranslate to new rule syntax
RTR scriptsScripts and put-files
RTR Admin API
Script filesUsually portable
Raw telemetryEvery event
Falcon Data Replicator
S3 via SQSSeparate subscription
Live eventsDetections, audit
Event Streams or SIEM Connector
JSON log streamScope: Event streams read

Users don't export. Gold border: needs a separate license. Every route is documented by CrowdStrike; see the table and sources below.

Step 0

Before you start: an API client, the right scopes, the right region

Almost everything in this guide runs through CrowdStrike's OAuth2 API. An administrator creates an API client in the Falcon console under Support, API Clients and Keys, picks the scopes it needs, and saves the client ID, client secret and base URL.[1] Access is governed by both the API scopes and the user's role, and the base URL depends on your cloud region.[2] Tokens come from the OAuth2 token endpoint and last 30 minutes, so long exports need to refresh them.[3]

You don't need to write raw HTTP calls. CrowdStrike maintains FalconPy, its official Python SDK, which is in the public domain and installs with pip.[4] It has a service class for every collection used in this guide. For PowerShell shops, CrowdStrike's PSFalcon module includes a one-command configuration export, covered in step 4.[5]

Do this firstGrant read scopes only. An export client has no reason to change anything, and a read-only client can't damage the tenant you are leaving. Uninstall-token reveal and RTR Admin retrieval may need scopes beyond plain read; check them in the API client screen.

Data inventory

What you can export from Falcon, and how

This is the full map. The FalconPy class names are copied from the SDK source.[6]

Falcon data inventory and export routes
DataRouteFalconPy classNotes
Device inventory [7]Hosts API: query by filter, device details, hidden hosts, login historyHostsScope: Hosts read
Alerts [8]Alerts API: query, full records, aggregatesAlertsReplaces Detects, decommissioned Sep 30, 2025 [9]
Incidents [10]Incidents APIIncidentsSDK marks it for removal in March 2026
Prevention policies [11]Prevention Policy APIPreventionPolicyWindows, Mac, Linux, iOS and Android
Sensor update policies [12]Sensor Update Policy APISensorUpdatePolicyAlso reveals uninstall tokens
Device control policies [13]Device Control Policies API (v2 operations)DeviceControlPoliciesUSB and Bluetooth rules
Firewall rules and policies [14]Firewall Management APIFirewallManagement, FirewallPoliciesRules, rule groups, network locations
Response policies [15]Response Policies APIResponsePoliciesReal Time Response permissions
Host groups [16]Host Group APIHostGroupDynamic groups export as a rule, not a member list
Custom IOA rules [17]Custom IOA APICustomIOAPer-platform rule groups
Custom IOCs [18]IOC APIIOCIndicators, actions, severities
ML, IOA and sensor visibility exclusions [19][20][21]Three exclusion APIsMLExclusions, IOAExclusions, SensorVisibilityExclusionsReview each before rebuilding
Certificate-based exclusions [6]Certificate-based exclusions APICertificateBasedExclusionsCheck whether you use them
RTR scripts and put-files [22]Real Time Response Admin APIRealTimeResponseAdminCan retrieve put-file contents
Raw telemetry [23]Falcon Data ReplicatorFDR (schema only)Separate subscription; enabled by CrowdStrike Support
Live detections and audit events [24]Event Streams API or SIEM ConnectorEventStreamsScope: Event streams read
Users and accounts [5]Not exportedn/aRecreate in the new product

Route by route

Step by step: getting each data type out

Step 1. Device inventory

The Hosts collection searches devices with Falcon Query Language filters and returns full device details, hidden hosts, online state and recent login history.[7] Export everything, hidden hosts included. Your new product's rollout plan starts from this list, and your final reconciliation will compare against it.

Step 2. Alert history

Use the Alerts collection, which supports filtered queries, full-record retrieval and aggregates.[8] Don't build on the old Detects API: CrowdStrike marked the whole collection deprecated and set its decommission date as September 30, 2025.[9] Expect older scripts that call it to fail.

Step 3. Incidents, while you still can

FalconPy marks every Incidents method with a note that the Incidents API will be removed in March 2026, and the collection no longer appears in CrowdStrike's developer index.[10][25] If your tenant still answers those calls, save what you need now. If it doesn't, the alert history from step 2 is your record.

Step 4. Policies, groups and exclusions in one pass

You can call each policy API separately, or use PSFalcon's Export-FalconConfig, which writes host and firewall groups, IOA groups, prevention, sensor update, device control, firewall, response and content policies, all three exclusion types, IOCs, scripts and FileVantage settings to a zip of JSON files.[5] The matching Import-FalconConfig restores them to the same or another Falcon tenant. Note what that means: the JSON is Falcon's format. It moves between CrowdStrike tenants, not into another vendor's product. For a migration it is your reference copy, not an import file.

Two objects need extra care. Dynamic host groups are defined by a rule, so you export the rule and re-express it in the new product's grouping logic.[16] Exclusions deserve a review rather than a straight copy; many exist to quiet a false positive the new product may never raise.

Step 5. Custom detection logic

Custom IOA rule groups and custom IOCs export through their own APIs.[17][18] IOCs, being hashes, domains and addresses, usually move cleanly. IOA rules describe behavior in CrowdStrike's pattern syntax and need translating, rule by rule.

Step 6. Real Time Response scripts

The RTR Admin collection lists, retrieves and manages custom scripts and put-files, and can return put-file contents.[22] Scripts written in PowerShell or bash usually run elsewhere with small changes.

Step 7. Raw telemetry and live streams

Falcon Data Replicator delivers enriched, near real-time telemetry for your own data lake, SIEM or warehouse. CrowdStrike's own guide describes CrowdStrike-hosted S3 buckets that you pull from through a CrowdStrike-provided SQS queue. It needs an active FDR subscription and can only be enabled by CrowdStrike Support.[23] CrowdStrike keeps a full FDR record for at least seven days, so your copy is the long-term archive.[26] The FDR API itself only returns event schemas; it doesn't move data.[27]

For real-time detections and audit events, the Event Streams API returns stream URLs and session tokens, and CrowdStrike's SIEM Connector keeps a persistent connection to it and writes events to a local JSON log for a log shipper to collect.[24][28] If you use Falcon Next-Gen SIEM, its API runs searches and manages saved queries, but its documentation doesn't describe a bulk raw-event export.[29]

Step 8. Uninstall tokens

Hosts with uninstall protection need a maintenance token to remove the sensor. The Sensor Update Policy API can reveal those tokens.[12] Retrieve them before the contract ends; removing protected sensors at scale without them is slow work.

The gaps

What you can't export, and how to rebuild it

  • Users and roles. PSFalcon's export skips them because user accounts are unique and can't be duplicated.[5] Rebuild access in the new product from your identity provider.
  • Raw history without FDR. No FDR subscription means no bulk export of raw events. What you keep is alert history and whatever your SIEM already collected.[23]
  • Behavioral rules in a portable format. Custom IOA patterns, prevention settings and exclusions are Falcon-specific. Treat them as a specification for the new product, not an import file.
  • Retired API data. Detection IDs and workflows from the Detects era, and the Incidents API, won't carry forward as they were.[9][10]
  • Retention beyond your tier. CrowdStrike sells extended search retention separately; anything older than what you hold has aged out.[30]

Working list

The Falcon export checklist

Use this as your runbook. The boxes keep count while you work; nothing is saved or sent anywhere.

Export checklistTick as you go

Before you cancel

Verify the export, then plan the cutover

  1. Reconcile counts. Hosts, policies, exclusions and IOCs in your files should match the console on the day you exported.
  2. Spot-check content. Open three policies and three exclusions and confirm every setting is present.
  3. Keep Falcon running while the new product deploys. A coverage gap during migration is the most avoidable risk in the project.
  4. Time it to renewal. Export at least 60 days before the renewal date so you have room to deploy, pilot and retire.
  5. Store the export securely. It describes your defenses in detail. Treat it as sensitive.

The full cutover sequence, from pilot to retirement, is in our CrowdStrike migration guide. If you are still deciding where to go, read the CrowdStrike Falcon review, the shortlist of CrowdStrike alternatives and CrowdStrike vs SentinelOne. The EDR buyer's guide covers what to ask the next vendor, including how you would export from them. If cost drove the decision, check the numbers in CrowdStrike Falcon pricing first.

CSI runs Warden migrations with Falcon still installed, so endpoints are covered from day one. See Warden vs CrowdStrike, the Warden platform, or the full EDR comparison hub. Agencies can start with government solutions.

Methodology

How this guide was built

Every route and class name comes from CrowdStrike's public Developer Center, the FalconPy and PSFalcon repositories on GitHub, and CrowdStrike's published guides, all opened on the research date below. Some CrowdStrike documentation sits behind the customer login; where a detail was only there, we left it out. We found no public CrowdStrike documentation of console CSV exports or of the specific user roles needed to create API clients or enable FDR, so confirm both with your Falcon administrator. We re-check API deprecations every 90 days.

Disclosure: CSI resells Warden, a CrowdStrike competitor. This guide is useful whichever product you move to.

FAQ

Falcon export questions

Can I export everything from CrowdStrike Falcon?

Most configuration and history, yes: device inventory, alerts, policies, host groups, exclusions, custom IOAs, IOCs and RTR scripts all have API routes.[6] Users do not export, and raw telemetry needs a Falcon Data Replicator subscription.[5][23]

What replaced the CrowdStrike Detects API?

The Alerts API. CrowdStrike marked the whole Detects collection deprecated with a decommission date of September 30, 2025, and directs developers to the Alerts collection.[9][8]

Does Falcon Data Replicator send data to my own S3 bucket?

CrowdStrike's FDR guide describes CrowdStrike-hosted S3 buckets that the customer pulls from using a CrowdStrike-provided SQS queue. FDR needs its own subscription and is enabled by CrowdStrike Support.[23]

Can I import my Falcon policies into another EDR?

Not directly. PSFalcon's Export-FalconConfig saves policies and exclusions as Falcon-format JSON that Import-FalconConfig can restore to another Falcon tenant.[5] For another vendor, use the export as a specification and rebuild the settings.

What API scopes do I need to export Falcon data?

Read scopes for each collection you export, for example Hosts, Alerts, the policy collections, the exclusion collections and Event Streams. Access also depends on the user's role, and the base URL depends on your region.[2][1]

How do I remove Falcon sensors that have uninstall protection?

Retrieve the maintenance tokens first. The Sensor Update Policy API can reveal uninstall tokens for protected hosts.[12]

How long does a Falcon export take?

Configuration exports with PSFalcon or FalconPy are usually quick. Alert history and telemetry depend on volume. Plan the export at least 60 days before renewal so deployment and verification aren't rushed.

Next step

Leaving Falcon? Keep every endpoint covered on the way out

CSI deploys Warden alongside Falcon, pilots it on your awkward hosts, and times the cutover to your renewal. No gap in coverage.

Vincent Sullivan

Vincent Sullivan, founder and CEO of Cyber Strategy Institute. Twenty-two years as a U.S. Air Force cyber officer, finishing as Technical Director at U.S. Cyber Command. CSI designs prevention-first security architecture and publishes AI SAFE², an open AI governance framework.

About CSI and the team

Sources

Sources and research date

Every figure on this page links to the public source below. Research date: Oct 3, 2026. Vendor claims are labeled as vendor claims.

  1. Quick Start (API client creation). CrowdStrike Developer Center. https://developer.crowdstrike.com/falcon-mcp/getting-started/quickstart/. Accessed Oct 3, 2026.
  2. API Reference overview. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/overview/. Accessed Oct 3, 2026.
  3. OAuth2 collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/oauth2/. Accessed Oct 3, 2026.
  4. FalconPy, the CrowdStrike Falcon SDK for Python. CrowdStrike (GitHub). https://github.com/CrowdStrike/falconpy. Accessed Oct 3, 2026.
  5. Export-FalconConfig (PSFalcon wiki). CrowdStrike (GitHub). https://github.com/CrowdStrike/psfalcon/wiki/Export-FalconConfig. Accessed Oct 3, 2026.
  6. FalconPy service class list (__init__.py). CrowdStrike (GitHub). https://raw.githubusercontent.com/CrowdStrike/falconpy/main/src/falconpy/__init__.py. Accessed Oct 3, 2026.
  7. Hosts collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/hosts/. Accessed Oct 3, 2026.
  8. Alerts collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/alerts/. Accessed Oct 3, 2026.
  9. Detects collection (deprecated). CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/detects/. Accessed Oct 3, 2026.
  10. FalconPy incidents.py (deprecation note). CrowdStrike (GitHub). https://raw.githubusercontent.com/CrowdStrike/falconpy/main/src/falconpy/incidents.py. Accessed Oct 3, 2026.
  11. Prevention Policy collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/prevention-policy/. Accessed Oct 3, 2026.
  12. Sensor Update Policy collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/sensor-update-policy/. Accessed Oct 3, 2026.
  13. Device Control Policies collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/device-control-policies/. Accessed Oct 3, 2026.
  14. Firewall Management collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/firewall-management/. Accessed Oct 3, 2026.
  15. Response Policies collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/response-policies/. Accessed Oct 3, 2026.
  16. Host Group collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/host-group/. Accessed Oct 3, 2026.
  17. Custom IOA collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/custom-ioa/. Accessed Oct 3, 2026.
  18. IOC collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/ioc/. Accessed Oct 3, 2026.
  19. ML Exclusions collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/ml-exclusions/. Accessed Oct 3, 2026.
  20. IOA Exclusions collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/ioa-exclusions/. Accessed Oct 3, 2026.
  21. Sensor Visibility Exclusions collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/sensor-visibility-exclusions/. Accessed Oct 3, 2026.
  22. Real Time Response Admin collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/real-time-response-admin/. Accessed Oct 3, 2026.
  23. Falcon Data Replicator SQS add-on for Splunk: installation guide. CrowdStrike. https://www.crowdstrike.com/wp-content/uploads/2021/10/crowdstrike-falcon-data-replicator-fdr-sqs-technical-add-on-guide.pdf. Accessed Oct 3, 2026.
  24. Event Streams collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/event-streams/. Accessed Oct 3, 2026.
  25. Operations by Collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/operations-by-collection/. Accessed Oct 3, 2026.
  26. Falcon Data Replicator data sheet. CrowdStrike. https://www.crowdstrike.com/wp-content/uploads/2022/06/crowdstrike-falcon-data-replicator-data-sheet.pdf. Accessed Oct 3, 2026.
  27. FDR collection (schema only). CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/fdr/. Accessed Oct 3, 2026.
  28. Collecting SIEM Connector data with Cribl Edge (guide v1.4). CrowdStrike. https://www.crowdstrike.com/wp-content/uploads/2023/07/crowdstrike-siem-cribl-edge-connector-guide.pdf. Accessed Oct 3, 2026.
  29. Next-Gen SIEM collection. CrowdStrike Developer Center. https://developer.crowdstrike.com/api-reference/collections/ngsiem/. Accessed Oct 3, 2026.
  30. Falcon Search Retention data sheet. CrowdStrike. https://www.crowdstrike.com/wp-content/uploads/2024/01/Falcon-Search-Data_Retention_V2.pdf. Accessed Oct 3, 2026.

Stop Threats Before They Execute

Your free Kernel-Level Defense Buyer’s Guide is ready to download.

By providing my email address, I consent to receive emails and text messages—including newsletters and marketing communications—from creators of Warden Secure, Cyber Strategy Institute, our flagship zero-trust platform for ransomware prevention, and agree to the Terms and Privacy Policy. You may unsubscribe at any time.