Moving from ClickUp

Before you start

1. Invite your team first, with the email addresses they use in ClickUp. People are matched by email only. Anyone who is not a member yet is left unassigned; the import invites nobody.
2. Have an owner or admin run the import. Only then does each comment stay under the name of the person who wrote it. When anyone else imports, every colleague’s comment is stored under the importing person, with the author’s name in front.
3. Keep each file under 2,000 rows. A larger file is refused. Export list by list, or folder by folder.
4. A task is imported into a project once. Each imported task remembers its ClickUp task id, so importing the same file into the same project again creates nothing twice. This holds per project: a file imported as new projects a second time makes new projects again.

1. Export from ClickUp

As of 2026-10, and not checked against ClickUp’s screens; their menus may differ. ClickUp has two exports, and they do not carry the same columns:

2. Import into AlianHub

1. Open Settings, then Import & export, and press Start an import (owners and admins). Inside a project, anyone who may create tasks can open More in the project toolbar and choose Import tasks… instead.
2. Choose ClickUp.
3. Under ClickUp export (CSV or Excel), pick the file. .csv, .xlsx and .xls are read; only the first sheet.
4. Choose Where should the tasks go? (see below).
5. Press Next and read the preview: tasks and subtasks per ClickUp list, new statuses, new tags, custom fields, who will be assigned, who is “not in this workspace”, how many rows will be skipped, each date that could not be read, and the columns that are not imported or not recognised. If tasks of the file are already in the project, the preview says how many and asks what to do with them.
6. Press Import N task(s). The bar moves one ClickUp list at a time.
7. Read the summary (What came in, rows skipped, dates not read, Left unassigned) before pressing Done. Undo this import is on the same screen.

Started from inside a project, the import goes into that project and the destination step only asks for the list.

What comes across

What changes shape

What does not come across

Check afterwards

1. Count. “N task(s) created” should equal ClickUp’s task count for those lists, less the skipped rows listed under it.
2. Tree. Open one task that has subtasks, and every task the summary says was moved or imported as a task.
3. People. Read the Left unassigned line. Invite those people, then assign their tasks by hand; the import will not do it later.
4. Dates. Read the “dates could not be read” list and set those by hand. Open five tasks that had a due date in ClickUp, and if your dates are written as numbers check that day and month are the right way round.
5. Fields and statuses. Compare the “did not fit their field” count with what you expect, open a task that uses each custom field, and look at the board: added statuses sit at the end of the project’s status list.

How long it takes

Not measured. There is no timing for 40, 1,000 or 10,000 tasks yet, so this guide gives none. What the code fixes:

• A file holds at most 2,000 rows, so 10,000 tasks means at least five files.
• The whole file is sent once for the preview, then one request per ClickUp list. The server accepts 2 MB per request unless BODY_LIMIT is raised; a list with long descriptions or many comments can reach that before it reaches 2,000 rows.
• Tasks are created first, level by level, then comments and links are saved one at a time. The dialog must stay open until it shows the summary.

What your team notices

Imported comments notify nobody and count as unread for nobody. Imported tasks have no watchers, so no “task created” notice goes out. People looking at the project see the tasks appear, and the project’s activity log gets one “created” line per task. Imported tasks are created the normal way, so an automation or webhook that reacts to new tasks in that project may run once per task; that has not been tested.

Importing again

Every imported task keeps its ClickUp task id. When you import into An existing project and tasks of the file are already in that project, the preview says how many and offers two choices:

A status the file changed is saved the way a status you change by hand is: the task leaves its old place on the board, a task moved to a done status records you as the person who closed it, and the task’s history gets a “changed status” line in your name. A status the project does not have is not applied: the task keeps its status, and the summary names the task and the status.

A task that was moved to the trash no longer counts as already here: importing its row again creates it anew. A task counts as already here only in the project it was imported into.

Undo

Undo this import moves every task that import created to the trash, where each can be restored. It is on the last screen of the import, and beside each import under Recent imports: in Settings, Import & export (owners and admins see every import), and in a project’s Import tasks… dialog.

• The person who ran the import can undo it, and so can an owner or admin.
• If someone has worked on an imported task since (changed it, commented on it, or added a subtask), the undo stops and names those tasks. Choose Undo, and keep those tasks to trash the rest; a kept task keeps the tasks above it.
• Custom fields the import created are switched off when no task outside the trash still uses them. Statuses and tags it added stay.
• Tasks the import only updated are not touched, and what an update changed is not rolled back.
• One undo covers one ClickUp list. The last screen of an import undoes all its lists at once.
• Nobody is notified.