Migrate from GanttPRO to Asana

GanttPRO Portfolios group multiple projects for high-level monitoring. Asana Portfolios (Business tier and above) provide a similar cross-project view with progress and workload tracking. We migrate portfolio membership and project-level metadata (project name, status, owner) into Asana Portfolio items. If the customer is on Asana Free or Premium (no native Portfolio), we map portfolio groupings to a top-level Project-within-Project structure or a tag-based grouping strategy, agreed during scoping.

GanttPRO Projects map directly to Asana Projects. We preserve the project name, description, start date, and auto-scheduling toggle. GanttPRO's duration step (hours/days/weeks/months) is set per project; Asana Timeline infers duration from start and due dates. Project color coding migrates as a custom field in Asana if the customer uses color for status tracking.

GanttPRO Summary Tasks are parent rows that group related subtasks and display roll-up progress. We map Summary Tasks to Asana Sections (if the summary task has no dates of its own) or to a parent Task (if the summary task has independent start/end dates and progress). The choice is made per Summary Task based on whether it carries its own date values in GanttPRO. Subtasks under each Summary Task are imported as Asana Subtasks of the corresponding parent.

Standard GanttPRO Tasks map to Asana Tasks with all standard fields preserved: title, description, start date, due date, status, priority, assignee, and progress percentage. We set Asana's Start Date and Due Date fields from GanttPRO start_date and end_date properties. Task color coding migrates to a custom field if used for classification rather than status.

GanttPRO Subtasks nested under Summary Tasks map to Asana Subtasks. The parent-child relationship is preserved by setting the Asana parent Task reference at import time. Subtasks carry their own dates and assignments in GanttPRO; these migrate as Asana Subtask start and due dates and assignee assignment.

All four GanttPRO dependency types (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) are extracted from the GanttPRO API. Asana's native Timeline supports Finish-to-Start dependencies directly. Start-to-Start, Finish-to-Finish, and Start-to-Finish dependencies are imported using Asana's dependency attachment API (dependency_type field) and validated after import. We flag any circular dependency chains detected in the GanttPRO data before import to prevent broken Timeline arrows in Asana.

GanttPRO project members who correspond to real user accounts map to Asana project Members. We match by email address across the two systems. Member-level permissions (Admin, Member, Viewer) are approximated from GanttPRO's role assignments, with the customer's admin confirming the final permission structure in Asana since the role models differ.

GanttPRO virtual resources are role-based placeholders with assigned cost rates and no corresponding user account. They do not migrate automatically to Asana because Asana has no virtual resource concept. We extract virtual resource assignments as a task-level note on each affected task and provide a written conversion map during scoping: each virtual resource must be assigned to a real Asana user or team before the migration runs. If the virtual resource carried a cost rate used in GanttPRO budget tracking, we map it to a custom numeric field on the task or project for the customer's budget tracking to continue in Asana.

GanttPRO custom fields (text, number, dropdown, date, checkbox, user) on the Advanced tier and above are extracted per project. We pre-create matching custom fields in the Asana workspace before any task data is imported, using the same field label and type where possible. GanttPRO dropdown options map to Asana enum options; GanttPRO user-picker fields map to Asana members custom fields. If a GanttPRO field type has no direct Asana equivalent, we choose the closest Asana type and document the mapping in the field inventory.

GanttPRO time logs (date, user, hours, optional comment per task) map to Asana time entries on Business and Enterprise plans. We export time logs via GanttPRO's XLSX export (the only available format) during scoping, then convert to Asana time tracking entries by matching the task name and date range. Time log export in GanttPRO defaults to the current month; we explicitly request the full project date range during scoping to avoid silent data loss.

GanttPRO workload snapshots display resource allocation in hours, percentages, or task-count mode. We extract workload data per resource and project. Asana's Workload view (Business tier) requires a user-level assignment; we map GanttPRO resource workload to Asana project Member workload by matching real user assignments. Virtual resource workload is included in the virtual resource conversion map.

GanttPRO budget calculations derive from resource cost rates and estimated hours. We extract both the calculated budget values and the underlying resource-rate assumptions. Since Asana has no native budget object, we create numeric custom fields (Budget Estimate, Actual Cost, Estimated Hours) at the project level and populate them from the GanttPRO export. The customer's finance team uses these fields in Asana reporting or exports them to a spreadsheet tool for detailed budget tracking.

GanttPRO project calendars define working days, holidays, and exceptions per project. We export these as working-day configurations and map them to Asana's working-day settings at the workspace level. Asana does not support per-project working-day calendars; a single workspace-level working-day configuration applies to all projects. We flag this limitation during scoping and recommend the customer choose the most commonly used calendar or configure a project-specific note field.

GanttPRO custom project templates (task hierarchy, dependencies, custom field configurations) are documented as a structural inventory during migration scoping. Asana does not have a native template import feature beyond duplicate-project. We deliver a written template map describing the original GanttPRO template structure so the customer's admin can recreate it in Asana by duplicating a migrated project or using Asana's template library.

GanttPRO saved filters (by task name, type, assignee, status, priority, date range, color, custom fields) are extracted per project. Asana's saved views serve a similar function. We document each GanttPRO filter configuration and its Asana equivalent (filter by field, sort order, grouping) in the migration handoff. Asana's saved views are project-scoped and must be recreated manually in each destination project.