Skip to main content

Data export

Beech user guide for architecture studios.

Administration

Last updated: 25 Oct 2026

Your data is yours. Admins can download a firm-wide or project-scoped export anytime — open JSON metadata plus original Vault files.

Firm export

Settings → Data & Privacy → Export firm data. Downloads a ZIP containing firm-export.json (schemaVersion 4), Excel status reports, Vault binaries under vault/files/, and vault/manifest.json listing any skipped files.

  • Included — firm profile, users, projects, drawings, tasks, vendors, reviews, sprints, invitations, notifications, Vault folders/files/blobs/links/shares/packages, chat, time logs, and audit log entries.
  • Excluded — password hashes, MFA secrets, OAuth tokens.

Project export

From a project, Admins can download a scoped ZIP (project-export.json + that project's Vault files) via /api/projects/{id}/export — useful for client handoffs.

Scheduled auto-export

Connect Google Drive under Plugins, then enable weekly or monthly auto-export in Data & Privacy. Beech pushes a fresh firm ZIP into a Beech Exports Drive folder.

We commit to at least 60 days' notice before shutdown or major discontinuation, and a 30-day post-cancellation retrieval window.

Before you start

  • You are an Admin with access to Firm settings and Data & Privacy controls.
  • You know whether you need a firm-wide archive or a project-limited handover package.

Workflow checks and quality guardrails

  • Checklist item 1: Record the export reason and date so compliance reviews can trace why and when the archive was generated.

  • Checklist item 2: After download, verify JSON, Excel, and Vault file folders are present before sharing the package onward.

Common mistakes to avoid

  • Assuming password hashes or OAuth secrets are part of the export. They are intentionally excluded.
  • Generating exports without documenting who requested them and what scope was approved.

Troubleshooting

  1. 1
    Troubleshooting step 1

    If large Vault exports take longer, wait for completion and avoid repeated trigger attempts that create duplicate archives.

  2. 2
    Troubleshooting step 2

    If recipients cannot locate specific files, confirm they were stored in Vault and not only referenced in Studio links.

What to do next

  1. Open /docs/security and continue with the next workflow.
  2. Open /docs/vault and continue with the next workflow.
  3. Open /docs/deliverables and continue with the next workflow.

Related reading: Guides and Blog and feature workflows.