Backup

In this article:

Overview

A backup is simply a copy of your KanBo data—this includes your workspaces, spaces, cards, and configurations. It’s a safety net in case of:

  • Accidental deletion or data loss

  • System failures, outages, or corruption

  • Software updates or migration risks

  • Compliance and governance requirements for data retention and recovery

Always back up data before updates or configuration changes.

Having regular backups ensures business continuity—with the ability to restore your platform quickly, avoid downtime, and maintain data integrity.

A KanBo backup includes cards, spaces, workspaces, activity stream, and information about attached documents. Please note that documents attached to cards are not stored in KanBo. Instead, they are links to their locations on external platforms or servers.

The KanBo backup only contains information about attachments, not the attachments themselves.

Detailed instructions

For more detailed technical guidance, KanBo provides a dedicated DevOps Help section within its Help Portal. This is the best place to find instructions related to backup, deployment, and maintenance workflows.

The exact steps for creating a backup in KanBo depend on your deployment model. In other words, it depends on whether your organization is running KanBo in the cloud or on-premises.

Both articles explain the backup and update processes, highlighting the importance of performing a full database backup before making any changes.

Was this article helpful?

Please, contact us if you have any additional questions.