Migrate from Tability to Trello

Tability Objectives map to Trello Boards. Each Objective's title, description, owner, start date, and end date transfer to the Board name, description, and membership. The Board is created first so that its ID is available for all child Key Result and Task records. Parent-child Objective hierarchies in Tability map to Board Collections or Workspace-level board grouping if the customer uses multiple Workspaces.

Key Results map to Trello Lists within the parent Objective Board, or to Card records with the metric configuration documented in the Card description. Numeric Key Results (number, percentage, currency) are stored as Custom Fields in the Key Results list if the customer is on Trello Standard or above. The current value, target value, and unit label migrate as structured data. Progress percentage is not natively tracked in Trello; we use checklist completion percentage as a proxy or document the last-known progress value in the Card description for manual reference.

Tability Tasks connected to Objectives map to Trello Cards on the corresponding Board. We preserve the assignee (mapped to Board member), due date, description, and completion status. Tability's task-to-objective linkage is recorded in the Card description as a structured note (e.g., 'Linked to Objective: [name]') since Trello has no native many-to-one task-to-objective relationship. Subtasks in Tability migrate as Card checklists with individual checklist items.

Tability check-in history (date, author, note, updated progress value) is reconstructed as Trello Card Comments. We export the activity log separately from the main CSV, parse each check-in by Objective or Key Result ID, and insert a dated Comment on the corresponding Card. The comment format preserves the author and the updated progress value. This is the closest Trello equivalent to Tability's timestamped progress-update log; there is no native check-in object or progress history in Trello.

Tability's cross-team dependency graph (Strategy Map) has no structured export format and is a UI-level construct. We attempt to export the dependency adjacency list by querying each Objective's linked dependencies manually from the Tability interface. On Trello, we reconstruct dependencies as Card Links (using Trello's Attachments > Linked Cards feature) and document the full adjacency list in a delivered CSV so the customer can re-establish links manually. For organizations with more than 20 cross-linked Objectives, we flag the graph for manual re-linkage planning.

Tability Users and Objective owners are matched by email to Trello members on the target Workspace. We add each matched user as a member of the relevant Board(s). Users without a matching Trello account are flagged as ghost owners and held in a reconciliation queue for the customer's admin to provision before Board membership migration completes.

Tability custom fields on Objectives and Key Results are exported as name-value pairs. On Trello Standard and above, we create Custom Fields of the appropriate type (text, number, date, dropdown, checkbox) within each Board. On Trello Free, custom field values are stored as structured text in the Card description. Type coercion is applied where possible; mismatched types are flagged in the pre-migration audit.

Tability tags on Objectives and Key Results map to Trello Labels on Cards. We export the tag array per record and create Label records on the destination Board with matching colors where the customer has defined a color scheme. Unmapped tags (where no corresponding Label exists) are created as new Labels in a neutral color.

Tability Standups are async daily updates scoped to individuals and are transient conversation-level data with no structural equivalent in Trello. We do not migrate standup records. We document their existence and approximate volume in the pre-migration audit so the customer understands what will not appear in Trello.

Tability Dashboards are saved view configurations with chart layout and filter state. These are UI-level constructs with no semantic data. We do not migrate dashboard layouts. The customer rebuilds dashboard views in Trello using Board Filters, Dashboard views (Premium), or Power-Up reporting tools.

Tability AI-generated goal drafts and suggestions live in the platform's AI feature layer and are not stored as exportable database records. They cannot be migrated to Trello or any other destination platform. We document this boundary upfront so customers do not expect their AI-generated draft library to carry over. Trello's own AI features (quick-capture on Standard and above) regenerate recommendations post-migration.

Tability integration configurations (Slack, Teams, Jira, Asana connectors, Zapier) are destination-side settings that do not carry over. We document which tools were connected in Tability so the customer can re-configure them within Trello using Power-Ups, Butler rules, or Trello's native integrations (Slack, Google Drive, etc.) on the destination side.