Migrate from Tability to monday Work Management

Tability Objectives map to monday.com Boards. We create the Board with the Objective title as Board name, description in the Board welcome column, owner mapped to a Board subscriber, and start/end dates set via timeline column configuration. Each Board is created before any Items are imported so that group and item dependencies resolve correctly. For organizations using Tability's parent-child objective hierarchy, parent Objectives become top-level Boards and child Objectives become Groups within the parent Board.

Key Results map to monday.com Groups or Items depending on metric type. Numeric, percentage, currency, and binary Key Results migrate as Groups containing Items where each Item represents a measurement update (current value vs target value). Progress percentage is stored in a number column, target in a separate number column, and the metric unit label as a text column. On monday.com Pro and Enterprise, the dependency column can link Key Result Groups to the parent Objective Board for cross-board alignment visibility.

Tability Tasks connected to Objectives migrate as monday.com Items. We map assignee to the People column, due date to the Date column, status to the Status column (with Tability's open/in-progress/complete states mapped to monday.com's default or custom status values), and description to the Text column. If Tasks have a direct Key Result linkage, we set the Item's Group assignment to match the Key Result Group.

Tability check-ins are timestamped progress updates with author and note content. The CSV export does not include check-in history. We export the activity log separately and reconstruct check-in entries as monday.com Updates on the corresponding Board or Item (using the Update API), preserving date, author, note text, and the updated progress value. If the activity log is inaccessible on the customer's Tability tier, we flag this gap and recommend the customer export a screenshot archive of key check-in periods before cutover.

The cross-team dependency graph in Tability's Strategy Map has no structured export format. We extract a best-effort adjacency list by querying linked Objectives manually from the UI. For organizations with more than 20 cross-linked Objectives, we flag this as a manual re-linkage scope. On monday.com Pro and Enterprise, we configure the Dependency column on the relevant Boards and deliver a written dependency map listing every Objective pair and its dependency direction for the customer's admin to re-link manually post-migration.

Tability user records carry name and email. We match by email to the monday.com workspace User directory. Owners assigned to Objectives or Key Results map to the People column on the Board or Item. Users without a matching monday.com account are flagged as ghost owners and held in a reconciliation queue for the customer's admin to provision before the migration resumes. Active versus inactive status is preserved in a text column for admin review.

Tability allows custom fields on Objectives. We export them as name-value pairs and create monday.com columns of the matching type (text, number, date, dropdown). Type coercion is applied where Tability stores a numeric value in a text field; we create a number column in monday.com and flag any value that fails validation for manual correction.

Tability Key Result custom fields map to monday.com columns on the Group or Item representing the Key Result. Metric type configurations (number, percentage, currency, binary) are preserved as separate configuration columns alongside the custom fields. Tability's metric type selector does not have a direct monday.com equivalent; we document the metric type as a text column label and advise the customer to use the relevant column type for the metric values themselves.

Tability tags applied to Objectives and Key Results are exported as a string array. On monday.com Standard and above, we map them to the native Tags feature on Boards. On Basic tier (which has no Tags), we attach them as a comma-separated text value in a custom label column. The customer chooses tag strategy during scoping based on their monday.com plan tier.

Tability integration configurations (Slack delivery, Teams check-in prompts, Jira linkage, Asana sync) are destination-side settings that do not carry over as migration data. We document each active integration with its trigger conditions and delivery target so the customer's admin can re-configure equivalent automations in monday.com's Automation Centre or re-establish native integrations from the Integrations page post-migration.

Tability's AI-generated goal drafts exist within the platform's AI feature layer and are not stored as structured database records. They cannot be exported or migrated to any destination platform. We document this boundary upfront so customers do not expect their AI-generated draft library to carry over. monday.com's own AI capabilities or third-party OKR integrations (such as Apero, Koan, or Perdoo connectors) regenerate recommendations post-migration.

Tability dashboards are saved view configurations with chart layouts and filter state. These are UI-level constructs with no semantic data content. We do not migrate dashboard layouts. We deliver a written inventory of each dashboard's chart type, metric, and filter configuration so the customer's admin can rebuild equivalent views using monday.com's Chart View and Dashboard widgets post-migration.