ClickUp

What a ClickUp backup contains

Coverage version 2 records the sets below, subject to the connected account's permissions and ClickUp's API. Yes means the restore can recreate supported parts of that set; it does not mean a lossless copy. Read the fidelity table before confirming.

Dataset registry

Restore recreates required Space, folder and list parents in their backed-up hierarchy, including folderless lists. Spaces and folders are restored as parents of selected lists or Docs; they are not separate selection units. Active elements recognized by identity are reused. Members and field definitions support mappings; users and field definitions are not created. Task details include supported checklists and attachments. List comments remain in the download. Additional task list memberships are recorded for context, not recreated.

Coverage and gaps

Open a snapshot's Contents to see each dataset's state, count and any reason it is unavailable. A successful snapshot describes this coverage version, not all ClickUp data. Partial snapshots can still contain usable sets. The restore tree disables selections whose required sets are missing or incomplete; available Docs can be selected independently of lists. When a new snapshot records complete page coverage for one Doc, that Doc can remain selectable even if another Doc could not be read. Its original supported parent must also be present. Older partial snapshots without per-Doc coverage cannot establish that completeness.

Doc metadata and page content

A Doc's name, ID and parent are metadata. Finding a Doc in ClickUp or storing this metadata does not mean its page content was backed up. We separately request the pages and subpages as Markdown, and store only content ClickUp returns to the connected account.

A Doc may be listed while its page request is refused. Known inaccessible page sets are reported as gaps; a new backup continues collecting other accessible Docs and remains partial. We do not replace missing current pages with an older snapshot and label them current.

Check both Docs and Doc pages (Markdown) in Contents. A Doc count is not a count of fully protected documents. Markdown can omit rich elements; an empty Markdown response is not proof that every part visible in ClickUp was captured. Test the export and recovery of important Docs. Successful reading also does not establish permission to create a replacement Doc with the selected access in the destination.

Older coverage-1 snapshots collected structure and tasks, without the full content pipeline. Do not assume a dataset is present merely because it appears in this registry.

Files and export

Only supported ClickUp-hosted attachment URLs are copied, with size, host, redirect and storage checks. External links remain in raw records. Missing, inaccessible or quota-limited files are reported as gaps. Stored files are shared between snapshots of the workspace.

Prepare ZIP produces JSON datasets, per-list task CSV files, successfully collected Doc pages as Markdown and copied files. A ZIP cannot recover page content that was not collected. A prepared ZIP is retained for up to seven days, never beyond its snapshot's expiry. Restoring a copied attachment has a separate 50 MiB per-file upload budget; see restore limits.

Not covered

• Doc comments and rich Doc content: formatting, embeds, synced content, styles, covers and wikis are not preserved by Markdown export.
• External file contents are not copied.
• Whiteboards, forms, automations, dashboards, templates and history are outside this scope.
• Chat, views, goals and time entries are not collected by this coverage version.

See ClickUp limitations and the exclusions in each restore preview.

Something missing or unclear? Write to [email protected].