Procedures for exporting content
A. Information on exporting content
Contentful’s procedures for exporting your data and digital assets are as follows:
As an API first platform, the primary procedure that Contentful makes available for exporting your content is via APIs, which is achieved by implementing code to call the API for various resource types and individual instances of resources. The data structures and data formats in which your content is made available for export via APIs are set out in the Documentation linked in section B below.
Contentful also makes available a CLI tool which provides additional porting functionality for certain data as set out in section B below. The data structures and data formats available for exporting your content via the CLI tool are available here.
The parameters and technical limits associated with the exporting mechanisms are as follows:
For export via API, the parameters and technical limits can be found here.
NOTE: Contentful provides multiple distinct APIs, all available from the linked URL, with more specific detail for each category of data as set out in the linked URLs in section B below.
For the CLI, the parameters and technical limits are available under the Tips and limitations section.
B. Exportable content
An exhaustive specification of all categories of exportable content that can be ported via API (or an alternative method where noted) are set out in the table below. Note that those data categories that are also exportable via Contentful’s CLI tool are marked with an asterisk (*).
| Data category | Description / Notes | Link(s) to developer documentation |
| Entries* | Entries are text content. | Entries |
| Assets* | Images or files. Includes embargoed assets. | Assets |
| Studio Experiences | Experiences and design patterns are stored as entries with a system annotation.Design components are stored in customer code bases and only referenced from experiences. | - Experience entry annotation details- Entries- Design components details |
| Comments | Comments are tied to Entries. | Comments |
| Content model* | Composed of templates and content types. | - Templates- Content types |
| Scheduled actions | Scheduled Actions | |
| Bulk Actions | Bulk Actions | |
| Tasks | Tasks are tied to Entries. | Entry tasks |
| Tags* | Tags | |
| Taxonomy | Taxonomy | |
| Locales* | Locales | |
| Releases | Releases | |
| Workflows | Workflows | |
| AI Actions | AI Actions | |
| Snapshots | Snapshots | |
| Webhooks* | Webhooks | |
| Webhook signing secret | Webhook signing secret | |
| Resource Provider | Resource Provider | |
| Resource Type | Resource Type | |
| Users | Composed of users’ name, email, and avatar image. | Users |
| Teams | Teams | |
| Roles* | Roles | |
| Spaces | Spaces | |
| Organizations | Organizations | |
| Memberships | Composed of Spaces, Organizations, and Team memberships. | - Space Memberships- Organization Memberships- Team Memberships |
| App Bundles | App Bundles | |
| App definitions | App definitions | |
| App installations | App installations | |
| App Actions | App Actions | |
| App keys | App keys | |
| App signing secrets | App signing secrets | |
| App Functions | App Functions | |
| Audit Logs | These are exportable via UI Config. | Audit Logs |
In accordance with the EU Data Act, Contentful does not make available for export the following categories of data that are specific to the internal functioning of Contentful’s subscription services: GQL Schema Registry; Vectorized content; Live preview variable; App Action Calls; Organization / space record; SSO configuration; 2FA configuration; OAuth token; Personal and API tokens; and Audit log configuration.