Moving to ClickUp from Asana or Monday.com usually goes wrong in the same way. The import runs, the tasks arrive, and a week later nobody can find anything because the structure, statuses and automations didn’t make the trip in a way that makes sense.

The import is the easy part. The thinking you do before it is what decides whether your team adopts ClickUp or quietly goes back to spreadsheets. At Kodah we run ClickUp migrations for teams in South Africa, the UK, Spain and Singapore, and we always map these five things first.

1. Map Your Structure to the ClickUp Hierarchy

Each tool organises work differently, so a straight copy rarely fits.

Asana Monday.com ClickUp
Workspace or organisation Account Workspace
Team Workspace Space
Portfolio Folder Folder
Project Board List
Section Group Status or custom field
Task and subtask Item and subitem Task and subtask

Decide what each Space and Folder represents before you import, usually a department, a client or a service line. Getting this right is what makes everything else easy to find. Our ClickUp page shows the structures we use most.

2. Map Statuses and Workflows

In Asana, sections often double as workflow stages. In Monday, a status column usually does the job. In ClickUp, statuses are built into each List or Space and drive views, automations and reporting.

List the stages work actually moves through in each team, then agree a clean set of statuses before the move. Fewer is better. We’ve written more about how we run our own workflows in our articles.

3. Map Custom Fields and Columns

Monday boards often carry many columns, and Asana projects collect custom fields over time. Not all of them are still used.

Audit each field. Keep the ones people filter, report or automate on. Merge duplicates, like three different priority fields, and drop the rest. Then decide which fields should apply across a whole Space rather than one List. See how this differs by sector on our industry pages.

4. Map Automations and Integrations

Automations generally don’t carry over in an import, so they need rebuilding. Write down every rule your team relies on, such as “when status changes to Done, notify the client lead” or “when a form is submitted, create a task”.

Do the same for integrations. If your projects connect to Salesforce, email, Slack or Google Drive, plan how each connection will work in ClickUp. This is also the moment to add AI, for example using Claude to write weekly status updates from the workspace. Our Claude page explains how.

5. Map People, Permissions and Guests

Decide who needs full access, who only needs to see certain Spaces, and which clients or freelancers should join as guests. Match each person to the Spaces and Lists they actually work in.

Permissions done well keep the workspace tidy and protect client information, which matters under POPIA in South Africa and GDPR in Europe. Read about our approach on our about page.

How to Prioritise the Move

Don’t move every team on the same day. Start with one team that has simple workflows and a keen manager. Run Asana or Monday alongside ClickUp for a short overlap, then switch off the old tool for that team and move on to the next.

Archive finished projects instead of migrating them all. Bring across active work and anything you report on, and keep a read only export of the rest.

A quick example. Picture a Pretoria marketing agency moving from Monday.com with 40 boards. After mapping, they found 12 boards were really the same workflow for different clients. They became one ClickUp template, with a Folder per client. The team moved in three weeks and stopped asking where things were by week two. See more examples on our use cases page.

Moving to ClickUp FAQ

Can you import from Asana or Monday into ClickUp?

Yes. ClickUp offers import options for both Asana and Monday.com, which bring across tasks and much of their data. Structure, statuses and automations still need planning and checking afterwards.

How long does a migration to ClickUp take?

A single team can move in a week or two. A full company migration usually takes one to three months, depending on the number of teams, integrations and automations.

Will we lose our task history?

Most task details, comments and attachments can come across in the import. Check a sample after each import, and keep an export of the old tool until you’re confident nothing is missing.

Map First, Then Move

A good migration feels boring for your team, and that’s the goal. Map the structure, statuses, fields, automations and people first, and the import becomes the easy part.

If you’re planning a move to ClickUp in the new year, let’s chat. We’ll help you map it before anything moves.

Want to see where AI could help once you’re in ClickUp? Book a free AI Impact Assessment.