ClickUp workspace migration checklist
Last updated: July 2026
However you migrate — template, CSV or API copy — the fidelity of the result is decided before the move, by what exists in the target workspace. ClickUp's API can write custom field values but cannot create field definitions, statuses or enable ClickApps, so anything missing in the target silently degrades. Ten minutes of setup prevents all of it.
1. Members and permissions
- Invite everyone who owns or is assigned work to the target workspace first — assignees that don't exist in the target can't be set.
- Note guests: guest seats and permissions are per-workspace.
2. Custom fields
- List the fields actually used in the source Space (name + type + dropdown options).
- Re-create them in the target with identical names and option labels — a workspace-level field (Custom Field Manager) covers every List automatically and is the simplest route.
- Matching by name is what lets values map even though option IDs differ between workspaces.
3. Statuses
- If the source uses custom statuses, create a Space in the target with the same status names — same-name statuses map cleanly; missing ones fall back to the default status.
4. ClickApps
- Toggle on in the target whatever the source relies on: Custom Fields, Tags, Dependencies, Time Tracking, Sprints. ClickApps are per-workspace settings, not data that migrates.
5. Things that will not move — plan around them
- Automations: screenshot or export the rules, rebuild them in the target after the move.
- Whiteboards and Forms: no API exists; re-create or link back to an archive workspace.
- Activity history: keep the source workspace on a free plan as a read-only archive instead of deleting it.
Let the scan write the checklist for you
SpaceMove's free scan reads the source Space and produces this list automatically — which statuses are in use, which custom fields and options need to exist in the target — before anything is written. Pair this checklist with the workspace merge guide for the full picture.