Migrate your Tability data

Objectives are the top-level container in Tability. We migrate them 1:1 with their title, description, owner, start/end dates, and current status. Parent-child objective hierarchies are preserved via a parent_objective_id reference field.

Key Results attach to Objectives and carry a metric type (number, percentage, currency, binary). We preserve the metric configuration, current value, target value, and unit label. Progress is recalculated on the destination based on value/target ratios.

Tability's Tasks connect to Objectives and carry assignees, due dates, and completion status. We map them to the destination's equivalent task or subtask object, preserving the objective linkage as a tag or custom property since not all PM tools have native objective-to-task wiring.

Check-ins are timestamped progress updates on Objectives or Key Results. We export the full check-in history (date, author, note, updated progress value) as a flat log. On destination platforms that support activity feeds or comments, we post this history to preserve the narrative context.

Standups in Tability are async daily updates scoped to individuals. They are transient, conversation-level data with no structural equivalent in most goal-tracking or PM tools. We do not migrate standup records.

Dashboards in Tability are saved view configurations with chart layout and filter state. These are UI-level constructs that do not carry semantic data. We do not migrate dashboard layouts; users rebuild these on the destination platform.

The Strategy Map visualizes cross-team objective dependencies and alignment. We export the dependency graph as a structured adjacency list. On platforms with native dependency linking, we reconstruct the relationships; otherwise, we flag them for manual re-linkage.

User records carry name, email, and role within Tability. We match them by email to the destination platform's user directory. Unmatched users are flagged as ghost owners and must be assigned manually post-migration.

Tability allows custom fields on Objectives and Key Results. We export them as name-value pairs. On destination platforms with typed custom fields, we apply type coercion where possible; mismatched types are flagged for review.

Integration configurations (Slack, Teams, Jira, Asana connectors) are destination-side settings that do not migrate. We document which tools were connected so the customer can re-configure them on the new platform.

AI-generated goal drafts and suggestions live in Tability's AI feature layer and are not stored as structured data objects. These are regenerated by the destination platform's own AI at setup time.

Tags applied to Objectives and Key Results are exported as a string array and mapped to the destination's tagging system. Where the destination has no tagging, we attach them as a comma-separated custom property.