Migrate from Gauss Box Projects to Microsoft Project

Gauss Box Projects map directly to Microsoft Project project files (MPP) or Project Online projects. We preserve the project name, start date, finish date, phase structure, and budget fields. Each Gauss Box project becomes one Project Online project with its own schedule. Multi-phase Gauss Box projects preserve phase ordering through Project Online outline phases or milestone groupings.

Gauss Box Tasks map to Microsoft Project tasks with Task Name, Start, Finish, Duration, and % Complete transferred directly. The Gauss Box status field (active, on hold, completed) maps to Project status codes. Gauss Box priority values transfer as custom fields or flags if the destination Project Online org enforces priority-based filtering. Dependencies created in Gauss Box via the Gantt interface translate to predecessor-successor links (FF, FS, SF, SS) in Microsoft Project.

Gauss Box subtasks under a parent task map to Microsoft Project summary tasks. The parent-child hierarchy in Gauss Box becomes the Project outline structure. Summary task Start and Finish dates are rollups of child task dates, and % Complete rollup is computed from child task completion rates. We validate that the subtask ordering is preserved within the outline level during import.

Gauss Box project phases map to outline phases in Microsoft Project (summary tasks without duration at the project level) or to milestone tasks if the phase represents a key deliverable with a specific date. Phase start and end dates transfer as task constraints. We confirm the customer's use of phases during discovery to determine whether phase-level rollup reporting in Project Online or Power BI is needed.

Gantt chart data in Gauss Box is backed by task start and end dates, duration estimates, and manually or automatically set dependencies. We extract these as task-level date fields and predecessor-successor relationships. Microsoft Project recalculates the schedule on open based on dependencies and constraints, so we set a Baseline immediately after import to preserve the original Gauss Box timeline before any Project-level rescheduling modifies the dates.

Kanban board columns and card positions in Gauss Box have no native equivalent in Microsoft Project, which is Gantt-centric. We extract the task names and column assignments and document the column-to-status mapping. The customer chooses whether to re-create a Kanban view in Microsoft Planner (for lighter-weight task management) or to accept that card ordering is reconstituted as a filtered Group By in Project Online. Card ordering within columns does not persist unless a custom column is added to preserve the order value.

Gauss Box automatically tracks time entries on tasks with billable and non-billable flags, time estimates, and actuals. These map to Project assignment notes on the task-resource pair, or to a custom Number field capturing total logged hours if the destination org does not use the Resource Usage view. Budget comparison data from Gauss Box becomes a custom cost field. We flag whether the customer uses billable time for client reporting, as Project Online requires the cost tracking feature to be enabled at the SharePoint site collection level.

Gauss Box comments attach to tasks and projects with author name and timestamp. We map comment body text to the Microsoft Project task Notes field, author name to a custom Text field, and timestamp to the Notes metadata. If comments contain @mentions or formatted content, we strip to plain text for the Notes field. Threaded comment chains in Gauss Box flatten into a single Notes block in chronological order.

File attachments from Gauss Box tasks and projects are exported and uploaded to the corresponding Project Online SharePoint document library. The file name and link reference are preserved. Because Gauss Box storage is tiered and the destination SharePoint library is tied to the Microsoft 365 tenant's allocated storage, we inventory total file volume during scoping and confirm whether the destination tenant has sufficient capacity before migration. Files without a clear task assignment are uploaded to the root project folder.

Gauss Box Custom Fields built through the attribute set system map to Microsoft Project Enterprise Custom Fields. The customer-defined attribute names and field types (text, number, date, dropdown) are inventoried during discovery and matched to the equivalent Project Online custom field type. Lookup table custom fields in Gauss Box map to Project lookup tables. We note that Gauss Box attribute sets can vary per project, so the full schema inventory may reveal different field sets per project that require separate custom field provisioning.

Gauss Box users with department assignments map to Microsoft Project resources on the Resource Sheet. The resource name, email, and department map to Resource Name, Material Label, and Group respectively. We create resource assignments by matching Gauss Box task assignees to the resolved Project resource records. Department-level resources in Gauss Box may represent team pools that need to be split into individual resources or kept as department-level assignments depending on the customer's resource management approach in Microsoft Project.