Kodavara Guide
Migrate From Wrike to ClickUp: Folders, Projects and Custom Fields
ClickUp has a native Wrike importer that maps folders and projects and brings custom fields and statuses. Deep folder structures get flattened, and some Wrike features have no equivalent. This guide covers how it maps and how to plan the move.
Last reviewed October 2026. ClickUp changes often, so check ClickUp's help center for the latest. Written by Kodavara, an independent ClickUp Partner. Not published or endorsed by ClickUp.
What ClickUp Does Today
What You Can Do Natively
Start with the features available on your ClickUp plan.
The Native Importer
Sign in to Wrike from ClickUp's import settings. Wrike collaborators cannot export, so you need a full Wrike user account with enough permissions.
Folders and Projects
Top-level Wrike folders become ClickUp Folders, and Wrike projects become Lists. Nested folders with tasks and projects flatten into Lists inside the Folder.
What Comes Across
Tasks and nested subtasks, comments, assignees, start and due dates, time tracked, workflows as statuses and, optionally, attachments and user mapping.
An Export Fallback
Wrike can export to Excel or CSV if you need a manual route.
Where It Falls Short
The Gaps People Run Into
If these are your problem, keep reading.
- Collaborators cannot export, so a full Wrike user account is required.
- Nested folders are flattened, so deep structures need redesigning before the import.
- Formula and percentage custom fields are not imported, and comments on attachments are not included. Check anything beyond tasks and structure in a pilot.
- Check how attachments, dependencies, tags and user matching are handled in a pilot.
- Wrike workflows map to statuses. Request forms, dashboards and automations are checked in a pilot and rebuilt in ClickUp where needed.
Worked Example
How Wrike Concepts Map to ClickUp
Check each row in a pilot before you rely on it.
| In Wrike | In ClickUp | Note |
|---|---|---|
| Top-level folder | Folder | Imported as a Folder |
| Project | List | Imported as a List |
| Nested folder | Flattened into Lists in the Folder | Redesign deep structures first |
| Task and subtask | Task and subtask | Comments come with them |
| Custom field and status | Workflows become statuses; most custom fields import | Formula and percentage fields are not imported |
| Time tracked | Imported with the task | Check attribution and totals in a pilot |
| Dashboard, workload | Rebuilt in ClickUp | Check in a pilot |
Sample data for illustration.
The Configuration
How We Run a Wrike Migration
Wrike structures are often deep and heavily configured. These are the phases we follow, and what you get at each one.
| Phase | What We Do | What You Get |
|---|---|---|
| 1. Discover | We inventory your Wrike setup: folders, projects, workflows, custom fields and request forms, and your users. | A migration scope and a risk list |
| 2. Design | We design the ClickUp structure and write down how every source field, status and person maps. | A written mapping everyone agrees to |
| 3. Prepare | We tidy the source, then build the Spaces, fields and statuses in ClickUp. | A target that is ready to receive data |
| 4. Pilot | We import one or two real projects and check them task by task. | Fixes found before the full move |
| 5. Move | We run the full import and bring across anything the importer does not. | Your data in ClickUp |
| 6. Rebuild | We recreate your workflows, request forms, dashboards and workload views in ClickUp. | Working processes, not just data |
| 7. Cut Over | We freeze the old tool, check for last-minute changes and switch the team on an agreed date. | A clean switch date |
| 8. Support | We train the team and fix what turns up in the first weeks. | A stable workspace |
How Kodavara Consulting Does It
Set It Up Once
We untangle your Wrike structure, run the import and rebuild what does not carry across.
Scope the Structure
Map your folder tree, projects, custom fields, workflows and request forms, and decide what to keep.
Flatten and Redesign
Design a ClickUp hierarchy that works without deep nesting, and map statuses and fields to it.
Pilot a Real Project
Import a project with the folder depth, fields and comments you rely on, and check every task.
Run the Full Import
Import the rest and verify counts against the source.
Rebuild, Train and Cut Over
Recreate workflows, forms and views, train the team and switch on an agreed date.
FAQ
Common Questions
Not here? Ask us.
Does ClickUp import from Wrike?
Yes. There is a native Wrike importer. You need a full Wrike user account, because collaborators cannot export.
How do Wrike folders and projects map?
Top-level folders become ClickUp Folders and projects become Lists. Nested folders flatten into Lists inside the Folder.
Do custom fields come across?
Most do. Formula and percentage custom fields are not imported. Statuses, assignees, dates, time tracked, comments and subtasks are.
What does not come across?
Formula and percentage custom fields, and comments on attachments. We also check dashboards, workload settings and file versions in a pilot.
Do I lose my deep folder structure?
Nested folders are flattened, so we redesign the structure before importing.
Can you manage the migration?
Yes. We scope it, redesign the structure, pilot, import, rebuild workflows and support the cutover.
Keep Reading
Related Guides
Migrate From Asana
How to migrate from Asana to ClickUp: the native importer, what comes across, what does not, and a step-by-step plan for a clean switch.
Read the Guide →GuideHierarchy Design
How to design a ClickUp hierarchy that stays tidy: the levels, ClickUp's own guidance, why subtasks cannot have their own statuses, and agency setups.
Read the Guide →GuideWorkspace Migration
ClickUp cannot move tasks or Spaces between Workspaces natively.
Read the Guide →ServiceKodavara Consulting
The Kodavara service behind this guide: what we assess, configure and hand over.
Learn More →Want Help Setting This Up?
Tell us what you are trying to get done and we will point you at the fastest route.