ClickUp

ClickUp limitations

ClickUp backup and restore cover the supported records listed in these docs. Some provider features and permissions limit recovery; a restore is not a complete workspace clone.

Access and API limits

Backups see only data available to the connected ClickUp account. Missing permissions, plan restrictions, API errors or unavailable source files can leave gaps. No fixed completion time is promised: the first backup and comment/Doc/file-heavy workspaces can take substantially longer. Requests share a rate-limit budget across workspaces using the same authorization. Backoffs respect provider throttling; separate workspaces do not bypass a token's limit.

Tasks and task details are reread; a task timestamp is not treated as proof that comments, checklists or files did not change. Docs are Markdown, with rich content and formatting losses. Original comment authors and dates are recorded in text headers, not restored as system metadata.

Docs access and completeness

Doc discovery, reading page content and creating a restored Doc are different operations. A Doc appearing in a search is not proof that its pages are readable or saved. Only Markdown returned by successful page-content requests is stored; known refusals produce gaps. New backups continue reading other accessible Docs after an explicit per-Doc access refusal.

Restore requires collected pages and a supported original parent present in that snapshot. An older kept snapshot may contain pages that a later snapshot could no longer read; inspect the selected snapshot rather than assuming all versions contain the same content.

For new Docs, Private and Workspace members are explicit access choices. The target's ClickUp plan and permissions must permit the chosen access. Read access to a source Doc does not guarantee permission to create a private replacement. A refusal is reported as incomplete; BackupLatte never automatically widens access to make a private create succeed.

ClickUp documents these Doc-sharing and plan limits and the Markdown limits of page retrieval. These limits do not mean all private Docs are unbackable: accessible page content is supported.

Recovery boundaries

Read the fidelity table and each preview. Restores select lists and Docs, not individual tasks. Limits are 50 lists and 50 Docs per operation. Required Spaces, folders and lists are recreated in the backed-up hierarchy when missing; active recognized records are reused. Users, original sharing permissions, field definitions and additional list memberships are not recreated. Whiteboards, forms, automations, dashboards, templates, history, views, goals, chat and time entries are outside restore scope. List comments are export-only.

An uncertain create can require a human decision. A candidate alone does not prove which operation created it. Saved mappings and recovery markers reduce repeat writes, but do not guarantee exactly-once creation or a duplicate-free result after an explicitly authorized retry.

Billing

ClickUp has its own plan and storage pool, separate from Linear. Billing counts unique members returned by ClickUp per active workspace, then sums across workspaces. A person in two workspaces can count twice; guest and bot exemptions are not assumed. The current prices and limits are shown on the pricing page and in the app.

Disconnect and data lifecycle

Disconnect stops access and queued work; reconnect is needed before new target writes. After app deauthorization, deactivation, uninstall or termination, affected data and metadata are deleted within 10 days, including stored snapshots and disaster-recovery copies. A paid plan and ordinary retention settings do not extend this deadline. Deauthorization does not cancel the separate Paddle subscription or remove records already restored into ClickUp.

See the Terms, Privacy Policy and DPA.

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