Exporting your account data — Help

1pm gives you a one-click export of everything in your account: every event and run of show, every contact, lead, quote, invoice, menu, task and appointment, every request and response, every uploaded file, every branding theme. The output is a ZIP, and you can grab it any time, as often as you like.

This article covers what's in the export, what's deliberately not in it, when venues reach for it, and a few practical notes on size and timing.

Why an export exists

Three reasons we offer this.

A personal backup. If your account ever gets locked out or you accidentally delete the wrong event, you've got a copy of the data sitting on your own machine.
A handover. If you're moving an event to a different system, or handing the file across to a venue or client who wants their own copy of the run sheet, the export gives them something they can open without a 1pm login.
A record before you leave. If you're cancelling or deleting your 1pm account, the export is the cleanest way to keep what you built before the data goes. Deletion has a 48-hour grace window (you can sign back in and cancel during it), but once that runs out it's permanent (see the Deleting your 1pm account article), so the export is a good last step before clicking the destructive button.

Whatever the reason, the export is yours: there is no charge, no quota, no waiting list.

Where to find it

Sign in and open Account from the top navigation (the Billing page). Scroll to the Account section and click Export my data. You'll land on a page describing what's inside and a Download my data button.

You can also reach it directly at 1pm.app/Account/Export if you've bookmarked that URL.

Clicking Download my data doesn't start the download straight away. A short confirmation opens first, asking you to tick that you understand it's on you to open the ZIP afterwards and check your events, crew and files are all in it. The Download button in that box stays disabled until you do. It's a deliberate speed bump: a download that dies halfway looks much like one that worked, and the person most likely to be hurt by that is the one exporting before they delete the account.

One restriction worth knowing if you share your account: the export is blocked while a collaborator is switched into your account. Handing over the entire account in a single file is the owner's call, so a collaborator going to the URL gets a refusal rather than the page.

What's inside the ZIP

The file you download is a single .zip with this layout:

data/: one CSV file per kind of record on your account, named after what it holds. events.csv, timeline_items.csv, vendors.csv, invoices.csv, menus.csv, tasks.csv, appointments.csv, and so on. Open any of them in Excel, Numbers, Google Sheets, or a text editor.
files/: the raw bytes of every file you uploaded, sorted into folders. uploads/ for files attached to an event or a run of show item, library/ for your file library, spaces/ for files pinned to a Space, enquiries/ for attachments on enquiry messages, branding/ for your logos, and selfies/ for crew photos.
profile.json: your account email and account id.
manifest.json: when the export was generated, and which version of the format it uses.
README.txt: a short guide to which file maps to what.

Every row carries an id column, and records that belong to another record carry that record's id. Rows in timeline_items.csv have an event_id matching a row in events.csv. Rows in invoice_line_items.csv have an invoice_id. Files under files/ are named with the id of the row they belong to, so you can match a PDF back to the event it was attached to.

This is the same idea as a spreadsheet workbook with a tab per topic, just as separate files. If you only care about one thing (say, a list of every invoice you've raised), open that one CSV and ignore the rest. Dates and times are UTC in ISO-8601 format, which every spreadsheet tool understands.

A note on quotes and confirmations: 1pm stores invoices, quotes, pricing documents, confirmations and credit notes as one kind of record, so they all live in invoices.csv together. The doc_type column tells you which is which.

Half-written work comes out too. Unsent draft replies on your leads, and the files staged against them, are in the export alongside the messages that were actually sent. They are working state rather than a record, but they are your words on your own leads, so the export takes the lot. On a shared account you get every collaborator's drafts on your leads, not only your own.

What is deliberately not in the export

Crew-uploaded files.

If your crew uploaded documents in response to your requests (insurance certificates, identification, signed waivers, supplier licenses), those files are not in the main export. The request they answered is recorded in event_requests.csv, but the uploaded files themselves, both the bytes and their file details, are left out.

This is a privacy decision rather than a technical one. Crew uploaded those documents to a specific event under a specific planner, and shipping their files into a generic backup ZIP that could move anywhere isn't what they signed up for when they uploaded. The requests themselves, and the text and choice answers crew gave, are in the export: it's the files that are held back. If you need the crew-uploaded files (for example, because you're audited and need to keep proof on file), use the Download submitted files button on the same Export page. It opens a short note asking you to email [email protected] from your registered address. A real person handles it manually, and the files come back as a separate package.

There is a longer-term plan to make crew-uploads-export self-service with appropriate guard rails (password re-entry, a privacy acknowledgement, a notification to the crew members involved). For now it's a manual ask.

Captured signatures.

Where someone has signed off a terms request, the acceptance record itself exports: who signed, when, which version of the terms they were shown, and the audit columns behind it. The drawn signature image does not, for the same reason as the crew uploads above. If you need the image as part of an audit pack, ask for it alongside the uploads.

Share links, booking links, and calendar feed URLs.

The export does not include the secret tokens that make these links work. A share link is a credential, not a piece of data: anyone holding one can open what it points at, so putting them into a ZIP that might end up on a shared drive or in an email would quietly hand out access. The same goes for public booking links and for the subscription URL of any external calendar you've connected.

You still get the surrounding record, so you can see that a crew member had a link and when it was sent. Tokens live only inside the running app, and you can rotate them any time from the planner. If you want a URL itself, copy it out of the planner's Share accordion; if a share link is in the wild and you need it killed, use Revoke link inside the event.

Payment credentials.

Card details are held by our payment provider and never by us, so they cannot be in the export. Where a contact has a card on file you'll see that fact, along with the card brand, last four digits and expiry that 1pm shows you in the app, but nothing that could be used to charge it.

Stripe billing data.

Your 1pm subscription invoices and receipts live in Stripe's customer portal rather than in the export. Open the Billing page and click Manage subscription to land in the Stripe portal, where they're downloadable as PDFs. (Invoices you raise to your clients are a different thing, and those are in the export, in invoices.csv.)

How big the file is

A new account with a handful of events and a couple of crew is well under a megabyte. The size scales with how many file attachments you have. A venue running thirty events a year with three or four briefing PDFs each will see a ZIP in the tens of megabytes. A studio with a hundred events and heavy floor-plan attachments could see hundreds of megabytes.

The download streams as it's built, so the browser shows a download starting almost immediately. For very large accounts, the streaming can take a minute or so as 1pm walks every event, pulls every file out of storage, and writes them into the ZIP. Keep the tab open until the download finishes, as closing the tab cancels the stream.

If a download fails partway through (a flaky network, your laptop sleeps), just start it again. The export is built fresh each time, so a partial download from earlier is harmless.

When venues reach for this

A few common situations:

Year-end record-keeping. Pull an export at the end of December and tuck it into your archive folder for the year. Reduces the "what was on the schedule for that wedding in March" anxiety later.
Before a big software change. Whenever 1pm is about to push a feature you don't fully trust yet, or whenever you're about to do something destructive in your own account (rebuilding the crew list, mass-deleting old events), pull an export first.
Sharing a frozen copy. If a venue wants the run sheet permanently archived on their side, send them the relevant rows from the export. Filter events.csv and timeline_items.csv to the event in question, and they have a spreadsheet with the briefing fields and the timeline items in order.
Switching systems. If you're trying another tool and want to bring your data with you, the export gives the other tool's import everything it would need. None of them have a direct 1pm importer today, so this involves manual mapping, but at least the source data is in front of you.
Before deleting the account. Always pull an export before clicking Delete account. After the 48-hour grace window runs out, the data is gone for good.

Privacy and storage of the file

Once you download the ZIP, it's on your machine: not on a 1pm server, not in a third-party cloud, not in anyone's email inbox unless you put it there. Treat it accordingly. It contains client contact details, supplier contact details, briefing notes, and any files you uploaded.

Common-sense bits:

If you keep the ZIP in cloud sync (Dropbox, Google Drive, OneDrive), the sync provider holds a copy. That's usually fine but worth knowing if your data agreement with clients has anything to say about it.
If you email the file to a colleague, every email server on the path holds a copy. For larger transfers a shared drive link is cleaner than an email attachment.
If you stop needing the export (because you've already imported it into the next system, or you've pulled a fresher one), deleting the old ZIP is sensible hygiene.

If you want a fresh export instead of trusting an older one, just go back to Account, Export my data, Download my data. There's no rate limit and no reason not to grab a new one.