Migrate from Tability to Microsoft Project

Tability Objectives map to Microsoft Project projects if the organization manages objectives as standalone initiatives, or to summary tasks within a master project if multiple objectives roll up to a single program. The Objective title becomes the Project name or summary task name. Start and end dates migrate as Project Start and Finish or as the summary task's start and finish dates. Owner assignment maps to a Microsoft Project Resource record created during the owner-to-resource reconciliation phase.

Tability Key Results map to Microsoft Project tasks. The metric type (number, percentage, currency, binary) and target value are stored in custom task fields (Text1 for metric type, Number1 for target) since Microsoft Project has no native Key Result data model. Current progress value is mapped to PercentComplete on the task. The unit label migrates to a Text2 custom field. We do not attempt to replicate Tability's automatic progress calculation because Microsoft Project calculates task progress based on actual work or percent-complete entries rather than from an external metric.

Tability Tasks connected to Objectives and Key Results map to Microsoft Project tasks or subtasks. The Objective linkage is preserved by nesting the task under the corresponding summary task (representing the Key Result) that is itself nested under the Objective summary task. Assignee, due date, and completion status migrate as Resource Assignment, Finish date, and PercentComplete=100 respectively.

Check-in history is not included in Tability's standard CSV export. We extract the activity log separately and reconstruct check-in records by Objective and Key Result ID, merging them with the CSV export. Each check-in becomes a Microsoft Project task note appended with the check-in date, author name, and progress note. Where Microsoft Project does not support task-level notes at scale, we attach check-in history as a project-level document or SharePoint-linked note. Large check-in histories (over 50 entries per Key Result) may require manual triage to keep the task note field readable.

Tability's Strategy Map visualizes cross-team objective dependencies as a UI-level graph with no structured export format. We export a best-effort adjacency list by querying each Objective's linked dependencies from the Tability UI. Dependencies are then reconstructed in Microsoft Project as Finish-to-Start task dependencies. Dependency graphs exceeding 20 cross-linked objectives are flagged for manual re-linkage planning on the destination because automated dependency reconstruction from the adjacency list is fragile for complex graphs.

Tability Users and Objective owners are matched by email to Microsoft Project resource records. We extract distinct owner emails from the CSV export and create a corresponding Resource record for each unique owner. Unmatched owners (users in Tability without a corresponding identity in the destination) are flagged as ghost owners and require manual assignment to the correct Resource before task import resumes. Inactive Tability owners map to Resources with the 'Inactive' flag in Microsoft Project.

Tability custom fields on Objectives and Key Results are exported as name-value pairs in the CSV. We map them to Microsoft Project custom enterprise fields (Text, Number, Cost, Flag, or Date types chosen during scoping to match the custom field data type). Type coercion is applied where Tability's untyped custom fields contain values that fit a specific Microsoft Project field type. Mismatched types are flagged and stored as Text fields to avoid data loss.

Tags from Tability Objectives and Key Results are exported as string arrays. They are mapped to a Microsoft Project custom Text field (e.g., Text3) as a comma-separated list, or to an Outline Code field if the destination org uses Outline Codes for categorization. The customer selects the tagging strategy during scoping.

Tability dashboards are saved view configurations with chart layout and filter state that do not carry semantic data. We do not migrate dashboard layouts. Users rebuild their reporting views in Microsoft Project using built-in views, SharePoint project site dashboards, or Power BI project templates post-migration.

Tability AI-generated goal drafts and suggestions exist within the platform's AI feature layer and are not stored as structured data objects. 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. The destination platform's own AI capabilities (Microsoft Copilot in Project for the web or Planner Premium) regenerate recommendations post-migration.