ClickUp

Restore a ClickUp backup

Restore keeps the backed-up hierarchy: Spaces, folders, lists, tasks and subtasks. Docs return to their original supported parent location, with their page hierarchy.

Choose where to restore

Choose This workspace to recover missing content in the backed-up workspace. Active elements are reused by identity, so existing tasks and their current edits are kept. An element deleted or newly archived since the snapshot is recreated. ClickUp assigns a new provider ID; BackupLatte stores its relationship to the original element. Later restores and later backups recognize that relationship.

Choose Another workspace to restore into a separately authorized ClickUp Workspace. Required Spaces, folders and lists are recreated in their original hierarchy. Repeating the restore into that Workspace reuses earlier replacements. Equal list names in different source containers remain separate lists.

Select content and prepare the preview

1. Open a kept successful or partial backup and choose Restore.
2. Choose the destination Workspace.
3. Select lists and Docs. Select all includes available items hidden by search. A request supports up to 50 lists and 50 Docs.
4. If restoring Docs, choose access for newly created Docs.
5. Prepare and review the preview, including unsupported content and warnings.
6. Confirm Restore in ClickUp.

Only tasks whose home list is selected are restored. Additional list memberships are not recreated. Guest-only tasks are also excluded. Required parents of selected Docs may be created even when their lists' tasks were not selected.

Preview counts describe selected elements and required parents. Active elements are reused during execution; these counts are not a promise to create that many new copies. Provider limits and recovery verification can increase the duration.

Access for Docs

Existing Docs retain their access and content. For new Docs, choose Private or Workspace members explicitly. Workspace access is not a public Internet sharing link.

ClickUp does not expose every original Doc permission through the public API. The target's ClickUp plan and permissions must allow the chosen access. Private creation can be refused even when the account can read the source Doc. A saved Doc name or metadata is not enough: its page content must have been collected. If creation is refused, the restore reports the Doc and its dependent pages as missing. It never automatically retries private content with wider access.

To change the chosen access after a refusal, choose Review restore options and prepare a new preview. Existing records are recognized again; a new preview does not authorize duplicate copies of records that already exist.

Results and continuation

The result distinguishes Created, Already present, Adopted after recovery, and Skipped records. Selected records that could not be restored produce Completed with gaps, not an unqualified success.

An explicit Resume restore retries proven missing records while preserving completed mappings and attempt history. A record deliberately skipped after an uncertain request is not silently retried.

When a decision is needed

If ClickUp does not confirm whether a create succeeded, the restore saves its intent and pauses. It checks the exact target container and its recovery marker. An ambiguous result requires a decision: adopt a verified existing object, skip, or explicitly accept the risk of another create. It never automatically repeats an uncertain POST. Another restore cannot bypass an unresolved creation.

Files and links

Copied task attachments can be re-uploaded when their stored bytes are available. Embedded Doc/comment links may still point to the source and can expire; inspect unresolved links in the report.

The report includes ID mappings, selected omissions and their reasons, name adjustments, duplicates observed during recovery, and source links that could not be rewritten. Download links are short-lived; request the report again if a link expires.

Fidelity

New IDs and system creation dates: recreated records have new ClickUp IDs, system dates and creators. BackupLatte retains their logical identity; it cannot rewrite all provider system metadata. Docs use Markdown; rich formatting, embeds, synced content, styles, covers and wikis are not fully reproduced. Custom-field Definitions are not created; complex field mapping remains limited; see the preview for values preserved as text or other exclusions. Original permissions and sharing rules are not fully recreated by the API.

Whiteboards, Forms, Automations, Dashboards, Templates, history, views, goals, chat and time entries are excluded from backup coverage and this restore scope. Verify the selected scope and report before using a restored Workspace.

If one Doc cannot be read, new backups continue collecting other accessible Docs and remain partial. A Doc is selectable only when its own pages were fully collected and its original parent is present in the snapshot. Older partial snapshots without per-Doc coverage cannot prove this and keep Docs unavailable.

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