Backup and restore

Purpose

Under Setup & Configuration → section License & advanced, administrators download a backup of the app data as a JSON file and restore from it when needed.

Who can do this

Jira administrators only.

What the backup contains — and what it does not

• App configuration: language, project type, ISMS roles, onboarding, automation and notification settings, measure-review configuration, document-control mail settings, BSI selection, custom field options.
• App content & logs: document control (controlled pages, rounds, tasks, audit log, issue links), risk trend history and report log.

Steps: creating a backup

1. Open the App data backup card and click Download backup (JSON).
2. The card shows progress during the export (“Exporting … records”). The result is a file isms-toolkit-backup-YYYY-MM-DD.json.

Steps: restoring

1. In the Restore (import) card, click Choose backup file… and select the file.
2. The app validates the file and shows a preview of what would be applied — nothing is written yet. Select App configuration and/or App content & logs (document control, histories) separately.
3. Click Restore and confirm: “Restore? Existing app configuration and same-named content will be overwritten. Jira issues and Confluence pages stay untouched.”

Rules and limits

• Restore content only on the same site: the records reference your Confluence pages, Jira issues and accounts. If the file comes from a different site, the import warns (“The backup comes from a different site … Recommendation: restore the configuration only.”) and unchecks the content box.
• The language is never switched automatically — that is the language switcher’s job (Switching the app language); the project type is immutable after installation (the preview points this out).
• Older backups (format v1) contain configuration only.
• No import is possible while an installation job is running.

Related pages

• Privacy and data erasure
• Ongoing configuration and maintenance