Commvault protects monday.com Work OS data including all workspaces, folders, boards, columns, groups, items with all column values, subitems, update threads with replies and attribution, and file attachments. The solution also backs up account-wide users and teams to support people remapping on restore.
What's supported
monday.com requirements
To back up and restore monday.com data, your account must meet the following requirements:
-
monday.com account plan that supports API access. Free plans may have limited API access.
-
Personal API Token with the required scopes. For details, see Configure permissions for monday.com protection.
-
API version 2026-4 or later. Commvault uses API version 2026-4 pinned via the API-Version header.
For more information, see the monday.com API documentation.
Supported resources and data
Commvault backs up the following monday.com resources:
-
Account-wide metadata: Users and teams (backed up for remapping during restore; not created on restore)
-
Workspaces: Workspace name, kind (open, closed, or private), and description
-
Folders: Folder name and parent chain (supports nested folder structures)
-
Boards: All board contents including columns with status and dropdown label settings, groups, items with all column values, subitems, update threads with replies, and file attachments
Backup and restore capabilities
| Capability | Details |
|---|---|
| Backup levels | Full backups only. Incremental backups are not supported. |
| Content scoping | Back up all workspaces, folders, and boards in the account, or scope backup to a specific workspace and all boards within it. |
| Restore destination | Isolated workspace mode only. Commvault creates a fresh workspace and rebuilds all folders and boards inside it. Original data is not modified. |
| People remapping | Users are matched by email and teams are matched by name on the target account. Users and teams are not created during restore. |
Data flow and storage
Commvault uses the monday.com GraphQL API to back up data. The access node makes API calls to monday.com to retrieve workspace metadata, folder structures, board contents, and file attachments, and then writes the data to the backup storage destination.
What isn't supported
The following restore options are not supported:
-
Out-of-place restore to a different monday.com account
-
In-place restore to original workspace IDs
-
Creating users and teams on restore. Users are matched by email and teams are matched by name on the target account.
The following column types and values are not restored:
-
Server-computed column values: formula, progress, auto_number, creation_log, last_updated, item_id, button, subtasks, time_tracking
-
Doc and Workdoc column body content. An empty target doc shell is created so linkage is not lost, but the document body content is not restored.
Limitations
-
Incremental backups not supported: Incremental backups automatically fall back to full backups.
-
Isolated restore only: In-place restore onto original workspace IDs and custom-destination restore into a caller-supplied workspace are not supported.
-
User and team remapping: User and team management is organization-level. After restore, board owners and sharing settings must be reconfigured manually.
-
Cross-board column resolution: board_relation, dependency, and mirror columns that reference boards outside the backup scope are created but left unlinked.
-
User list limitation: The user list is capped at 1000 rows. Large enterprise accounts with more than 1000 users require additional paging.