Migrate from Zenkit to Trello

Zenkit Collections map to one Trello Board per Collection. Multi-view data (Gantt, Table, Calendar) does not have a Trello equivalent, so we preserve the primary Kanban view structure and note the other view types in the migration summary for the customer to recreate manually. Collections with fewer than 10 Lists create a single Board; Collections with more than 10 Lists may be split into multiple Boards by List group to stay within Trello's navigation model.

Zenkit Lists migrate directly to Trello Lists within the target Board. List-level metadata (description, color) maps to the List's title and optional description. We preserve List order from the Zenkit Collection's default Kanban view.

Zenkit Items map 1:1 to Trello Cards. Standard fields (name, due date, assignee) map to Card name, due date, and member assignment. Custom fields translate to Trello Power-Up Custom Fields (Standard and above) or to Labels for simple categorical data. Card position within List preserves the Zenkit Item sort order.

Zenkit Sub-items have independent fields, which cannot be fully represented in Trello's checklist model. We convert Sub-items to checklist items with the Sub-item name as the checklist item text. Checked/unchecked state preserves. Any Sub-item custom fields are noted in the migration summary as manual rebuild items. For Sub-items with complex independent schemas, we create child Cards and link them with a Card link for the customer to organize manually.

Zenkit Labels migrate to Trello Labels on the target Board. We extract the label taxonomy (colors and names) and recreate it in Trello. Multi-value label fields (items tagged with multiple labels) preserve as multiple Label assignments on the Card.

Zenkit Item comments migrate to Trello Card comments with the original comment body, author (matched by email if a Trello user exists; noted as external author if no match), and timestamp preserved. Rich text HTML from Zenkit's JSON export is stripped to plain text for Trello compatibility.

Zenkit file attachments download to local storage, then re-upload to the target Trello Card via the Trello API. We handle file type mapping (Trello supports images, PDFs, and common document formats; files exceeding Trello's attachment limit are flagged for the customer). Attachment count and metadata migrate to the Card's attachment list.

Zenkit References connect Items across Lists and Collections. Trello has no cross-Board relationship field. We resolve each Reference to the target Item, create a Card link (the Card URL stored as a custom field or as a link in the Card description), and flag circular Reference chains for the customer to review. Cross-Board References without a Trello equivalent are documented in the migration inventory for manual reorganization.

Zenkit custom field types map as follows: text to Trello text Custom Field; number to Trello number Custom Field; date to Trello date Custom Field; select to Trello dropdown Custom Field; multi-select to Trello multi-select Custom Field; checkbox to Trello checkbox Custom Field. If the destination Trello workspace is on the Free tier (no Power-Up Custom Fields), select and multi-select fields collapse to Labels with a note that Power-Up upgrade is needed for full fidelity.

Zenkit formula fields (computations across Items) have no Trello equivalent. We document each formula field's logic and source fields in the migration summary. The customer rebuilds these as Trello dashboards (via Dashboard Power-Up) or in a connected BI tool post-migration.

Zenkit view configurations are UI-layer display settings, not data objects, and have no export mechanism. We migrate the underlying Items, not the view state. The primary Kanban view structure is preserved in the Board layout; Gantt, Calendar, and Mind Map views are documented as manual rebuild items in the migration handoff.

Zenkit automation rules (Business tier) have no standard export format. We capture each rule's trigger, conditions, and actions during discovery and deliver a written specification mapping each Zenkit rule to its equivalent Trello Butler rule or third-party automation tool (Zapier, Make). The customer's team implements these manually post-migration.