Migrate from ClickUp list by list

One way to leave a project tool is a weekend export. It is hard to get right: statuses don't map, comments go missing, a client still sends work to the old board, and the team can end up working in two tools and trusting neither.

Tengu moves you off ClickUp one list at a time, and you don't rebuild anything. Each list goes through the same three steps, and you choose when each one moves.

Who this is for

• Agencies that want to run engineering on a board built for the dev loop, without a big-bang migration.
• Teams that tried a big-bang migration before and don't want to do it again.
• Delivery leads who need the move to be invisible to developers: same statuses, same task IDs, no retraining.

Prices

List prices, October 2026, per user (ClickUp) or per seat (Tengu) per month, billed annually.

The importer is on every plan, Free included. During the move, people still working in ClickUp keep their ClickUp seats.

The three steps

1. Import a list

Connect ClickUp so Tengu can read the list, then choose what comes along: open quests only, or open quests plus those closed in the last 3, 6 or 12 months. The importer brings tasks, subtasks and every assignee, then each task's comments and attachments. The files ClickUp keeps (attachments, and images pasted into descriptions and comments) are copied into Tengu, up to 25 MB each, so they still open after you leave ClickUp; bigger ones stay links to ClickUp. A list imported before files were copied has a "Copy files into Tengu" action.

• Quests keep their ClickUp IDs, so links in Slack and agent integrations keep working.
• It stays under ClickUp's API rate limit, so a big list takes a while. About 500 quests take several minutes.
• It keeps going if you close the tab, pauses on a rate limit, and picks up where it stopped if you import again.
• Importing is silent: no notifications, no XP.

2. Check the counts

When it finishes, Tengu shows the quests per status that ClickUp reported beside the quests per status Tengu now holds. Tengu may hold more (quests closed before your window stay). It should never hold fewer. Any quest whose comments or attachments didn't come is listed by name, with the reason.

3. Move the team when it's ready

When the counts match and nobody on the list needs ClickUp for it any more, move the list. From then on it lives in Tengu, and ClickUp's copy stays as it was. Everyone with a quest in the list gets a notice in their inbox.

What doesn't change for the team

• The status menu. Imported lists keep their ClickUp statuses, colours and order, one key to change.
• Task IDs. The ID in last week's Slack message still opens the quest.

Linear and Jira too

Part of the team on Linear or Jira? The same importer reads a Linear team, or one project in it, with a personal API key, and a Jira Cloud project with your site address, your Atlassian email and an API token. Each comes into a new list in Tengu. Issues keep their Linear or Jira keys, Jira's descriptions and comments are converted to Markdown, files are copied into Tengu, and the same count check runs. The details are in A Linear alternative for agencies.

Where ClickUp is better

• Docs and the rest of ClickUp's breadth. Tengu is a delivery board, not a copy of ClickUp.
• Clients who work tickets. Tengu's client guests, free on Board and Studio, see the lists you share with them, comment and file requests. They can't move, assign or edit tickets.
• Custom fields. Tengu has no custom fields of its own yet.

Where Tengu is different

Once a list lives in Tengu, all of Tengu works on it: Run in Claude Code, the review queue with Pass and Send back, Ship with release notes, agents reading the full comment thread through the API, Tengu Bot routing a Slack channel to it, and, on Studio, a timer on every quest with timesheets and payroll behind it. It no longer depends on ClickUp's API at all.

What Tengu doesn't have yet

Custom fields of its own, docs, whiteboards, forms, dashboards and a mobile app.