Data Exports
Overview
Fortress also supports integration through scheduled data exports delivered via SFTP. This is currently the best option for downstream analytics workflows that need bulk data in files instead of API calls.
Upon request, Fortress provisions an SFTP folder for each organization to access its exported data. Refresh cadence varies based on integration needs.
Architecture
The following diagram shows the data export integration flow.
Export Delivery Model
Fortress supports two export delivery modes:
-
Full load A full snapshot file for a topic (for example, Activities or Work Orders) is delivered.
-
Change detect (CDC) A full snapshot file is delivered first. After that, additional files include only row-level changes for that topic.
Folder Structure
Exports are organized by organization and topic folder.
Equivalent parquet exports use the same path pattern with .parquet file extension.
Example Topic Folders
Based on a typical organization export location, you may see folders such as:
Example Files Per Topic
Full-load and CDC files for a topic might look like:
In CDC mode, incremental files follow YYYYMMDD-HHMMSSfff ordering.
File Formats
Exports can be delivered in either of the following formats:
csvparquet
Typical Integration Flow
- Fortress provisions the organization SFTP location.
- Consumer reads initial full-load files per topic.
- Consumer processes ongoing CDC files for incremental updates.
Getting Started
- Contact Fortress to enable Data Exports for your organization.
- Confirm required topics and preferred file format (
csvorparquet). - Align on refresh cadence and CDC enablement during onboarding.
- Implement ingestion using the CDC processing guidance.
See the Change Data Capture (CDC) page in this section for operational details, including operation precedence and row ordering requirements.

