Import and Export > Available Export & Backup Options

At DatoCMS, ensuring the security and integrity of your data is our top priority. Our ISO 27001 certification guarantees that our architecture is designed with internal backups, providing a reliable safeguard against data loss. In other words, you can rest assured that we follow best practices to keep your data safe.

However, data security is a complex and multifaceted issue. That’s why having a clear, precise, and reliable plan is essential to protect against potential risks, including human errors at any level.

To help you navigate this, we’ve broken down different approaches depending on your specific needs:

You trust DatoCMS but need backup solutions to recover from human errors on your end

For this scenario, DatoCMS provides a powerful feature: environments. Environments allow you to create complete copies of your project’s data, which can be instantly promoted to replace your primary environment in case of accidental data loss.

Additionally, plugins like are available that let you automate periodic backups of your primary environment, ensuring you always have a rolling backup in place.

Another common cause of human error is unintentionally deleting records, and the can assist you in managing that as well.

You want to ensure protection against potential data loss on DatoCMS’s end

While our infrastructure is designed to prevent data loss, we understand that you may still want an extra layer of protection.

The first key assurance is that all content within DatoCMS is accessible through APIs, allowing you to generate offline backups and store them outside our architecture.

To facilitate this, you have multiple options:

• Use existing plugins from the DatoCMS Marketplace designed for exporting your data or managing offline backups/restore functionality, like or .

• Enterprise customers can access a periodic export feature managed by DatoCMS, which automatically exports project data to an external cloud provider storage.

If existing plugins are not enough for you, and you're not an Enterprise customer, you can also create custom scripts tailored to your specific backup needs using our APIs.

A template for a custom export script

Exporting your DatoCMS data or making offline backups is easy with our Content Management API. Here's a quick example script that dumps every record into a records.json file:

1
import { buildClient } from '@datocms/cma-client-node';
2
import fs from 'fs/promises';
3

4
async function main() {
5
  const client = buildClient({
6
    apiToken: 'YOUR-FULL-ACCESS-API-KEY',
7
    environment: 'YOUR-ENVIRONMENT-NAME',
8
  });
9

10
  const itemTypes = await client.itemTypes.list();
11
  const models = itemTypes.filter((itemType) => !itemType.modular_block);
12
  const modelIds = models.map((model) => model.id);
13

14
  const records = [];
15

16
  for await (const record of client.items.listPagedIterator({
17
    nested: true,
18
    filter: { type: modelIds.join(',') },
19
  })) {
20
    records.push(record);
21
  }
22

23
  const jsonContent = JSON.stringify(records, null, 2);
24

25
  await fs.writeFile('backupProduction.json', jsonContent, 'utf8');
26
}
27

28
main();

And here is a simple script that exports all assets, and downloads them locally:

1
import { buildClient } from '@datocms/cma-client-node';
2
import fetch from 'node-fetch';
3
import { writeFile } from 'fs/promises';
4

5
async function downloadImage(url) {
6
  const response = await fetch(url);
7
  const buffer = await response.buffer();
8
  const fileName = new URL(url).pathname.split('/').pop();
9
  await writeFile('./' + fileName, buffer);
10
}
11

12
async function main() {
13
  const client = buildClient({
14
   apiToken: 'YOUR-FULL-ACCESS-API-KEY',
15
   environment: 'YOUR-ENVIRONMENT-NAME',
16
  });
17

18
  const site = await client.site.find();
19

20
  for await (const upload of client.uploads.listPagedIterator()) {
21
    const imageUrl = 'https://' + site.imgix_host + upload.path;
22
    console.log(`Downloading ${imageUrl}...`);
23
    downloadImage(imageUrl);
24
  }
25
}
26

27
main();

You can then add this script into a cron-job and store the result in a S3 bucket, upload it to another system, or back up the results locally.

Recap

Here's a structured comparison table summarizing the key aspects of the two backup scenarios: