Product / Data ownership

Your data, exportable forever.

JSON, CSV, or full SQL dump in one click. The export button lives in your dashboard, visible from day one. No support ticket. No exit fee. No retention period.

Get started Read the export docs

Export is a feature, not a favor.

<60s
Typical export

For organizations under 5,000 members. Larger orgs queue with email link.

3
Formats supported

JSON for developers, CSV for non-developers, SQL for engineering teams.

1-click
In the dashboard

No support ticket. No salesperson call. No retention specialist.

$0
Exit fee

Now and forever. The export is the same on day 1 as on day 1,000.

What you can export

Everything. Specifically:

Members

Every field, every custom property, every tag, every note. Tier history, role assignments, status changes.

Invoices and payments

Stripe IDs included for reconciliation. Refunds, partial payments, dispute records.

Events and RSVPs

Including waitlists, cancellations, ticket types, and per-member event history.

Email history

Every transactional and bulk message. Subject, body, recipients, send time, opens, clicks, bounces.

Audit log

Who did what, when, from where. Tamper-evident hash chain across every record.

Files and attachments

Member uploads, logos, branded assets, receipt PDFs. Delivered as a downloadable archive.

Three formats

Pick the export that matches who reads it.

JSON keeps full relational fidelity for re-import to another system. CSV opens in Excel, Numbers, or Sheets without ceremony. SQL dumps the schema and data ready to restore to your own PostgreSQL.

Same data, three packagings. Use the one your accountant, developer, or board treasurer needs.

  • JSON: nested objects, foreign keys preserved, suitable for migration to another platform.
  • CSV: one file per resource (members.csv, invoices.csv, etc.) with sensible flat schemas.
  • SQL: PostgreSQL schema + data, ready to restore to your own database.
  • Scheduled exports to S3-compatible storage (R2, AWS S3, Backblaze B2) or webhook endpoints.

Lock-in is a business model, not a feature.

Most membership platforms make leaving expensive. We treat your right to leave as the simplest way to keep them honest, and to keep us honest. The export tool ships in the same release as the rest of the dashboard, on day one.

Get started See subprocessors
$ sembr export --format=sql --since=2024-01-01
> resolving relations ............ done
> writing schema ................. done
> writing 12,847 members ......... done
> writing 38,902 invoices ........ done
> archive: workspace-2026-04-12.sql.gz (47MB)
> retention: forever
FAQ

Common questions.

Can we automate the export on a schedule?
Yes. Scheduled exports (daily, weekly, monthly) deliver to S3-compatible storage (R2, AWS S3, Backblaze B2) or to a webhook endpoint. Useful for nightly backups to your own infrastructure.
Does the export include Stripe data?
Stripe IDs are included in the export so you can join against your Stripe dashboard data. Actual Stripe customer/charge objects stay in Stripe; you can pull those via Stripe's own API at any time.
What about email content sent via Sembr?
Every email message body, subject, recipient, send time, open/click events, and bounce/complaint flags are included in the export. Useful for transferring email history into a new platform or for compliance audits.
Is there a public schema reference?
Yes. The PostgreSQL schema is documented in the developer docs, with field-by-field descriptions, foreign-key relationships, and per-tenant isolation notes. The same schema is what you receive in the SQL dump.
Do you sell or share customer data?
No. Sembr makes money from subscription fees, full stop. Your data is not sold, shared with third parties for marketing, used to train AI models, or aggregated for industry reports without explicit opt-in.

Try Sembr knowing you can always leave.

The export button is the first thing you see in Settings.

Get started See pricing