Kodavara Guide
Migrate From Asana to ClickUp: What Carries Over and What Does Not
ClickUp has a native Asana importer that brings across tasks, subtasks, comments and more. It leaves some things behind, and the structure you choose matters more than the import itself. This guide covers what comes across, what does not, and how a migration is planned so the switch is clean.
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
Start from Settings, then Imports / Exports, then Import from apps, and sign in to Asana. The Asana account must be able to see the projects you import, including private projects, teams and portfolios. Start-up takes a few minutes, and the run itself can take from a minute to several hours depending on data volume and Asana rate limits.
What Comes Across
Tasks, subtasks, descriptions, comments, assignees and collaborators, start and due dates, and attachments that are still accessible from Asana at import time.
Sections and Milestones
Asana sections and columns become ClickUp Lists or statuses. Milestones can be imported as ClickUp Milestones, as plain tasks or skipped.
What Does Not Import Automatically
Freestanding tasks, nested subtasks, tasks shared between projects, recurring tasks, private tasks and @mentions do not import automatically. Each has a manual route, such as moving tasks into projects first or recreating recurrence and privacy in ClickUp.
Where It Falls Short
The Gaps People Run Into
If these are your problem, keep reading.
- @mentions do not import.
- Sections can import as Lists, statuses or a Label Custom Field, so choose the mapping before you import and check how your Asana custom fields land in a pilot.
- Asana rate limits can slow a large import.
- Rules, forms and permissions may not come across, so plan to rebuild them.
- Manual or CSV migrations tend to flatten comments, attachments, subtask hierarchy and dependencies, and there is no sync afterwards.
Worked Example
How Asana Concepts Map to ClickUp
The importer decides some of this. The rest is a design choice you make before the import, which is where most of the work is.
| In Asana | In ClickUp | Note |
|---|---|---|
| Project | A List or Folder, your choice | Decide the structure before you import |
| Section or column | A List or a status | Choose one rule and keep to it |
| Task and subtask | Task and subtask | Comments come with them |
| Milestone | Milestone, task or skipped | Chosen at import time |
| Custom field | Check in a pilot | Sections can arrive as a Label field |
| Rule, form, permission | Rebuilt as automations, Forms and sharing | Check in a pilot |
Sample data for illustration.
The Configuration
How We Run an Asana Migration
A migration is a business configuration project, not a button. 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 Asana setup: custom fields, rules, forms and portfolios, 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 rules and forms as automations and Forms, and your 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 plan the move, run the import, bring across what it misses and check the result with you.
Scope It
List the projects, custom fields, rules and users in Asana, and decide what to move, what to archive and what to leave behind.
Design the ClickUp Structure
Choose Spaces, Folders, Lists and statuses, and map Asana sections and fields to them.
Pilot Two Projects
Import a small, real project, check comments, subtasks, attachments and dates, and fix the mapping.
Run the Full Import
Import the rest, then bring custom fields across with the CSV importer.
Rebuild, Train and Cut Over
Recreate rules and forms, train the team and switch on an agreed date.
FAQ
Common Questions
Not here? Ask us.
Does ClickUp import from Asana?
Yes. There is a native Asana importer under Settings, Imports / Exports. It brings tasks, subtasks, comments, assignees, dates and attachments when they are accessible.
Do custom fields come across?
Check them in a pilot. Sections can import as a Label Custom Field, and we map the rest of your Asana fields as part of the migration.
Do comments and attachments come across?
Comments come across with their tasks. Attachments come across when they are still accessible from Asana at import time.
How long does the import take?
Anywhere from a minute to several hours, depending on how much data you have and Asana rate limits.
Do @mentions import?
No. @mentions do not import.
Can you manage the migration?
Yes. We scope it, design the structure, run a pilot, import, rebuild what the importer misses and support the cutover.
Keep Reading
Related Guides
Workspace Migration
ClickUp cannot move tasks or Spaces between Workspaces natively.
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 Cleanup
How to clean up a messy ClickUp workspace: merge duplicate custom fields, remove unused setup, and audit what you have before you delete.
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.