Sovrain
  1. Documentation
  2. Your organization

Reference

Export format

The organization export file - name, encryption, structure, what it contains and leaves out, and what an import does.

An export is one file that holds an organization’s data, made and imported on Admin › Backup (/admin/backup). Steps: Back up your organization and Restore or move your organization.

Who

ActionWho
ExportAny owner or administrator, after typing their password again
ImportOwners only, after typing their password and the organization’s address (slug)

What else each role can do: Roles.

File

ItemValue
Nameorg-<slug>-<yyyyMMdd>-<HHmm>.json, time in UTC, for example org-acme-20261117-0930.json
EncryptedEncrypt to an age public key (default): the JSON encrypted with age to an X25519 recipient (age1…, at most 100 characters). The name ends in .json.age.
Not encryptedNo encryption, after ticking the confirmation that the file contains private signing keys and SCIM tokens
FormatJSON, UTF-8
Size for importAt most 50 MB
Rate1 export per organization per 60 seconds; 1 import per 5 minutes

The file contains secrets in clear text inside the JSON: password hashes, SAML and OpenID Connect private signing keys and SCIM tokens. An unencrypted file must be kept as safely as the organization itself.

Structure

The top level is one JSON object:

{
  "format": "idp-org-export",
  "version": 10,
  "exportedBy": "idp 0.1.0",
  "exportedAt": "2026-11-17T09:30:12.512Z",
  "organization": { "name": "Acme", "insertedAt": "…", "updatedAt": "…" },
  "attributeDefinitions": [ ],
  "users": [ ],
  "…": [ ]
}
KeyContent
formatAlways idp-org-export
versionThe bundle version. Current: 10. Import reads versions 1 to 10.
exportedByThe program that made the file
exportedAtWhen
organizationThe organization’s name and dates. The slug and the region are not exported; an import keeps those of the importing organization.
one key per tableA list of rows; see below
vaultAn object with the password manager’s tables and files

Rows refer to each other by natural keys (a user’s public id, a group’s name, an application’s slug), never by internal numbers. Binary values are Base64. Times are kept as stored.

Sections

KeyRows
attributeDefinitionsThe attribute bank
usersAccounts: public id, login, email, password hash, verification, invitation, suspension and removal dates, time zone, locale
userProfilesDisplay, first and last names
userAttributesCustom attribute values
groupsGroups, with the default and two-step flags
groupMembershipsWho is in which group
samlConfigs, samlAcsEndpoints, samlSpCertificates, samlSigningKeys, samlAttributeMappingsSAML setup of each application, signing keys included
oidcSigningKeys, oidcClients, oidcRedirectUris, oidcPostLogoutRedirectUris, oidcClaimMappingsOpenID Connect keys and clients, client secret hashes included
scimConnections, scimMappings, scimScopeGroups, scimScopeUsersSCIM connections, tokens included
applicationsApplications, with launcher URL, status, delegation and two-step flags
applicationGroupAccessGroup access and roles
customDomainsThe custom domain and when it became primary
orgBrandingBranding, icons included
orgAccountRecoveryThe account recovery settings
delegationPolicy, delegationProtectedGroupsThe delegation policy and protected groups
vaultThe password manager: encrypted entries, their versions, sharing, keys and attachment files. Entries stay encrypted.
twoStepPolicyThe two-step sign-in policy

Removed users (admin Remove) are in users, with their removal date.

Not in the export

  • Sessions, authorization codes, refresh tokens and consents.
  • Every second step: authenticator apps, security keys, passkeys and backup codes. After an import, everyone who needs a second step sets one up again.
  • Delegations and their events.
  • Security events, the mail log and application activity.
  • SCIM sync state (what was sent to which application).
  • Admin API grants and device codes.
  • The history of exports and imports.

What an import does

  1. Checks the file: valid JSON, format is idp-org-export, a known version, every property known and of the right type. A problem refuses the whole file with a message.
  2. Builds a complete new database for the organization, under a new organization key.
  3. Replaces the live database in one step. The previous database is kept as a safety copy on the server (one generation).
  4. Replaces the organization’s custom domain entry.
  5. Schedules a full SCIM synchronization.
  6. Signs everyone out, the owner who imported included.

An import replaces all users, groups, attributes, applications, signing keys and custom domains of the organization. It is not a merge.

The Import key shown on the page (valid 24 hours; New key makes another) is the age public key to encrypt a file to when it will be imported into this organization.