What format do exports use?

A ZIP archive containing one CSV per selected object. Filenames use API names. Encoding is selectable — UTF-8 with BOM is the default for Excel compatibility.

How long can I download an export?

48 hours after the job completes. A permanent log records what was exported, when, and record counts per object.

Are attachments included?

Not in v1. Exports cover record field data only. Attachments remain in the workspace storage layer.

Workspace owners and admins from Setup → Data export. Members work with records in Operations, Views, and forms; bulk export is an admin capability.

On-demand CSV backups and scheduled exports

Workspace admins export selected CRM objects to CSV files packaged in a ZIP — on demand or on a recurring schedule. System and custom fields are included; download within 48 hours when the job completes.

ZIP

One file per object

API names as filenames

48h

Download window

After job completes

UTF-8

Excel-ready default

BOM encoding selectable

Backup without click-through

ZIP of CSVs — on demand or scheduled.

Backups, audits, and handoffs to spreadsheets should not require clicking through every object manually. Data export produces one CSV per object with API names as filenames and encoding options that open cleanly in Excel.

Pair export with import for round-trip migration workflows. Scheduled exports keep leadership or compliance teams on a rhythm without remembering to click Run.

ZIP of CSV files
One file per object. System fields (id, timestamps, authors) plus all custom fields. UTF-8 with BOM default for Excel.
On-demand or scheduled
Run a one-off export or configure a recurring schedule. Email and in-app notification when jobs finish.
Permanent export log
Record of what was exported, when, and counts per object. Download links available for 48 hours.

Use cases

When teams reach for export

Periodic backup, migration to another system, or point-in-time audit of record counts.

Select all objects or a subset before running
Choose ZIP encoding for your downstream tools
Attachments are not included in v1 — data only

Format

Output your analysts expect

CSV structure mirrors workspace fields so re-import or spreadsheet work stays straightforward.

Filenames use object API names
Custom fields export alongside system columns
UTF-8 with BOM opens correctly in Excel by default

Schedule

Scheduled exports for recurring needs

Configure cadence so backups or reporting extracts happen without manual triggers.

Add or edit schedules from Setup → Data export
Notifications when each scheduled run completes
Same object selection and encoding per schedule

Delivery

After the job completes

Download from Setup, act on the notification, or rely on the export history log.

Download window is 48 hours from completion
Permanent log shows objects, counts, and timestamps
Re-run when you need a fresher snapshot

Stack

Complements import and Operations

Export for bulk exit; import for bulk entry; Operations for day-to-day deltas.

Round-trip migrations use export then import mapping
Live Views replace weekly CSV rituals for internal reviews
API keys available when jobs need programmatic access

Questions

Short answers before you request access.

What format do exports use?: A ZIP archive containing one CSV per selected object. Filenames use API names. Encoding is selectable — UTF-8 with BOM is the default for Excel compatibility.
How long can I download an export?: 48 hours after the job completes. A permanent log records what was exported, when, and record counts per object.
Are attachments included?: Not in v1. Exports cover record field data only. Attachments remain in the workspace storage layer.
Who can run exports?: Workspace owners and admins from Setup → Data export. Members work with records in Operations, Views, and forms; bulk export is an admin capability.