Move your own data. In an afternoon.
Forty client projects sit in the tool you have outgrown, and the cost of moving them is what renewed it two years running. Here is exactly what moves, what does not, and how to undo a run that goes wrong.
Two ways in, depending on the tool
- Export a file
- Trello and CSV read a file you already have. Export the board or the spreadsheet, upload it, map the columns if it asks.
- Paste a token
- ClickUp and Asana pull straight from their API with a personal token you generate and we hold only for the run.
What each import actually maps
ClickUp
- Each list becomes a project
- Tasks become tasks, subtasks become child tasks, two levels deep
- Status maps across: done and closed become Done, doing becomes In progress, qa becomes Review
- Priority maps urgent, high, normal and low onto ours
- Assignees match your workspace members by email, then by name
ClickUp's Space and Folder layers flatten away, and imported tasks arrive in the project without a section.
Asana
- Projects become projects
- Sections stay sections, which ClickUp cannot offer because it has none
- Tasks become tasks and completed becomes Done
- One level of subtasks becomes child tasks
- Assignees match by email, then by name
Subtasks deeper than one level are flattened into the title with a “parent > ” prefix rather than dropped.
Trello
- The board becomes a project, or lands in one you already have
- Lists become sections and cards become tasks
- Checklists become subtasks
- Members match your workspace users by name
- Labels and attachment links append to the task description
Lists named done, complete, completed, finished, closed or archived land their cards as Done. Cards sitting in a closed list are skipped.
CSV
- Rows become tasks, contacts or projects, whichever you pick
- Column headers auto-map to fields, so name, title and task all land as the title
- You confirm the mapping before anything is written
This is the path for a tool with no wizard of its own. If you can export a spreadsheet, you can move.
What to check when the run finishes
- The skipped count
- Every run returns what it created and what it skipped, per entity. A skipped count above zero is the number to open the error log for.
- The error log
- Row-level failures are recorded against the job with the item name and the reason, up to 100 entries. Past 100 the run keeps going and stops logging.
- Anyone left unassigned
- A person we cannot match is left off the task rather than guessed at. Invite the team first and the match rate goes up.
A run you can undo
Every row an import writes carries that run's batch id. If the result is wrong, an Owner or Admin can roll the whole batch back, and the tasks, contacts and projects it created are removed together with a count of each. Fix the export, run it again.
So what: the first attempt does not have to be the good one, which is the actual reason migrations stall.
What does not come across
- Comments do not import. No importer writes them, on any source.
- Time entries do not import. Historic hours stay in the old tool as a record.
- Custom fields do not import.
- Attachments arrive as links appended to the task description, not as files in Flowboard.
- These are one-time migration tools, not an ongoing sync and not an integrations marketplace. Nothing keeps talking to the old tool once you have moved.
Bring your data with you on the trial, not after it.