Export your data

On the account page, press Export everything. Or call export_account_data from the REST API (POST /api/v1/account/export) or MCP. It is made in the background, which can take a few minutes for a large list, and the links come to the account owner's email. get_account_export answers with the status and, once it's ready, the links.

curl -X POST $FLOCKSTACK_URL/api/v1/account/export \
  -H "Authorization: Bearer $FLOCKSTACK_API_KEY"

The links need no key and work for 7 days; anyone who has one can download your data, so treat it like a password. After that the files are deleted, and a new export makes new ones. One export at a time, and one every 5 minutes. A very large account comes in several ZIP files, each with its own link.

flockstack-export-2026-10-18.zip
├── README.txt
├── manifest.json
├── suppressions.csv
├── contacts/
│   └── field-notes.csv
├── campaigns/
│   └── field-notes/
│       ├── 2026-10-04-how-to-price-a-side-project.md
│       └── 2026-10-04-how-to-price-a-side-project.html
└── images/
    └── cover-1b2c3d4e5f607182.png

Everything is plain text, CSV or the original picture files. Nothing is encrypted or tied to FlockStack.

One CSV per newsletter in contacts/, with every contact whatever its status: active, pending, unsubscribed, bounced, complained and dormant. The columns are email, status, newsletter, source, subscribed_at, confirmed_at, unsubscribed_at, last_sent_at, last_open_at, last_click_at, emails_received, opens, clicks, tags, referrals, referred_by, created_at. Dates are ISO 8601 in UTC; tags are separated by ;; referrals is how many people a contact brought in. The first columns are the ones FlockStack's own CSV import reads, so the file goes back in as it is.

suppressions.csv lists the addresses that bounced, complained or were blocked, with the reason. Keep them off any list you move to.

Every issue and draft is two files in campaigns/<newsletter>/: Markdown and a standalone HTML page, named date-slug. Both start with the same frontmatter, as static site generators read it.

---
title: "How to price a side project"
date: 2026-10-04T08:30:00.000Z
newsletter: "field-notes"
status: "sent"
archive_url: "https://field-notes.example.com/p/how-to-price-a-side-project"
preview_text: "Charge more than feels right."
slug: "how-to-price-a-side-project"
format: "rich"
id: "6650f1c2e9b1d4a012345678"
---

status is draft, scheduled, sending, paused, sent or canceled. archive_url is where the issue is published, when it is. Issues written in Markdown keep their Markdown; the editor's issues are turned into Markdown, and designed HTML issues into their text. The HTML file is the issue as the website shows it. Pictures from your library are in images/, and both files point to them with relative links.

manifest.json lists everything in the export: each newsletter with its settings (sender, welcome and confirmation emails, archive address, feed address, referral rewards), its contact count and file, every issue with its title, date, status and files, every picture with its original address and whether it could be fetched, and each file's size and CRC-32. Its version changes only when the layout does.