Migrate from TeamGantt to Asana

TeamGantt Projects map to Asana Projects at the individual level. For organizations with multiple parallel projects that share resource pools, we can group related Asana Projects into a Portfolio for portfolio-level tracking. The TeamGantt project-level custom fields (e.g., client name, project type, budget code) migrate to Asana custom fields at the project level. Note that TeamGantt infers project start and end dates from the earliest and latest task dates; Asana allows explicit project start/end dates that we set from the same inference during migration.

TeamGantt Tasks map directly to Asana Tasks with name, description, start date, due date, duration, and percent complete preserved. The TeamGantt task-level custom fields map to Asana task-level custom fields. Subtasks in TeamGantt (Groups) map to Asana subtasks, preserving the parent-child nesting depth. Assignee assignments carry over by resolving TeamGantt user email to Asana member. Note: TeamGantt allows multiple assignees per task; Asana allows exactly one assignee per task, so tasks with multiple assignees spawn duplicate task records with the same details and one assignee each, flagged with a _multi_assignee suffix in the name.

TeamGantt task dependencies map to Asana dependency links preserving the predecessor-successor relationship. Finish-to-Start (FS), Start-to-Start (SS), Start-to-Finish (SF), and Finish-to-Finish (FF) dependency types migrate directly. Lag time values transfer as day offsets on the successor task. We sequence the migration so that predecessor tasks insert before successors to avoid Asana throwing orphan-reference errors. Asana requires Premium or higher for the dependency feature; we verify the destination workspace plan tier during scoping and flag if the migration would exceed the Free-tier dependency limit.

TeamGantt Milestones map to Asana Tasks with the Milestone subtype. The milestone name, date, and project association migrate. Asana renders milestones as diamond markers in Timeline view, matching TeamGantt's zero-duration diamond visualization. If the destination Asana workspace is on a Free plan (which does not support Timeline), milestones migrate as regular tasks with a custom field Milestone_Date set to the original milestone date and a tag _milestone for manual conversion by the admin in the paid-tier Timeline view.

TeamGantt Baselines capture a snapshot of the originally planned schedule for comparison against actual progress. Asana has no baseline feature. We export all saved baselines as a structured CSV with task name, planned start, planned end, planned duration, and actual start/end for each baseline instance, and attach this CSV to the project record in Asana as a documentation reference. The customer's project management team uses this CSV for manual variance analysis.

TeamGantt time entries (tracked hours on tasks) map to Asana's built-in time tracking if the destination is on Asana Business or Enterprise. On Asana Premium, time entries map to a custom field Total_Tracked_Hours__c (number type) at the task level. We extract the total tracked time per task from TeamGantt's API or CSV export and insert it into the destination field. Hourly estimation values from TeamGantt Pro+ migrate to Asana custom fields Estimated_Hours__c and Actual_Hours__c for variance tracking.

TeamGantt Workloads report (available on Pro/Unlimited plans) exports per-user task assignments and capacity data. We map each user's assigned tasks to Asana tasks with the same assignee, and create a custom numeric field Capacity_Hours__c on the user profile if the destination supports it. TeamGantt Basic and Standard accounts do not have Workloads access; we fall back to the CSV export of task assignments by user. Note: Asana's Workload chart requires Business or Enterprise; we map workload data into custom fields that the admin can surface in a spreadsheet or third-party reporting tool if the plan tier is lower.

TeamGantt checklist items on tasks map to Asana subtasks with the checklist item text as the subtask name and the completion status preserved as the subtask completion flag. The subtask inherits the parent task's assignee and due date unless the checklist item has a specific assignee set in TeamGantt, in which case we create a subtask with that specific assignee.

TeamGantt discussion threads attached to tasks migrate to Asana task comments. Each discussion post becomes a comment entry with the original author name, timestamp, and HTML-formatted body preserved. Threaded discussions in TeamGantt maintain their reply structure in Asana's comment chain. Attachments referenced in discussions migrate as task attachments if the attachment URL is accessible; we log a note for any attachments that require re-upload.

TeamGantt Labels (used for task categorization) map directly to Asana Tags. Label names and color assignments migrate to tag name and tag color. Tasks with multiple labels in TeamGantt receive multiple tags in Asana. Asana Tags are workspace-level and reusable across projects, matching TeamGantt's label scope.

TeamGantt Users map to Asana workspace Members by email address. User display name, email, and avatar URL migrate. Guest users in TeamGantt (collaborators without full access) map to Asana Guest members with appropriate workspace restrictions. We extract the full user list during scoping and match against the Asana workspace membership; any unmatched users go to a provisioning queue for the customer's admin to create before record migration begins.

TeamGantt project-level custom fields (text, number, date, dropdown) map to Asana project-level custom fields of equivalent type. We discover field types via the TeamGantt API during scoping, pre-create the matching custom field in the destination Asana workspace, and map values during migration. Dropdown options in TeamGantt map to Asana enum options. Number and date fields map directly with type validation before insert.

TeamGantt task-level custom fields migrate to Asana task-level custom fields using the same type mapping as project-level fields. Text fields map to Asana text custom fields, number fields to number custom fields, date fields to date custom fields. If a TeamGantt custom field type does not have a direct Asana equivalent (e.g., a TeamGantt formula field), we convert to a text custom field with the computed value and note the conversion in the mapping spec.