Migrate from Mosaic to Asana

Mosaic Clients represent the organizations associated with projects. We map client records to Asana Teams (for organizational grouping of members) or to Projects (for project-level client association), depending on the customer's scoping preference. Client name becomes the Team or Project name. If Mosaic client records contain contact details and billing information, those map to Asana custom fields on the Project. The client-to-project association is preserved as a Project-level custom field referencing the client name.

Mosaic Projects are the primary planning containers holding budget, revenue, and resource allocation data. We export project metadata including name, status, start and end dates, and associated client. In Asana, the project is created with the same name and dates. Budget and revenue fields from Mosaic map to Asana custom number fields. Resource allocation data maps to custom fields or becomes a project-level task for tracking.

Mosaic Phases subdivide projects into logical stages. We preserve phase names, date ranges, and phase-to-project relationships. In Asana, each phase becomes a Section within the project. Phase date ranges map to Section header metadata or to a set of dated tasks representing the phase timeline.

Mosaic Employee records are pulled from integrated HRIS systems such as Gusto and include names, departments, roles, start dates, and salary information. We export the employee roster and map names and emails to Asana member Profiles. Departments map to Asana Teams or to custom fields on the user's profile. Compensation and salary fields do not have an Asana native equivalent; we map them to custom number or currency fields on the user's profile, or to a custom compensation Project visible only to designated admins.

Mosaic Time Entries log labor against projects and phases with employee, project, date, hours, and billing rate. We convert each time entry to an Asana Task assigned to the corresponding employee User, with the project as the parent Project. Hours and billing rate become custom fields on the task. Date becomes the task due date or start date. If Mosaic time entries span multiple phases, each phase becomes a subtask. This transformation requires resolving the employee-to-user lookup before time entry import begins.

Mosaic Custom Metrics use user-defined formulas for variance analysis and KPI tracking. We evaluate each formula during migration scoping, document its logic, and recreate equivalent Asana calculated fields or custom formula fields from Premium tier. Complex multi-step formulas may require manual verification post-import. We do not migrate formulas as executable code; we deliver a written formula inventory for the customer's admin to implement in Asana.

Mosaic project budgets contain revenue forecasts, cost budgets, and variance thresholds. These are mapped to Asana Custom Fields (number type for budget amounts) or to Project Goals at the Premium tier. The budget variance calculation from Mosaic becomes a formula field in Asana. Customers using Mosaic's budget rollup features should expect to re-implement those in Asana Goals or in a connected BI tool.

Mosaic client records may contain contact person names and email addresses separate from the client organization record. We map these to Asana Project Members (invited as guests or members to the project) or to custom fields on the project for contact tracking. This is a configuration decision made during scoping based on whether the client contact needs to receive Asana task notifications.

Mosaic employee departments map to Asana Teams. Each department becomes a Team, with employees added as members. Teams allow cross-project visibility for department members and enable workload management features in Asana Premium and Business tiers. Department hierarchies in Mosaic flatten to a single Team level in Asana unless the customer specifies a nested team structure during scoping.

Mosaic's native Gusto integration pulls live employee and compensation data. OAuth credentials and refresh tokens do not transfer across platforms. We document the integration configuration — which Gusto fields were mapped to Mosaic employee fields, sync frequency, and any field transformations applied — so the customer's admin can re-establish the connection in Asana or via a third-party integration tool. Compensation data that was synced from Gusto into Mosaic employee records migrates as part of the employee roster export.

Mosaic integrations with Deltek Vision, Vantagepoint, or Ajera (hosted or cloud) store connection credentials that do not transfer. If the customer is migrating between Deltek products within Mosaic, that is a Mosaic integration migration (handled by Mosaic's service on a 2-3 week timeline with 6-week advance notice). For migrations to Asana, we document the Deltek integration scope and field mappings so the customer can evaluate Asana-native ERP integrations or third-party connectors post-migration.

Mosaic does not expose a public export API for variance analysis reports or dashboard configurations. These are stored in the application layer and cannot be programmatically extracted. We advise customers to screenshot and document their key Mosaic reports before migration begins, and we deliver a written report inventory listing every dashboard and chart configuration as a reference for manual rebuild in Asana's reporting tools or in a connected BI platform.