Board structure
- Board name and description
- Lists and cards
- Labels and custom fields
- Archived cards when selected
Trello migration
Import one board, review every mapping, and test Kanera with real work before moving the wider team.

The importer carries the structure and context needed to evaluate Kanera with a real project.
See the technical import guideNothing is created while Kanera analyzes the export and you work through the mapping choices.
Kanera reads one Trello board JSON export and identifies lists, fields, members, cards, comments, checklists, and attachments.
Create, reuse, or skip lists, labels, and compatible custom fields. Archived lists are skipped by default.
Map Trello members to Kanera users or leave them unassigned. The choice controls assignees and comment attribution.
Check the board options, skipped-card count, attachment count, and mappings before Kanera creates the imported data.

Create, reuse, or skip each Trello list before Kanera creates the board.
The destination determines whether the imported workflow stands alone or joins a shared Kanera structure.
The import stays controlled. Resolve each structural choice before confirmation and review exceptions again after the import.
Create a compatible Kanera field, map it to an existing field, or skip it. Incompatible field types must be resolved before import.
Leave the member unassigned. Unmapped card and checklist assignments are skipped, while the original comment author name is preserved in the comment body.
Kanera keeps the Trello attachment link and reports why the file was skipped, such as access, file type, size, or storage limits.
Archived lists are skipped by default. Turn on archived-card import only when that history belongs in the first move.
A standard Trello board can usually be prepared and reviewed in less than 30 minutes. The import time depends on board history, card volume, and attachment copying.
Begin with one representative board. Confirm the workspace structure, mappings, permissions, and imported result before planning the rest.
We can help select the pilot, review how boards should become Kanera workspaces, plan member access, and prepare the wider rollout.
Yes. Import one representative board and run it alongside Trello during the evaluation. The import does not modify the Trello board.
No. It creates a one-time copy in Kanera. Changes made later in Trello are not reflected automatically in Kanera.
Yes. You review list, label, custom-field, and member mappings, along with the import options and summary, before confirmation.
A standard board can usually be prepared and reviewed in less than 30 minutes. Board size, history, attachments, and mapping decisions affect the import itself.
Yes. For suitable company evaluations, we can help select the pilot board, review the workspace structure, plan mappings, and prepare the wider rollout.
Usually not at first. Begin with active work and one representative workflow. Review historical and archived material separately after the pilot.
Choose someone who understands the Trello workflow and the people using it. They should review mappings before import and validate the first Kanera board afterward.