Move from ClickUp to devBoard

By Darko Bačić, founder of App Tube · 9 October 2026 · Facts checked 9 October 2026

When you finish, your open ClickUp work sits on a devBoard board. It has the same columns, the same tags (labels) and the same people. It takes about 45 minutes for one small project. devBoard has no ClickUp importer, so this is a move by hand. Your AI assistant does most of the typing.

Before you start

Move only open work. Closed tasks, old comments and history stay in ClickUp, where you can still read them.

Save a copy first. ClickUp can export your tasks to a CSV file, a table that any spreadsheet opens. If you cannot find the export, check ClickUp's help pages.

You also need:

• The role of admin or owner in devBoard. Members cannot make projects, columns or tags.
• An AI assistant connected over MCP, for step 6. MCP is the open standard that lets an AI assistant use other tools.

Still deciding? Read devBoard vs ClickUp, or the list of ClickUp alternatives.

What maps to what

ClickUp has more levels than devBoard: Workspace, Space, Folder, List, task and subtask. devBoard has a workspace, projects, and epics, tasks and subtasks. An epic is a big piece of work split into smaller tasks. A subtask is a step inside a task.

Pick one level to be your project. For most small teams, one Folder or one List becomes one project.

Steps

1. List the open work

Open the CSV in a spreadsheet, or open the List in ClickUp. Copy the titles of open tasks into a plain text note. Put each subtask on the line under its task, indented. You now have one short list per project.

2. Make the project

In devBoard, open Projects and press New project. Type a Project name and a Key of two to six letters, like CHK. Press Create project. The board opens with To do, In progress and Done.

3. Match the columns to your statuses

On the board, click Board columns in the header. Press Add column, type a Column name and pick its Group. Press Add column to save it. Rename or delete the first three to fit. The board now has one column for each status you use.

4. Add the tags

Open the project and choose Tags. Press New tag, type a Tag name and press Create tag. Make one for each ClickUp tag you still use. Make one for each custom field value you filter by, like "hotel".

5. Make the epics

Skip this step if each List became its own project. Otherwise open Epics and press New epic. Type the List's name and press Create. The epic shows as a card that says "No tasks yet".

6. Let your assistant create the tasks

Paste one list into your assistant. For example: "Create these ten tasks under the epic Checkout, assign me, due next week. Make each indented line a subtask of the task above it." The assistant answers with a key for each new task, like CHK-1. This turns an afternoon of typing into a few minutes.

Not connected yet? Connect devBoard to Claude Code first. ClickUp has its own MCP server too. Connect both, and the assistant can read the tasks from ClickUp instead of your paste.

7. Move the work that was already started

Ask: "Move CHK-3 and CHK-5 to In progress." Or drag the cards on the board. They now sit where they sat in ClickUp.

8. Stop adding work in ClickUp

Tell everyone that new work goes into devBoard from today. ClickUp stays as the place to look things up.

Check that it works

Put the board and the ClickUp List side by side. Each column should hold the same number of open cards. Open two or three tasks and check the subtasks, tags and due dates. Turn on Show subtasks to see each task's steps on the board.

What you leave behind

None of these move.

• Comments and history. Copy a comment into the description if it still matters.
• Attachments. Download the ones you need and drop them on the card, up to 10 MB each.
• Custom fields, apart from the ones you turn into tags.
• Automations. A card moves when someone moves it.
• Time entries and timesheets.
• Docs and Chat.

More setup help is in the guides.

If it does not work