Can you move a ClickUp task to another workspace?

Last updated: July 2026

Not directly. Tasks move freely within a workspace (any List, any Space), but the move dialog never offers another workspace as a destination. Workspaces don't share members or data, so a native move would have to answer hard questions — ClickUp simply doesn't offer it.

What people actually do for one or two tasks

1. Open the task in the source workspace side by side with a new task in the target.
2. Copy the description over (markdown paste keeps most formatting).
3. Download each attachment, re-upload it to the new task.
4. Copy important comments into one summary comment — threading is lost.
5. Re-create checklist items, tags, due dates and priority by hand.

Ten minutes per task if it's rich. Fine once; painful for a hundred tasks, and subtask trees make it worse because parent links have to be rebuilt in order.

Moving tasks in bulk

If the tasks live in the same List or Space, the practical unit of migration is the Space: copy the whole thing through the API and archive what you don't need afterwards. SpaceMove moves a Space with subtask nesting, threaded comments, attachments, tags, checklists and dependencies intact, previews everything before writing, and undoes the whole run in one click. See how to move a Space to another workspace for the full comparison of template, CSV and API routes.