S3 export pipeline
ZTZenoti Docs Team Updated April 10, 2026 2 min readGuide
The S3 export pipeline is the final stage of the Analytics β Amazon S3 data pipeline. It converts processed data from the data warehouse into CSV files and places them in your S3 bucket.
Before you begin
- Your organization must have an active Analytics β Amazon S3 subscription.
- The initial S3 Data Share configuration must be completed by your Zenoti Implementation team.
- Your S3 bucket must be configured with the appropriate access permissions.
Steps
Understand the export process
The S3 export pipeline runs automatically as part of each data refresh cycle:
- The system reads processed data from the data warehouse.
- Data is converted to CSV format (UTF-8 encoded, comma-delimited, no column headers).
- Files are split by your subscription scope:
- Organization-level β All data in a single S3 bucket.
- Zone-level β Separate buckets for each zone.
- Center-level β Individual buckets per center.
- CSV files are placed in your S3 bucket following the folder structure:
Root/PODName/GroupID/table_name/logid/filename.csv.
Monitor export completion
- The system creates a temporary processing folder during export:
<groupid_processing>. - CSV files are generated for each table within the GroupID folder.
- Upon successful completion, the folder is renamed from
<groupid_processing>to the final<groupid>. - Large tables may be split into multiple CSV files:
Data0.csv,Data1.csv, etc.
Access schema information
The system generates schema files in your S3 bucket:
- SchemaFull folder β Complete schema files for all available tables. Use these during initial setup to create matching table structures in your data warehouse.
- SchemaUpgrade folder β Schema changes for new releases. Check this folder after Zenoti platform updates and apply changes before loading new data.
Schema files use .txt format and define column names, data types, and column order for each table.
Understand organization-level data replication
For center-level or zone-level subscriptions, organization-level dimension tables are automatically replicated across all buckets. These include:
Bi_DimAgentβ Agent reference data.Bi_DimCampaignβ Campaign definitions.Bi_DimCategoryProductsβ Product category mappings.Bi_DimCategoryServicesβ Service category mappings.Bi_DimCustomFormsβ Custom form definitions.Bi_DimDiscountβ Discount definitions.Bi_DimDonationsβ Donation type definitions.
This replication ensures that center- and zone-level data can be correctly joined to org-level reference records.
Tips
- Monitor folder naming β Processing folders indicate active exports. Completed exports use numeric GroupID folders.
- Plan for file splitting β Large tables may generate multiple CSV files. Your BI tool should handle file concatenation.
- Use incremental GroupIDs β Each data refresh creates a new GroupID. Use the highest GroupID for the most current data.
- Use schema files β Execute SchemaFull scripts in your data warehouse to create proper table structures before loading data.
Was this article helpful?
Your feedback helps us improve our documentation.