Migrate from Ganttic to Microsoft Project

Ganttic Projects map directly to Microsoft Project projects. Project name, start date, finish date, and time period configuration migrate as the project baseline. Ganttic project-level Data Fields map to MS Project custom Project fields (Field type = Project Custom Fields). We determine during scoping whether the destination is MS Project desktop (MPP file format) or Project for the Web (cloud), which affects the file delivery format and which custom field scope applies.

Ganttic Tasks map to MS Project tasks with Name, Start, Finish, Duration, and Percent Complete preserved. Task dependencies from Ganttic's predecessor-successor relationships map to MS Project Task Dependencies (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish). Task-level Data Fields migrate to MS Project Task Custom Fields. We flag any Ganttic Tasks with mandatory Data Fields to ensure required validation is not enforced on MS Project import unless the customer explicitly requests it.

Ganttic Resources map to MS Project Resources. Ganttic distinguishes resource types (People, Equipment, Rooms, Vehicles, Other) — we map People to MS Project Work resources with Max Units; Equipment, Rooms, Vehicles, and Other map to MS Project Material resources or Generic resources with a custom resource type field. Resource Data Fields migrate as MS Project Resource Custom Fields. Active resources migrate; archived resources are excluded from the standard migration unless the customer requests otherwise, which reduces Ganttic plan cost post-migration.

Ganttic implements Milestones as date-type Data Fields attached to Projects rather than as a distinct object type. We extract every Ganttic Data Field where field_type equals 'Date' and the field name contains 'milestone', 'milestone', or is flagged as a milestone indicator during discovery. These convert to MS Project Milestone tasks (Duration = 0) with the milestone date as the task Start and Finish. We preserve the original Ganttic Data Field label as the MS Project task Name.

Ganttic's nine Data Field types map to MS Project custom field types: Ganttic Text maps to Text, Number to Number, List to Outline Code or enterprise custom field with lookup table, Multi-Select to Text or multi-value outline code, Date to Date, and Boolean/Flag to Flag. We build the MS Project enterprise custom field schema during the configuration phase, including lookup table creation for List and Multi-Select fields, before any project records import.

Task-level Data Fields from Ganttic migrate to MS Project Task Custom Fields following the same type-mapping rules as Project Data Fields. We pre-create the custom field definitions in MS Project before task import. Any picklist values from Ganttic List and Multi-Select fields are seeded into the MS Project lookup tables during configuration. Ganttic's per-user visibility rules on Data Fields do not migrate; MS Project handles field visibility through Views, and we configure view-level custom field display during migration.

Resource Data Fields from Ganttic (commonly used for department, skillset, location, role, cost rate) map to MS Project Resource Custom Fields. We map the field values to the appropriate MS Project resource type: Text fields for role or department, Cost fields for hourly rate, and Flags for skill or certification flags. Resource grouping hierarchies from Ganttic map to MS Project Resource Groups or to a custom resource-level text field that replicates the grouping structure.

Ganttic allows resources to be grouped by any Data Field value, including nested groupings (e.g., Department > Location > Team). We preserve this structure by mapping the top-level group to MS Project Resource Groups and nested groups to a custom Resource Text field formatted with the full hierarchy path. We capture the grouping depth during discovery and present the mapping strategy (flat group vs hierarchical text field) as a choice to the customer before migration.

Ganttic assigns resources to tasks directly; MS Project assigns resources to tasks with assignment units and work values. We convert Ganttic's resource booking percentage (e.g., 50% on a task) to MS Project assignment Max Units. Where Ganttic records a resource booking without explicit hours, we estimate work using the resource's standard calendar hours multiplied by the task duration and assignment percentage. We flag any Ganttic booking where the resource is assigned to more than one overlapping task, as this requires leveling review in MS Project.

Ganttic Reports are exported as CSV during discovery to capture calculated metrics and summaries that exist only in the report views. We do not migrate Ganttic Reports as native MS Project reports — MS Project reports are rebuilt in the Microsoft 365 reporting stack (Power BI, Microsoft Project for the Web built-in reports) using the migrated data. We deliver the CSV report data as a supplemental dataset that the customer's analyst imports into Power BI or Excel for post-migration reconciliation.

Ganttic Custom Views define per-view time periods, groupings, and filtering criteria that do not have a direct MS Project equivalent. We export View configurations as part of discovery and map them to MS Project Views (Gantt Chart, Task Sheet, Resource Sheet, Calendar) and grouping/sorting settings. Timeline zoom levels and custom columns from Ganttic views map to MS Project view column configurations. The customer rebuilds any Ganttic-specific filtering as MS Project grouped views post-migration.