How to move a ClickUp Space to another workspace

Last updated: July 2026

You can move a Space between Spaces' own hierarchy freely, but there is no “move to another Workspace” option anywhere in ClickUp — not for Spaces, Folders, Lists or single tasks. Workspaces are isolated by design: separate members, separate billing, separate data.

Option 1 — the template workaround (structure only)

1. Space settings → Save as Template.
2. Switch workspaces, create a new Space from that template.
3. Re-create everything the template didn't carry (see below).

What arrives: Folders, Lists, statuses, view layouts, and task shells if you included them. What doesn't: comments, attachments, activity history, dependencies, current assignee state — the living parts of your project. Details in what template sharing does and doesn't copy.

Option 2 — CSV export/import (task names only)

ClickUp exports task lists to CSV, and can import CSV into another workspace. You get task names, dates and some fields — flattened. No hierarchy deeper than List, no comments, no attachments, no subtask nesting, no dependencies. It works as a backup of record, not as a move.

Option 3 — copy through the API (everything the API can reach)

ClickUp's public API can read nearly everything in a Space and re-create it in another workspace: the full tree down through subtasks, comments with threads and rich text, attachments (downloaded and re-uploaded), tags with colors, checklists with resolved state, custom field values, dependencies and task links re-pointed at the new IDs. That is exactly what SpaceMove does — with a free preview manifest before anything is written, a flat fee per migration, an old-ID → new-ID audit CSV, and one-click undo. The copy is non-destructive: your source Space is never modified, so you can verify the result before retiring the old workspace.

Which option fits

Before any of them, run through the pre-migration checklist — statuses, custom fields and ClickApps need to exist in the target for a full-fidelity result.