# Prepare your monday.com environment

Plan how Commvault protects your monday.com data. In most environments, you can start with recommended defaults and adjust only if your environment requires it.

## Start with your monday.com environment

One monday.com configuration protects one monday.com account. If you need to protect multiple monday.com accounts for isolation by region, environment, or business unit, configure a separate monday.com instance for each account.

## Align storage with your monday.com region

Neither the access node nor the backup storage destination has a regional requirement. The access node uses the monday.com GraphQL API to back up data, and API calls are not subject to regional placement constraints.

## Understand backup behavior

Commvault supports full backups only. Incremental backups are on hold because monday.com does not provide a server-side updated_since filter for item lists. Detecting hard-deletes between backups requires a full board traversal regardless, making incremental equivalent to full in API cost. When you run an incremental backup, Commvault automatically falls back to a full backup.

## Decide how to scope your data

You can scope backup content at the workspace level:

- Back up all workspaces, folders, and boards in the account by selecting the root level.

- Scope backup to a specific workspace and all boards within it by selecting a workspace path.

Per-board content scoping is not supported.

## Organize backups logically

Use subclients to organize the backups based on how your organization manages monday.com data. Common approaches include grouping by environment (production, test, or development), business unit or application, or data sensitivity or compliance requirements — whichever helps you apply consistent policies and simplifies monitoring and reporting.

## Plan for performance

Backup and restore performance depends on data size, change rate, and API rate limits. To optimize performance, avoid unnecessary fragmentation of protection scopes, and schedule backups to avoid peak workload periods.

## Confirm permissions early

Make sure the required monday.com permissions are in place before configuring protection. For details, see Configure permissions for monday.com protection.

## Understand key limitations

- Incremental backup is on hold and automatically falls back to full backup.

- Restore is limited to isolated workspace mode. In-place restore and custom-destination restore are not supported.

- Users and teams are matched by email and name on the target account. Users and teams are not created during restore.

- Server-computed column values are not restored.

- Doc and Workdoc column body content is not restored.

- Cross-board columns that reference boards outside the backup scope are created but left unlinked.

- The user list is capped at 1000 rows. Large enterprise accounts with more than 1000 users require additional paging.

For details, see Protect monday.com data.

×

Loading...