Migrate from Ganttic to Jira

Ganttic Resources are typed as people, rooms, vehicles, equipment, or custom asset categories. Human Resources with email addresses map to Jira User accounts. Non-human Resources (equipment, rooms, vehicles, facilities) do not have a native Jira equivalent; we model them as Jira custom field values using a single-select or multi-select custom field with the resource names as options. This requires pre-seeding the picklist before Task import so that assignee and resource allocation fields validate correctly.

Ganttic Resources can be grouped by any Data Field value, creating nested group hierarchies. We preserve these hierarchies by mapping top-level groups to Jira Groups and sub-groups to a custom field on the User record. If the grouping logic references non-human Resources, we use a cascading custom field structure instead.

Ganttic Projects map directly to Jira Projects. We preserve Project name, description, start and end dates, and the full Data Field set. The Ganttic Project time period (start/end dates) maps to the Jira Project's start date and the default fix version target date. If multiple Ganttic Projects map to a single Jira Project, we create Jira issue type schemes to separate the data while sharing configuration.

Ganttic Tasks map to Jira Issues with issue type determined during scoping. Tasks with deliverables map to Stories; Tasks with discrete actions map to Tasks; Tasks flagged as blockers or quality items map to Bugs. We preserve Task start/end dates, assignees (resolved via the resource-to-user mapping), and all Data Field values. Parent-child Task relationships in Ganttic map to Jira sub-task links or Jira Issue Hierarchy.

Ganttic Milestones are implemented as date-type Data Fields on Projects rather than a distinct object. We convert them to Jira Fix Versions (Releases) with the milestone name as the version name and the milestone date as the release date. If a Ganttic Project has multiple milestones, we create one Fix Version per milestone and link related Issues using the Fix Version field.

Ganttic Project-level Data Fields map to Jira Project-level custom fields. The nine Ganttic Data Field types map to Jira equivalents: List maps to Select, Multi-Select maps to Multi-Select, Number maps to Number, Text maps to Text Field, Date maps to Date Picker. We pre-create the custom field in Jira during schema design and assign it to the relevant Issue Type Scheme so it appears on the correct issue types.

Ganttic Task-level 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 enforced in Jira. List and Multi-Select picklist values must be pre-seeded in Jira before record import; we generate a pre-migration seed script for these fields during discovery.

Resource Data Fields store custom information like department, skillset, location, or role. Human Resource Data Fields migrate as custom fields on the Jira User record (if Jira Data Center or Server with User Management enabled) or as custom fields on Issues. Non-human Resource Data Fields migrate as custom fields on the Jira Issues they relate to, preserving the resource's custom attributes in the destination system.

Ganttic Custom Views define per-view time periods, groupings, and filtering criteria. We export View configurations during discovery and map them to Jira Saved Filters (JQL queries capturing the same filter logic) and Jira Boards (Kanban or Scrum). The time period and grouping logic may require adjustment because Jira's time-based filtering uses different primitives (sprint dates, fix version dates) than Ganttic's timeline windows.

Ganttic Reports export as CSV or PDF during discovery. We extract calculated metrics and summaries from CSV exports and map them to Jira Dashboard Gadgets (pie charts, bar charts, statistics gadgets) where structurally equivalent. Any report that exists only in a Ganttic view (calculated in real time, not stored as data) is flagged as a non-migratable artifact and listed in the handoff document for the customer's admin to rebuild as a Jira Dashboard.