Migrate from GanttPRO to Microsoft Project

GanttPRO Projects map directly to Microsoft Project files (MPP) or Project Online/Project for the Web projects. We preserve project name, description, start date, and the auto-scheduling toggle. GanttPRO's duration step (hours/days/weeks/months) maps to Microsoft Project's calendar and task mode settings. The project-level working day configuration maps to Microsoft Project's calendar (Project Calendar in desktop, Working Days in Project Online). Multi-project migrations in GanttPRO are handled as individual MPP files or as separate projects in the destination Project Online site.

GanttPRO Summary Tasks map to Microsoft Project Tasks with the Summary flag set to Yes. The parent-child hierarchy is reconstructed using Outline Level and WBS code fields in Microsoft Project. We preserve the summary task name, start and end dates (rolled up from subtasks), and the Summary checkbox. When subtasks are indented under a summary task in GanttPRO, we generate the matching indentation structure in Microsoft Project's task hierarchy.

Standard GanttPRO Tasks map directly to Microsoft Project Tasks with all standard fields preserved: Task Name, Start, Finish, Duration, Duration Type (elapsed/actual), Priority, Status, and the Notes/Description field. Task color coding from GanttPRO maps to Microsoft Project's Text 1-8 or Flag fields, which can be used for visual categorization in the destination. Task-level percent complete and physical percent complete migrate to the corresponding Microsoft Project fields.

GanttPRO Subtasks map to Microsoft Project Tasks nested under their parent Summary Task. We preserve subtask-level dates, assignees, and any custom field values. Subtask numbering from GanttPRO (which reviewers on Capterra cite as a standout feature) does not have a direct Microsoft Project equivalent; we generate WBS codes that replicate the numbering structure during migration. Flattening subtask hierarchies is not required because Microsoft Project supports the same parent-child nesting model as GanttPRO.

All four GanttPRO dependency types (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map directly to Microsoft Project predecessor types. GanttPRO uses the successor task bar or task settings to define dependency types; Microsoft Project uses the Predecessors field with type codes (FF, FS, SF, SS). We translate each dependency, flag any circular reference detected during import, and preserve lag time and lead time values as offset days in the predecessor string. The orange arrow visualization from GanttPRO does not migrate; it is a GanttPRO UI rendering artifact.

GanttPRO project members (human users assigned to tasks) map to Microsoft Project Work Resources. We map the member name, email (for cross-reference), and the Max Units value. GanttPRO's resource workload percentages map to Microsoft Project's resource assignment units. Where GanttPRO assigns a cost rate to a project member, we map that to the resource's Standard Rate in Microsoft Project. Resource calendars in Microsoft Project (working time exceptions per resource) can be populated from GanttPRO working day settings if those are resource-specific.

GanttPRO virtual resources are role-based placeholders with assigned cost rates but no associated user account. Microsoft Project does not have a virtual resource concept; all resources are actual. We convert virtual resources to Microsoft Project Work Resources using the virtual resource's name, role description, and cost rate. We flag virtual resource conversions in the migration report because cost calculations in Microsoft Project depend on the Standard Rate and accrue against the project budget differently than in GanttPRO's automatic budget mode. The customer's admin should review budget totals after migration for any variance introduced by the conversion.

GanttPRO custom fields (available on Advanced tier+) are available in nine types: Text, Number, Date, List, Checkbox, Color, Multiselect, People, and Label. Microsoft Project custom fields support a narrower set of types. We map Text to Text, Number to Number, Date to Date, Checkbox to Flag, and List to Text (since Microsoft Project does not have a dropdown custom field equivalent at core; Enterprise tier or Project Online with Project Client is required for enterprise custom fields). Color, Multiselect, People, and Label types from GanttPRO are mapped to Text or Flag fields with the original value preserved as a string. We flag field types that cannot map directly so the customer can decide whether to accept text representation or restructure the field in Microsoft Project.

GanttPRO Portfolios group multiple projects for high-level monitoring. Microsoft Project has no native portfolio object in the desktop application or Project for the Web at the base tier. We extract portfolio membership (which projects belong to which portfolio) and deliver it as a written reference list. For organizations with Project Online Plan 5 or Project Server, the portfolio view can be reconstructed using the Project Web App portfolio dashboards. For Project for the Web, Power BI or a SharePoint site structure can replicate the portfolio monitoring view.

GanttPRO Time Logs record hours worked against tasks with date, user, and optional comment. Microsoft Project does not have a native time-tracking object in the desktop application; timesheets require Project Server or Project Online with timesheet functionality enabled. We map time log entries to task assignment notes (as text: 'Time logged: X hours on Y date') or to a custom Timesheet Hours field on the task if the destination is Project Online with a timesheet-enabled site. Note that GanttPRO time log export is only available in XLSX format, so we convert the XLSX export to structured records during the extraction phase. Planned work hours from task assignments are preserved separately from logged time.

GanttPRO supports automatic budget calculation (derived from resource rates and estimated hours) and manual budget entry. Where GanttPRO uses automatic mode, we extract both the calculated budget value and the underlying resource rate and hours data. In Microsoft Project, budget tracking requires the Project Summary Task with a Budget Cost field (available in Project Professional or Project Online with Project Plan 3+). We map GanttPRO's project-level budget to the Microsoft Project Budget Cost field, and task-level costs to assignment cost fields. Virtual resource costs migrate with the resource conversion as described above.

GanttPRO saved filters (available on Advanced tier+) define task views by name, type, assignee, status, priority, date range, color, and custom fields. Microsoft Project Views store column, grouping, and filter configurations per project. We extract the filter definitions and deliver them as a written view specification document with the column order, sort order, grouping, and filter criteria for each saved filter. The customer's admin rebuilds the views in Microsoft Project using the View Definition dialog. Note that GanttPRO's Board View has no Microsoft Project equivalent; we note this in the gap analysis.