01 / Flowboard documentation
Choose the right route into the workspace
ClickUp and Asana use personal API tokens for the import run. Trello and CSV use uploaded files. Create or export the source material through the source product, then use Flowboard's corresponding import path. Keep the original system available while validating the result.
Invite the relevant team members before importing. Matching works against people already in the workspace, and an unmatched assignee is left off the task rather than guessed. Use a current export or a clearly identified source project so the team can distinguish the original state from changes made after migration began.
02 / Flowboard documentation
Understand the source-specific mapping
In ClickUp, lists become projects. Tasks and up to two levels of subtasks map into tasks and child tasks. Status and priority values map to Flowboard equivalents. Space and Folder layers flatten away, and imported tasks arrive without sections.
Asana projects remain projects and sections remain sections. Completed tasks become Done. One subtask level becomes child tasks; deeper subtasks are flattened into titles with a parent prefix. ClickUp and Asana assignees match by email, then name. These are explicit mappings, not a promise that the two systems have identical structures.
| Source | Primary mapping | Important boundary |
|---|---|---|
| ClickUp | List to project; tasks and child tasks | Space/Folder layers flatten; no imported sections |
| Asana | Project and sections retained | Deeper subtask hierarchy becomes title context |
| Trello | Board to project; lists to sections; cards to tasks | Cards in closed lists are skipped |
| CSV | Rows to the chosen task, contact or project entity | Confirm the field mapping before writing |
03 / Flowboard documentation
Use file imports deliberately
A Trello board can become a new project or land in an existing one. Lists become sections, cards become tasks and checklists become subtasks. Members match workspace users by name. Labels and attachment links are appended to descriptions. Recognized completed-list names can set tasks to Done, while cards in a closed list are skipped.
CSV is useful when the source does not have a dedicated import wizard. Choose the entity type, inspect auto-matched headers and confirm the mapping. A column named name, title or task can map to a title field, but similar names do not guarantee that every column has the meaning intended. Test a small file containing realistic dates, empty values and unusual text.
04 / Flowboard documentation
Keep the history that does not transfer
Comments, historical time entries and custom fields do not import. Attachment references arrive as links in descriptions rather than uploaded files. That means a visually complete task list can still lack the conversation or effort history needed to explain a past decision.
Retain source exports or read access according to your agency's obligations and agreements. Move essential current decisions into an appropriate project brief or document, clearly identified as migrated context. Do not describe copied summaries as original comments or create invented time entries to make old totals appear complete.
- Keep historical hours in the source record.
- Verify that attachment links remain accessible.
- Capture important current decisions in a project brief.
- Check source-retention needs before cancelling another subscription.
05 / Flowboard documentation
Validate a representative run
For an illustrative website project, count the source tasks and sections, note the key owners, and identify one completed item, one nested item and one attachment. After importing, compare those examples and inspect the job summary. Check created counts, skipped counts and work left unassigned.
Open the error log whenever records were skipped. Row-level failures record an item and reason, up to 100 entries; beyond that the run continues without recording additional errors. A small visible error list is therefore not proof that only a small number of records failed. Use the summary counts as well as the examples.
06 / Flowboard documentation
Plan rollback and the cutover
Owners and administrators can roll back an import batch. Imported rows carry the run's batch identifier, and rollback removes records created by that batch with per-entity counts. Review the batch and its consequences before using rollback, especially if people have begun working in imported projects.
Once verified, agree when the team starts updating Flowboard as its working record. These importers do not keep synchronizing with the source tool. Parallel editing without a cutover rule creates two versions of the project. Keep an exception list for work that stays elsewhere, and explain how the team should reference it.
THE PRACTICAL DETAILS
Questions, answered.
Is this an ongoing sync?
No. These are one-time migration tools. They do not continue exchanging changes with the original product after the import.
Will historical comments and time move?
No. Comments, time entries and custom fields do not import. Retain their source records if they are needed for reporting or decision history.
Why are some tasks unassigned?
The importer does not guess when it cannot match a person. Invite the team first, then inspect unmatched assignments and correct them deliberately.
Can I undo a bad import?
An Owner or Admin can roll back the specific batch. Review its records first and coordinate with anyone who has started working in them.