ComposableStack.AI CDP
Back to agent
Constraintconstraint.aep-batch-file-max-records-5m

AEP Batch Destination Export File — 5 Million Record Limit (System-Enforced)

Adobe Experience Platform enforces a system limit of 5 million records per exported file for batch (file-based) destinations, including cloud-storage destinations (Amazon S3, Azure Blob, Google Cloud Storage, SFTP) and any file-based batch destination. Exports of audiences exceeding 5 million records must be split across multiple files or multiple export jobs. For enterprise and healthcare organizations with large activated segments, this limit dictates file-partitioning strategy and downstream ingestion tooling requirements at the receiving platform.

confidence 85%v1reviewed May 28, 2026aep, batch, destinations, file-export, system-limit, records, cloud-storage, partitioning

AEP Batch Destination Export File — 5 Million Record Limit (System-Enforced)

What it is. Adobe Experience Platform enforces a hard system limit of 5 million records per exported file for batch (file-based) destinations. Unlike performance guardrails, AEP will not write more than 5 million records into a single output file — exports exceeding this size must be partitioned across multiple files automatically or via split export jobs.

Scope. Applies to all file-based batch destinations: Amazon S3, Azure Blob Storage, Google Cloud Storage, SFTP, and any other cloud-storage destination type in the AEP Destinations Catalog.

Architectural implication. For most mid-market activations (audiences of 100K–2M profiles), this limit is not binding. For enterprise organizations with large or merged audiences — national retail, financial services, healthcare with deduplicated patient lists — audiences can exceed 5 million records. These organizations must design their export configuration to accommodate multi-file partitioning and ensure that downstream ingestion tools (Snowflake COPY INTO, Fivetran, custom ETL) can handle split-file ingest from a single audience export.

Where the agent should surface this. When a user describes exporting large batch audiences (e.g., "we have a full 8-million-member loyalty program audience we want to export to S3"), note the 5-million-record-per-file system limit and confirm the downstream ingestion pipeline handles multi-file audience exports.

Sources

Related

← Referenced by

  • governed-byarchetype.aep-heavy-enterprise-evaluating-composable— OC-079. Enterprise organizations in this archetype (>500K profiles, often >5M at large enterprise scale) regularly export large audiences to file-based batch destinations (S3, Azure Blob, GCS). The 5M-record-per-file system limit requires deliberate file-partitioning strategy and downstream ingestion pipeline design — a planning constraint architects in this archetype profile encounter during activation stack design.