Migrate from Goplan to Microsoft Project

Goplan project workspaces map to Microsoft Project plan files or Project Online projects. We preserve the project name, description, start date, target date, and status. Goplan's collaboration settings (member access levels) do not transfer to Microsoft Project's resource assignment model; we document access configuration requirements for the customer's PMO admin to rebuild in Project Online or SharePoint. If Goplan export yields multiple CSV files per project, we merge them into a single hierarchical task list before Microsoft Project import.

Goplan tasks map directly to Microsoft Project tasks with Name, Start, Finish, Duration, and Notes preserved. Goplan's task status (open, completed) maps to Microsoft Project PercentComplete or Status. Task hierarchy from Goplan (if any subtask structure) maps to the WBS outline level in Microsoft Project. We validate that task names, dates, and durations survive the CSV-to-MPP conversion without truncation or date format shift.

Goplan task assignments (which team member is assigned to which task) map to Microsoft Project resource assignments on the Task Usage view. If a Goplan task has multiple assignees, we consolidate them into the first assignee on the main task row and add the remaining assignees as notes or custom fields because Microsoft Project assigns tasks to one resource per row by default unless using the Team Planner view.

Goplan user accounts map to Microsoft Project resources. We extract user display name, email, and role from Goplan and create corresponding Resource records in Microsoft Project. If Goplan roles are present, we populate the Resource Initials and Material Label fields. Resources are created before task import so that assignment lookups resolve at migration time.

Goplan timesheet entries (per-user, per-task, per-date hours) have no native Microsoft Project equivalent because Project tracks actual work on tasks rather than submitting timesheets. We offer two migration paths: (1) map hours to Task Actual Work fields for direct schedule tracking, or (2) create a custom WorkHours numeric field on tasks and a separate Timesheet custom view. The customer chooses during scoping; we document the chosen strategy in the migration spec.

Goplan milestones map to Microsoft Project milestone tasks (Duration = 0, Milestone checkbox enabled). The milestone name and target date preserve. We validate that milestone dates align with the dependent task chain after dependency mapping.

Goplan custom fields on tasks (text, number, date, dropdown) map to Microsoft Project custom fields at the Project level or task level depending on scope. Microsoft Project Professional and Project Online support custom text, number, cost, flag, date, and start-finish fields. We extract the custom field schema from Goplan during discovery and pre-configure matching custom fields in the destination plan before data import.

Goplan project-level custom fields map to Microsoft Project summary task fields or enterprise project-level custom fields in Project Online. We map field values to the corresponding Project Summary Task rows in the MPP file or to Project Online enterprise project properties accessible via PWA.

Goplan report configurations and historical output are extracted as data exports, not as live report definitions. Microsoft Project does not store report definitions inside the MPP file. We deliver a written inventory of every Goplan report with its data source, filters, grouping, and a recommended rebuild path using Microsoft Project's Visual Reports to Excel, Power BI via OData, or Project Online reporting.

Goplan task comments are not confirmed as a separately exportable object in available documentation. If comments are present in the export (detected during discovery), we migrate them as task Notes in Microsoft Project. If comments are not extractable, we document the gap and recommend a SharePoint-based comment archive as a mitigation.

File attachments on Goplan tasks or projects are not confirmed as available in export data. During scoping, we verify whether attachment URLs or binary files are present. If present, we migrate them as linked files in the destination Project Online SharePoint document library and document the link locations in the migration inventory. If not present, we flag the gap.