Ask a Question

Importing and Exporting data from Dgraph Cloud

You can export your data from one Dgraph Cloud backend, and then import this data back into another Dgraph instance or Dgraph Cloud Backend.

Exporting Data

You can export your data using JSON format. To do this, call the export mutation on /admin/slash. As an example, if your GraphQL endpoint is at, then the /admin endpoint for the schema is at

Note The /admin/slash endpoint requires Authentication.

The following is an example of a GraphQL mutation to export data to JSON.

mutation {
  export {
    response { code message }

The signedUrls output field contains a list of URLs which can be downloaded. These URLs expire after 48 hours.

Export will usually return 3 files:

  • g01.gql_schema.gz: The GraphQL schema file. This file can be re-imported via the Schema APIs
  • g01.json.gz: the data from your instance, which can be imported via live loader
  • g01.schema.gz: This file is the internal Dgraph schema. If you have set up your backend with a GraphQL schema, then you should be able to ignore this file.

Importing data with Live Loader

It is possible to import data into a Dgraph Cloud backend using live loader. In order to import data, do the following steps:

  1. First import your schema into your Dgraph Cloud backend, using either the Schema API or via the Schema Page.
  2. Log into Dgraph Cloud, and find your backend’s gRPC Endpoint on the Settings page. This will look like
Note The gRPC endpoint URL must have the string .grpc. added after the domain prefix. Without this change, Live Loader will not be able to find the endpoint.
  1. Run the live loader as follows:

    docker run -it --rm -v /path/to/g01.json.gz:/tmp/g01.json.gz dgraph/dgraph:v20.07-slash \
      dgraph live --slash_grpc_endpoint=<grpc-endpoint>:443 -f /tmp/g01.json.gz -t <api-token>
Note Running this via Docker requires you to use an unreleased tag (either master or v20.11-slash).