Migrate from Ganttic to Asana

Ganttic Projects map directly to Asana Projects. Project name, description, start date, and end date transfer as Project name, Project Notes, and start/completion dates. Ganttic's time period and shift operations are captured as date metadata. Projects with no assigned Resources map to Projects with no Members in Asana initially, to be populated during team onboarding.

Ganttic Tasks map to Asana Tasks within the corresponding Project. Start date, due date, and any Task-level Data Field values transfer directly. Task assignees in Ganttic (which reference Resources) must resolve to Asana Members; see Resource mapping for the non-human Resource handling strategy. Tasks without assignees in Ganttic become unassigned Tasks in Asana pending team assignment.

Human Resources in Ganttic (people, employees, contractors) map to Asana workspace Members. We resolve by email address where available, and create Member invitations for any human Resource without an existing Asana account. The customer's admin provisions Asana seats for the migrated Members post-migration, as Asana licenses are per-seat.

Ganttic Resources can be rooms, vehicles, machinery, or equipment. These do not map to Asana Members. We map them by converting each unique non-human Resource type to a Project-level Section (for room/vehicle assignments on a per-task basis) or to a custom Multi-Select field (Equipment Type, Room Booking) that the customer's admin pre-seeds with the available values before import. The customer chooses the strategy during scoping.

Ganttic Resource Data Fields (department, skillset, location, role) map to Asana custom fields on Projects or as workspace-level custom fields if the same field applies across all Projects. List and Multi-Select Data Field values require pre-seeding as picklist options in Asana before any records import. We extract all unique List and Multi-Select values during discovery and generate a seed script for the customer's Asana admin.

Ganttic Project Data Fields (nine types) map to Asana custom field types by type: Text to Text, Number to Number, Date to Date, List to Dropdown, Multi-Select to Multi-Select. Required field flags from Ganttic carry over as required validation in Asana custom fields, though Asana enforces required at the task level differently than Ganttic's per-field per-object model.

Ganttic Task Data Fields follow the same nine-type system as Projects and Resources. We perform type-aware mapping and flag any task fields marked as mandatory in Ganttic to ensure required validation is replicated in Asana. Multi-Select and List values are pre-seeded in Asana before import, same as Resource and Project Data Fields.

Ganttic Milestones are implemented as date-type Data Fields on Projects rather than a distinct object. We convert them to Asana's native Milestone feature: the milestone date becomes the Milestone's Due Date, and the milestone name comes from the Data Field label. This conversion is available from Asana Premium ($10.99/user/month); teams on Asana's free tier will see Milestones as regular Tasks marked complete, and we document this tier constraint in the scope.

Ganttic Resources can be grouped by any Data Field value, creating nested group hierarchies for resource pool visualization. Asana does not have a native resource grouping model. We map these to Asana Tags on Tasks (for ad-hoc grouping) or to custom fields (Department, Team, Location) depending on whether the grouping represents a planning attribute (custom field) or a collaborative tag (Tag). Nested Ganttic hierarchies flatten to top-level groups with a naming convention preserved.

Ganttic Custom Views define per-view time periods, groupings, and filtering criteria. Asana's Portfolio view provides high-level project status, progress, and due-date tracking across Projects but does not replicate Ganttic's resource-centric grouping. We export View configurations during discovery and map them to a written View-equivalent document: which Projects are included, what time period is active, and what grouping applies. The customer's admin recreates these as Asana Portfolios or filtered Project lists.

Ganttic Reports export as CSV or PDF and may contain calculated fields, utilization summaries, and capacity metrics that exist only in the view. We extract CSV exports during discovery and map them to a written report inventory. Asana's native reporting (Dashboard, Custom Fields, progress tracking) is available from Premium tier. We do not migrate Ganttic Reports as live Asana Dashboards; we deliver the report definitions for the customer's admin to rebuild as Asana Dashboards or to continue using in a BI tool.

Ganttic's shift feature moves an entire Project and all its Tasks along the timeline. This action cannot be automatically reverted in Ganttic (per Ganttic documentation). We capture the pre-shift state of all Project dates during discovery export so the Ganttic instance remains undisturbed during parallel-run validation. The shift dates themselves are recorded as metadata and applied as the final Project start/end dates in Asana, preserving the migrated timeline accurately.