How to merge two ClickUp workspaces

Last updated: July 2026

Short answer: ClickUp has no built-in way to merge two workspaces. The official feature request (“Move items across Workspaces”) has been open since 2017 with 2,800+ votes, and ClickUp's product team confirmed in late 2025 that it is not on the near-term roadmap. Until that changes you have two options: rebuild by hand with templates, or use a migration tool.

The manual method: templates + rebuilding

1. In the source workspace, save each Space (or Folder/List) as a template.
2. Share the template to your account, switch to the target workspace, and apply it.
3. Re-invite every member to the target workspace and redo their permissions.
4. Re-upload attachments one by one — templates don't carry files.
5. Repeat for every Space, then archive the old workspace.

This preserves structure (Folders, Lists, statuses, views) — but templates were never designed as a migration tool: comments, attachments, activity history, dependencies between tasks and actual task data beyond the template snapshot don't come along. For an agency consolidating client workspaces or two teams merging after an acquisition, that history is usually the part you can't lose.

What a real merge needs to carry

• The full hierarchy: Space → Folder → List → task → subtasks, all levels deep
• Comments with threads, formatting and who-said-what
• Attachments (files, not links that die with the old workspace)
• Dependencies and task links, re-pointed at the new copies
• Custom field values, tags, checklists with their resolved state

Merging with SpaceMove

SpaceMove copies a Space from one workspace into another through ClickUp's official API: one sign-in covers both workspaces, a free scan shows the complete manifest of what will move, and nothing is written until you approve it. Comments keep their threads (original author preserved as a prefix, since the API doesn't allow impersonation), attachments are re-uploaded file by file, and dependencies are re-wired to the new task IDs. Run it once per Space until everything lives in the target workspace — each run is a flat fee, undo is one click, and the audit CSV maps every old ID to its new one.

Honest limits: automations, whiteboards, forms and task activity history can't move — ClickUp exposes no API for them. Custom field definitions can't be created via API either, so the preview gives you an exact checklist to set up in the target first (see the migration checklist).