Exports, backups, and history

Choose the right export

Use a CSV export when you need tabular records for review or further analysis. Use a company JSON backup when you need data that can be imported back into Cap Table.

Cap table CSV

An export of the ownership view. Check the as-of date and ownership basis before exporting.

Stakeholder statement

A holder-specific view of securities and ownership that can be printed, saved as PDF through the print dialog, or exported to CSV.

Report CSV

The output of a selected report with its reporting period and assumptions.

Company JSON backup

A company data export intended for backup and re-import into the app.

Save a company backup

In Settings, use the company export action to download a JSON backup. Check the selected company before exporting. Keep the downloaded file somewhere you can retrieve independently of the working cap table.

Before a significant import or restructuring, save a fresh backup and record what it represents. A descriptive filename or accompanying note can identify the company and the point in time.

Document attachments are stored as separate files in Puter. Do not treat a JSON export as a downloadable archive of every attachment; retain supporting documents separately.

Understand restore points

The app takes restore points before operations such as a round close, stock split, import, or wipe when there is prior data to preserve. Settings lists the available points.

A restore point describes an earlier company state. Restoring it changes the working records, so review the point and the confirmation before proceeding. A first import into an empty company may not have an earlier dataset to restore.

A CSV report and a restore point serve different purposes. The report is a readable output; the restore point is used to recover an earlier working state. Follow Restore company data for replacement, new-company import, retention, and verification steps.

Read the permanent history

History records business transactions with their actor, recording time, effective dates where applicable, and before-and-after records. Use its filters to find changes. History exports to JSON or CSV include the entire trail regardless of those filters. See Filter and inspect transaction history for date ranges, pagination, original values, and outcomes.

Earlier events remain when you import, undo, wipe, or restore data. If the app starts tracking an existing company without its earlier transaction trail, the initial baseline explicitly identifies that earlier history as incomplete.

The recording date tells you when an action was entered. An effective date describes when the underlying event applies. The dates can differ, especially when adding a historical issuance or correction.

Respond to save and recovery messages

Keep an eye on the app’s save and connection messages. If another tab or device changes the same company and a save is refused, reload to pick up the newer records before continuing.

If the app reports an unfinished change, follow the recovery message and its retry action. A failed cloud save is not confirmed simply because an earlier screen showed the values.

The History view and backups help with review and recovery, but they do not replace the underlying company approvals and agreements.