Migrate from Tability to Asana

Tability Objectives map to Asana Goals. We preserve the objective title, description, owner (mapped by email to Asana User), start/end dates, and current status (At Risk, On Track, Completed). Parent-child objective hierarchies in Tability map to Asana's hierarchical Goals with a parent_goal_gid reference. Progress percentage migrates as a manual value in Asana's progress field since Asana Goals do not auto-rollup from sub-items without an integration.

Tability Key Results are sub-objects attached to Objectives with a metric type (number, percentage, currency, binary), current value, target value, and unit label. Asana has no native Key Result sub-object; we model Key Results as custom fields on the linked Asana Project or as numbered Tasks under a Key Results grouping section. For numeric Key Results, we create Asana custom number fields; for percentage Key Results, we create percentage fields; for binary (yes/no) Key Results, we create a checkbox custom field. The Objective-Key Result relationship is preserved by linking each KR Task or field group to the parent Goal.

Tability check-in history (date, author, note, updated progress value) does not export in the standard CSV. We extract it from the activity log separately and merge it by Objective and Key Result ID. Check-ins attach to the corresponding Asana Goal as Notes (for objective-level check-ins) or to the parent Project Task (for Key Result-level check-ins). The original author and timestamp are preserved. If the activity log is inaccessible on the customer's tier, we flag the gap before migration.

Tability Tasks connected to Objectives carry assignees, due dates, and completion status. We map them to Asana Tasks, preserving the objective linkage as an Asana Tag (named with the parent objective title) so that task-to-OKR alignment is visible via tag filtering. Due dates, assignees, and completion status transfer directly. Subtasks in Tability map to Asana Subtasks under the parent Task.

Tability user records carry name, email, and role. We match by email to the destination Asana organization's User directory. Owners without a matching Asana User are flagged as ghost owners and held in a reconciliation queue; the customer provisions matching Asana users before record import resumes.

Tability allows custom fields on Objectives and Key Results. We export them as name-value pairs and map them to Asana custom fields by type: text to Asana text fields, numbers to number fields, dates to date fields, and dropdowns to enum fields. Asana does not allow custom field type changes after creation; we create new fields with the correct type before import and flag any type mismatches for customer resolution.

Tags applied to Tability Objectives and Key Results export as a string array. We map them to Asana Tags with identical labels. Asana Tags are org-wide and can be applied across projects; this preserves cross-project tagging that Tability supports.

Tability's Strategy Map visualizes cross-team objective alignment and dependencies as a UI-level graph with no structured export format. We extract a best-effort adjacency list by querying each Objective's linked dependencies from the Tability UI. On Asana, dependencies are task-level constructs (not goal-level), so we document the dependency pairs and deliver a written relinking guide for the customer's admin to rebuild using Asana's dependency linking on the migrated Projects. Organizations with more than 20 cross-linked objectives should plan for a manual review session post-migration.

Tability dashboards are saved view configurations with chart layouts and filter states. These are UI-level constructs without semantic data. We do not migrate dashboard layouts. The customer rebuilds visibility using Asana Portfolios (Advanced tier) or project-level reporting views. We document the key metrics and objectives visible on each Tability dashboard so the customer can configure equivalent Asana views.

Tability Standups are async daily updates scoped to individuals. They are transient, conversation-level data with no structural equivalent in Asana. We do not migrate standups. If the customer uses standups for OKR-adjacent progress tracking, we recommend Asana's My Tasks view or a daily standup section within a project as the replacement.

Tability's AI-generated goal drafts and suggestions exist within the platform's AI layer and are not stored as exportable database records. They cannot be migrated to any destination platform. Asana does not offer an equivalent AI goal recommendation feature at this time. We document this boundary upfront so customers do not expect their AI-generated draft library to carry over.

Tability integration settings (Jira, Slack, Teams, Asana connectors) are destination-side configurations that do not export. We document which tools were connected to Tability and deliver a reconfiguration checklist for each so the customer can re-establish the connections in their Asana workspace. The Asana integration settings in particular (Tability's bidirectional Asana sync) are replaced by using Asana Goals natively.