Migrate from Mosaic to monday Work Management

Mosaic Projects (the primary planning containers holding budget, revenue, and resource allocation) map to monday.com Boards. The project name becomes the board title, project status maps to a Status column, start and end dates map to Date Range columns, and project-level budget figures map to Number columns configured for currency formatting. Each Mosaic Project becomes one monday.com Board organized by a workspace-level folder structure that mirrors Mosaic's project hierarchy.

Mosaic Client records (organization name, contact details, billing information, client-to-project association) map to monday.com Contacts (if using monday.com CRM) or to item-level text and link properties on the project board. Client name maps to a Text column, billing contact email maps to an Email column, and the client-to-project relationship is preserved as a Connect Boards column linking the project board to a client-facing board. Customers using monday.com without CRM use item grouping by client name as the organizational equivalent.

Mosaic Employee records (names, departments, roles, start dates, salaries pulled from Gusto and HRIS integrations) map to monday.com Users for user management and to People column values on Items for assignment. Compensation fields (salary, billing rate, cost rate) map to Number columns configured per employee record; however, salary data in monday.com is visible to workspace members by default, so we recommend using a dedicated numeric column with restricted view permissions or storing compensation as cost rate and billing rate only. Department and role map to Tags or Status columns on the employees board.

Mosaic Time Entries (employee, project, date, hours, billing rate) map to monday.com Items on the project board using Time Tracking columns. Each time entry becomes an Item with the employee assigned via a People column, the hours logged via the Time Tracking column, and the date preserved from the original entry. Billable vs non-billable flag from Mosaic maps to a Status or Tags column. Billing rate is stored as a Number column on the item or inherited from the employee's billing rate. monday.com's native time tracking requires Pro plan or higher.

Mosaic Phases (logical stages within a project with names, date ranges, and phase-to-project relationships) map to monday.com Groups within the project Board. Phase name becomes the Group title, phase start and end dates map to Date columns on items within the group, and phase-level budget maps to a Number column on the group header or a summary item. Phase ordering within the project is preserved by group sequence order in the board.

Mosaic Custom Metrics (user-defined formulas for variance analysis and KPI tracking) do not transfer as executable code into monday.com. We evaluate each formula during scoping, map supported functions to monday.com Formula column syntax (which supports arithmetic, date calculations, and conditional logic), and flag unsupported functions. Complex multi-step formulas requiring iteration, advanced statistical functions, or cross-board references are documented in a written inventory with recommended Formula column equivalents and manual validation steps. Customers rebuild these in monday.com post-migration.

Mosaic project budget figures (planned budget, actual spend, variance) map to monday.com Number columns configured for currency on the project board. Budget totals are stored as a Number column per budget item; actual spend is computed by summing time entry hours multiplied by employee billing rates using a Formula column. Variance calculates as budget minus actual using Formula column arithmetic. Customers with budget tracking needs should consider monday.com's reporting views for variance visualization.

Mosaic project hierarchies (parent projects and sub-projects) map to monday.com folder and board nesting. Parent projects become top-level folders; child projects become boards within those folders. The hierarchy relationship is preserved by folder structure rather than a native parent-child link. If Mosaic uses project groupings by client or portfolio, these map to monday.com Workspace or folder-level organization with boards as the project-level container.

Mosaic's native Gusto and HRIS integrations store OAuth credentials and sync configuration in Mosaic's platform layer; these tokens do not transfer to monday.com. We document the integration configuration (which HRIS was connected, sync frequency, which Mosaic fields mapped to which HRIS fields, and which employee data was pulled) in a written integration reference document. The customer uses this to re-establish the connection in monday.com using a supported integration (Gusto via Zapier or Make, or a direct monday.com HRIS integration if available) with the same field mapping.

Mosaic integrations with ERPs and other business systems store field-level mapping configuration that is not portable. We export integration mapping metadata as a reference document listing source field, destination field, transformation logic, and sync direction for each integration the customer had active. This document serves as the specification for rebuilding the same integrations in monday.com or a separate middleware layer post-migration.

Mosaic variance analysis reports and chart configurations are stored in the application layer and cannot be programmatically extracted. We do not migrate reports as code. We deliver a written report inventory documenting each Mosaic report's purpose, underlying data sources, chart types, and column layout, with recommended monday.com Dashboard widget equivalents. The customer rebuilds reports in monday.com's Dashboard and Explore views post-migration.

Mosaic does not expose automation logic through its data model, and monday.com's automation builder uses a different trigger-action infrastructure. We do not migrate automations as code. We deliver a written automation inventory documenting each Mosaic workflow's trigger, conditions, and actions with recommended monday.com Automation equivalents. Customers with complex automations or Mosaic's integration-based workflows rebuild them in monday.com's Automation center or transition to the new Workflows infrastructure (April 2026 deadline) post-migration.