Migrate from Mosaic to Microsoft Project

Mosaic Projects map to Microsoft Project project files or Project Online project records. We extract project name, status, start and end dates, budget figures, and client association from Mosaic and map them to Project Name, Project Summary Task, and Summary Task custom fields in Microsoft Project. The Work Breakdown Structure (WBS) comes from Mosaic's phase and sub-phase hierarchy, which translates to summary tasks and indented tasks in Microsoft Project. Active versus archived status maps from Mosaic's project status field to the project IsActive flag in Project Online or the task active/inactive state in desktop MPP files.

Mosaic Client records hold the organization name, primary contact, and billing information. Microsoft Project does not have a native Client object. We map client name to a custom Enterprise Project field (Client Name, text type) on the project summary row, and client billing address to a custom text field. If the customer uses Project Online with SharePoint, we map clients to SharePoint Project Site groups or a connected Dynamics 365 CRM Contact record as an external reference. Client-to-project association is preserved through the project-level custom field lookup.

Mosaic Phases subdivide projects into logical stages with names, date ranges, and phase-to-project relationships. Each Phase maps to a Summary Task in Microsoft Project with the Phase Name as the task name and the Phase date range pre-populating the task Start and Finish dates. Phase-level budget data maps to custom numeric fields on the summary task. Nested sub-phases translate to child Summary Tasks within the hierarchy. We preserve the full phase hierarchy as a WBS code structure in Microsoft Project so sorting and filtering by phase remains intact post-migration.

Mosaic Employee records pulled from integrated HRIS systems include names, departments, roles, start dates, and salaries. We map Employee Name to Microsoft Project Resource Name, Department to the Resource Department field, and Max Units to the resource's maximum availability percentage. Compensation fields (base salary, billing rate) from Mosaic's HRIS integration map to the Resource Sheet Standard Rate and Cost fields. Currency handling is verified during scoping since Mosaic may store compensation in a single currency while Microsoft Project's resource rate fields are currency-agnostic. Active versus inactive employment status maps to the resource's Active/Inactive flag.

Mosaic Time Entries log hours against a specific employee, project, and date with an associated billing rate. We map each Time Entry to a Resource Assignment in Microsoft Project with the Hours value assigned to the matching Task and Resource. The Time Entry date becomes the Assignment Finish or the corresponding task date segment. Actual hours and remaining hours on the assignment are updated to reflect the imported time data. For Project Online targets with timesheet integration, assignments appear in the user's timesheet view. Billing rate from Mosaic maps to the Assignment Billing Rate custom field if the customer uses Project Online with billing extensions.

Mosaic Custom Metrics use user-defined formulas for variance analysis and KPI tracking. Microsoft Project custom fields support formula-based calculations using field references but do not replicate Mosaic's full formula syntax. We evaluate each Mosaic formula during scoping, flag unsupported functions (any non-arithmetic or non-date operators not supported by Microsoft Project), and recreate equivalent calculated fields in Microsoft Project or document the formula logic for manual configuration. Complex multi-step formulas that cannot be represented in Microsoft Project are documented in a Formulas Inventory delivered alongside the migration, with a note that the customer admin should validate output values post-import.

Mosaic's native Gusto integration pulls employee and compensation data automatically via OAuth. This OAuth connection and the refresh token do not transfer to Microsoft Project. We export the integration configuration during scoping — including which fields sync, at what frequency, and which Mosaic properties they map to — so the customer can re-establish the connection via Microsoft Dataverse, Power Automate, or a third-party connector such as a Gusto-to-Microsoft 365 integration. No integration credentials migrate; the customer must authorize the new connection in their destination environment.

Mosaic integrates with Deltek products for project accounting and time-tracking. When migrating from a Hosted integration to a Cloud integration, Mosaic requires a stored procedure to be added to the Deltek product for future time entry sync to function. We document the stored procedure requirement, coordinate with the customer's Deltek administrator post-migration, and flag that if the stored procedure is not installed, future time entries from Deltek will not sync to the connected Microsoft Project or Mosaic cloud environment. This is a post-migration configuration step outside the core data migration scope.

Mosaic variance analysis reports and chart configurations are stored in the application layer and cannot be programmatically exported. We do not migrate reports. We deliver a Report Inventory document listing every Mosaic report with its filters, date ranges, chart type, and underlying data sources, so the customer's admin can rebuild equivalent reports in Microsoft Power BI connected to the migrated Project Online data or in Microsoft Project desktop with custom views. This inventory also serves as the baseline for validating that post-migration reports produce consistent results.

Mosaic consolidates multi-source financial data into a unified FP&A view used for board-level reporting. Microsoft Project does not have a native board-level reporting dashboard. We export the data sources and field mapping used in each Mosaic dashboard, then recommend rebuilding in Power BI with data pulled from the migrated Project Online data via the Power BI Microsoft Project Online content pack or via direct API connection. The Report Inventory document covers the full dashboard scope so no board-level report configuration is lost in the transition.