Skip to main content

Data Export module

One button, one gzipped JSON snapshot, dropped into the org's own storage bucket — with a short-lived signed download link for analysis, migration, audit, and offboarding.

Optional module Enable in Settings → Modules

Data Export is the org-level snapshot pipeline. It runs as a background job, gathers every row of every org-scoped record, gzips them into a single JSON file, and writes that file to the org's own storage bucket. The org admin gets a download link good for fifteen minutes; the file itself stays in the bucket until the org deletes it.

Who this module is for​

  • Org admins — running the snapshot, downloading it for analysis or migration
  • Platform admins — configuring the platform-level retention policy and the schedule preset
  • Members — different surface: a separate per-user export covers GDPR / CCPA data-subject requests

What gets enabled​

When Data Export is turned on for an org:

  • A Trigger export button appears in org settings under Backups & Export
  • Clicking it starts an async job that writes one gzipped JSON file into the org's own storage bucket
  • An Export History list shows pending, running, completed, and failed runs
  • Download issues a short-lived signed URL — valid for fifteen minutes — pointing at the file in the bucket
  • Only one export can be pending or running at a time per org; concurrent triggers return a "conflict" response

Platform-level configuration decides retention (separate daily / weekly / monthly counts the platform prunes against) and the schedule preset that controls automatic runs — daily at 2 AM, daily at 3 AM, every 12 hours, weekly on Sunday at 2 AM, or disabled. There is no per-org cron picker in the org admin UI today.

What's in the snapshot​

A typical export contains, when the relevant modules are enabled: organization, regions, chapters, memberships, user profiles, custom fields, saved views, member enrichment, Engage forum posts and comments, compliance records, elections and votes, billing and invoices, Foundation funds and donations, Learning courses and enrollments, Alumni profiles and career postings, documents, and the org-scoped audit log slice.

Media files (profile photos, attachments, document binaries) are not copied into the JSON. They already live in the org's storage bucket; copy them directly if you need them.

GDPR / CCPA data export (separate flow)​

A second, per-user export covers privacy-law data-subject requests — initiated by the member from their own privacy settings (or by a platform admin on their behalf), returning a single user's data through a different background job. See the platform admin GDPR data export runbook for the handling guide.

Common workflows​

What's not in this module today​

  • Per-chapter exports. The snapshot is org-wide. No way to scope the JSON to a single chapter.
  • A per-org schedule picker in the UI. Schedules are set centrally at the platform level via the preset selector.
  • A standalone CSV export of the audit log. The audit slice is included in the JSON snapshot; there is no separate audit-only CSV export button.
  • Format or destination choice. Output is always a single gzipped JSON file. No CSV / XLSX option, no "send to a different S3" flow — the file is already in the org's own bucket.

Where to go deeper​

Dependencies​

  • Org storage — the destination bucket for the gzipped JSON
  • Platform backup configuration — must be active and verified before exports can run
  • Operations — billing, compliance, and election data appear in the JSON when Operations is enabled
  • Foundation — donations and donors are included when Foundation is enabled
  • AI Services — exported data can feed external models

Last verified against v0.62.1 (2026-05-11).