Secrets ManagerImport & Export

Import Data

Import data to Secrets Manager for easy migration from another organization or secrets management solution. Secrets Manager supports direct import of both secrets and projects. Machine accounts and access tokens cannot be imported.

Condition an import file

Secrets Manager currently supports direct import of secrets and project as a .json file. Your import file should be conditioned according to the following schema and rules:

Even if you're only importing secrets, you must include a "projects" : object containing an empty array, for example:

Bash
{
  "projects": [],
  "secrets": [
    {
      "key": "Secret for Import 1",
      "value": "this-is-my-value",
      "note": "These are some notes.",
      "id": "00000000-0000-0000-0000-000000000001",
      "projectIds": []
    },
    {
      "key": "Secret for Import 2",
      "value": "this-is-my-value",
      "note": "These are some notes.",
      "id": "00000000-0000-0000-0000-000000000002",
      "projectIds": []
    }
  ]
}

For now, each secret can only be associated with a single project.

All objects must have a non-empty "id": "" attribute that matches an expected format. We recommend using "00000000-0000-0000-0000-000000000001" for the first object and incrementing with each subsequent object. On import, new randomly generated identifiers will be generated for each object:

Bash
{
  "projects": [
    {
      "id": "00000000-0000-0000-0000-000000000001",
      "name": "New Project"
    },
    {
      "id": "00000000-0000-0000-0000-000000000002",
      "name": "Second New Project"
    }
  ],
  "secrets": [
    {
      "key": "Secret for Import",
      "value": "this-is-my-value",
      "note": "These are some notes.",
      "id": "00000000-0000-0000-0000-000000000003",
      "projectIds": []
    },
    {
      "key": "Second Secret for Import 2",
      "value": "this-is-my-value",
      "note": "These are some notes.",
      "id": "00000000-0000-0000-0000-000000000004",
      "projectIds": []
    }
  ]
}

You can use the "projectIds": "" attributes to associate imported secrets with a newly imported project:

Bash
{
  "projects": [
    {
      "id": "00000000-0000-0000-0000-000000000001",
      "name": "New Project"
    }
  ],
  "secrets": [
    {
      "key": "New Secret",
      "value": "this-is-my-value",
      "note": "This secret will go in the new project.",
      "id": "00000000-0000-0000-0000-000000000003",
      "projectIds": [
        "00000000-0000-0000-0000-000000000001"
      ]
    }
  ]
}

Import to Secrets Manager

To import your .json file to Secrets Manager:

note

To import to Secrets Manager, your user account must be an owner or admin within the organization.

Select Settings → Import data from the left-hand navigation:
Import data
Select Choose File and choose a .json file for import, or Copy & paste import contents into the input box.
Select the Import data button. When prompted, enter your master password.

warning

Importing does not check whether objects in the file to import already exist in Secrets Manager. If you import multiple files or import files with objects already in Secrets Manager, this will create duplicates.

Suggest changes to this page

How can we improve this page for you?
For technical, billing, and product questions, please contact support

Cloud Status

Check status