What ClickUp template sharing does and doesn't copy

Last updated: July 2026

Saving a Space as a template and applying it in another workspace is ClickUp's closest thing to a cross-workspace move. Templates were built to start new projects from a pattern, not to relocate live ones — which explains exactly what survives the trip and what doesn't.

Carries over

• Space / Folder / List structure and their settings
• Custom statuses defined on the template's containers
• View layouts (List, Board, Calendar, etc.)
• Task shells, if you chose to include tasks — names, descriptions, subtask structure
• Custom field definitions attached to the templated containers

Left behind

• Comments — entire threads, gone
• Attachments — files are not embedded in templates
• Activity history — who did what, when
• Dependencies and task links across tasks
• Assignees and watchers — target workspace has different members
• Time tracked, sprint points state, live automations wiring

None of this is a bug — a template is a snapshot of structure, and ClickUp's help docs describe it that way. The trouble starts when a template is pressed into service as a migration tool: the losses are silent, and you discover them after the old workspace is gone.

If you need the living project to arrive

Copy through the API instead: comments (threads and formatting kept, original author preserved as a prefix), attachments re-uploaded file by file, dependencies re-wired to the new task IDs. That's what SpaceMove does, with a free preview manifest before anything is written and one-click undo after. For the decision between template, CSV and API routes, see how to move a Space to another workspace.