Migrate from KANNA to Trello

KANNA Projects map to Trello Boards. The Project name becomes the Board name, the Project status (active, on-hold, completed) maps to Board visibility and state, and the Project date range maps to optional Board start and deadline fields via a custom Power-Up or Trello Workspace table if the customer is on Premium. We preserve the original KANNA Project ID in a card label for audit traceability.

KANNA Sub-projects allow phased or multi-site work within a Project. Where a Sub-project contains fewer than 10 Tasks, we map it to a Trello List inside the parent Board. Where a Sub-project contains more than 10 Tasks or represents a distinct team scope, we promote it to a separate Trello Board with a naming convention referencing the parent Project. The customer chooses the split strategy during scoping based on their preferred visibility model.

KANNA Tasks map to Trello Cards. The Task name becomes the Card title, the due date maps to the Card due date, and the Task status (To Do, In Progress, Done) maps to the Card's position in the relevant List. Task assignees map to Card members by email resolution. Sub-task support in KANNA is not a separate object but a property; we represent sub-tasks as Checklist items on the parent Card in Trello.

KANNA custom input fields are configured per Project template via Settings > Customize Settings and are bound to the template, not the record. We capture both the field definition (field name, type) and the value stored on each Task. Trello Custom Fields (available on Standard and above) are flat key-value pairs per Card. We map KANNA field types (text, number, date, dropdown) to the equivalent Trello Custom Field type and add them to the Board before migration begins. Any KANNA fields without a Trello equivalent are appended to the Card description as a formatted block.

KANNA Photo Reports are a first-class export category in KANNA's Data Import/Export feature. We extract photos and their captions and attach them to the corresponding Card in Trello. The photo caption migrates as Card attachment description or as a Card comment referencing the photo. Large batches of photos (over 100 per Card) may require chunking to avoid Trello attachment limits; we flag this during scoping and handle it as part of the migration run.

Documents associated with KANNA Projects and Tasks migrate as Card attachments in Trello. The document file and its association are preserved. Document content itself is not extracted or transformed; the file is reattached in its original format. We validate attachment sizes against Trello's 10MB per file limit on Free and Standard plans and flag any files exceeding the limit before migration.

KANNA's in-platform chat and reporting threads on Projects and Tasks are treated as Card comments. We preserve the author name, timestamp, and text content. KANNA's Data Import/Export does not explicitly list chat threads as a named export category, so we extract them from the UI or export format where accessible and flag any gaps explicitly. We advise customers to manually archive any critical thread history not captured in the export before migration begins.

KANNA separates customer information and property information as distinct data types. We map KANNA Clients to Trello Board Members (invited by email) and KANNA Properties to Trello Labels with a naming convention referencing the Property name. This preserves the client-property association while adapting it to Trello's flat member and label model.

KANNA's configurable project and task statuses are captured during export. We map each KANNA status to a Trello List name using the nearest semantic equivalent (e.g., Not Started to To Do, In Progress to Doing, Completed to Done). Where KANNA has more status values than Trello Lists can cleanly represent, we consolidate closely related statuses and note the consolidation in the mapping document.

KANNA user accounts and task assignees are resolved by email address against Trello Workspace members. We extract every distinct assignee across all migrating Tasks and match against the destination Trello Workspace. Any assignee without a corresponding Trello account is flagged in the reconciliation report for the customer's admin to provision before record migration begins.

KANNA's Gantt Chart is derived from task start dates, end dates, and dependency relationships. Trello has no native Gantt view on Free or Standard plans; the Timeline Power-Up (Premium and Enterprise) provides a timeline view sorted by card dates. We export the underlying task start and end dates and populate Card start and due dates accordingly. Dependency links (if configured in KANNA) are preserved as Checklist items or as Card links referencing the dependent Card, since Trello does not have a native dependency field.

KANNA's approval flow and bulletin board features are construction-specific workflow tools with no equivalent in Trello's core feature set. We do not migrate these as functional automations. We document each approval workflow and bulletin board post as a written item in the migration inventory, noting its current state and recommending a Trello approach (Card status changes, Butler rules, or a third-party Power-Up) for the customer's admin to implement post-migration.