ChatGPT Business workspace owners need a complete machine-readable data export
Summary
ChatGPT Business workspace owners currently lack a self-service way to export the workspace's complete conversation and project data, even though personal ChatGPT accounts provide Settings → Data controls → Export data.
This creates a serious data-portability and business-continuity gap. A paid Business workspace should not provide weaker retrieval and backup capabilities than a personal account.
Current behavior
For personal Free, Plus, and Pro accounts, a user can request an account export that generally includes files such as:
chat.htmlconversations.json- other account and configuration data
In a ChatGPT Business workspace, the Export data control is unavailable. The Privacy Portal's consumer-account flow does not provide a clear solution for conversations and files stored only in the Business workspace.
The guidance to direct business-data requests to the organization is circular when the requester is the workspace owner or administrator.
Why this matters
Business users rely on ChatGPT as a long-lived knowledge and work system. Workspace data can include:
- conversations and complete message trees
- Projects and project membership
- uploaded source files
- generated artifacts
- conversation and file metadata
- workspace instructions and configuration
- memories or equivalent workspace-scoped retained context
- GPT configuration and associated knowledge files, where applicable
Without a supported export, the workspace becomes effectively one-way. This prevents reliable:
- backup and disaster recovery
- business continuity planning
- records retention and audit workflows
- e-discovery and compliance workflows
- migration between accounts or workspace types
- independent search and archival
- preservation before subscription, ownership, or product changes
Requested capability
Please provide a workspace-owner/admin export that produces a complete, machine-readable archive of the Business workspace.
At minimum, the export should include:
- All conversations, including branches and complete message content.
- Project structure and conversation-to-project relationships.
- Uploaded and generated files, with stable identifiers and checksums.
- Timestamps, authorship, model metadata, citations, and relevant provenance.
- Workspace instructions, GPT definitions, and associated knowledge files where permitted.
- A manifest describing archive structure, omissions, and schema version.
- JSON or another documented structured format in addition to a readable HTML representation.
The export should be available through either:
- Workspace settings → Data controls → Export workspace data, or
- a documented admin API.
Expected behavior
A verified Business workspace owner or administrator should be able to request and download the organization's complete workspace archive without having to manually open and copy individual chats.
The export process may require elevated verification, audit logging, and owner-only permissions, but the capability itself should exist.
Related issues reviewed
I found related requests for importing or exporting ChatGPT chats into Codex, including #30636 and #25387, but those focus on transferring ChatGPT context into Codex. They do not address the broader missing capability: a complete owner-controlled export of a ChatGPT Business workspace for backup, portability, and continuity.
Additional context
This is especially important as ChatGPT and Codex desktop experiences become more unified. Users should not have to choose between organizational controls and basic ownership of a recoverable copy of their own business data.
1 Comment
Follow-up proposal: Export Integrity Report
After thinking more about this request, I believe there is an opportunity to make the export significantly more valuable for Business customers by including a verifiable integrity report.
For enterprise use, an export is not only about obtaining data—it is also about demonstrating that the exported archive is complete, internally consistent, and recoverable.
I propose that every Business workspace export include an integrity manifest containing information such as:
This would provide administrators with confidence that:
Long-lived Business workspaces increasingly function as organizational knowledge repositories rather than transient chat histories. A verifiable export would therefore serve not only portability, but also governance, auditability, records retention, and business continuity.
In my view, the ideal outcome is not simply "Export my workspace," but "Export my workspace together with sufficient evidence that the export is complete, internally consistent, and recoverable."