Migrate from Mosaic to Trello

Mosaic Projects map to Trello Boards as the primary container. Each Mosaic Project's name, status, start date, and end date migrate to the Board name and description fields. Mosaic's project budget and revenue fields have no native Trello equivalent; we map these to Board description text or Custom Fields (number type) if the customer selects Trello Standard or Premium. Archived Projects in Mosaic map to Archived Boards in Trello. The Mosaic project-to-client association is preserved as a Trello Label with the client name for filtering across boards.

Mosaic Phases subdivide Projects into logical stages and map directly to Trello Lists within a Board. Phase names, start dates, and end dates migrate to List titles and card due dates. Mosaic Phase status (Active, Complete, On Hold) maps to List header text conventions or Labels if Trello Standard is not available. If a Mosaic Project has no Phases, we create a default List named 'Tasks' as a placeholder so the Board is not empty.

Mosaic Clients represent organizations associated with Projects. Trello has no native client or company object, so we map Clients to Trello Labels (one Label per unique client name) that are applied to all Cards belonging to that client's Projects. For organizations using multiple Workspaces in Trello, we may map high-level Clients to separate Workspaces if the customer requests a Workspace-per-client structure during scoping. Client contact details (name, email, billing address) are preserved as Card Custom Fields (text type) on key milestone Cards rather than as a standalone record.

Mosaic Employees pulled from HRIS integrations (Gusto) include names, email addresses, departments, roles, start dates, and compensation. Trello Workspace Members retain display name and email only. We map Employee email to Member email as the dedupe key, and preserve department and role as Trello Labels (one Label per unique department and role). Compensation data (salary, hourly rate, billing rate) has no Trello equivalent and is documented in the migration inventory for the customer's HR and finance teams to handle separately.

Mosaic Time Entries log hours against a Project, Phase, and Employee with date, duration, and billing rate. Trello has no native time tracking object. We map Time Entries to Card-level Checklist items with the format '[Employee Name] - [Hours]h on [Date]' or to Custom Fields (number type) if the customer is on Trello Standard or Premium. For clients requiring billable hour tracking, we create a dedicated 'Time Tracking' Checklist on each Card and summarize hours per Phase List using Checklist item counts. Historical time entry totals are preserved; detailed per-entry records require post-migration reconciliation.

Mosaic stores budget amounts at the Project level for revenue, costs, and margin targets. Trello has no financial object. We map budget revenue and cost fields to Board-level Custom Fields (number type) if available, or to Card descriptions on a designated 'Budget Summary' Card pinned to the Board. Variance between budget and actual is not natively calculable in Trello; we document the budget figures for the customer to manage in a spreadsheet or separate FP&A tool post-migration.

Mosaic Custom Metrics allow user-defined formulas for variance analysis and KPI tracking. Trello Custom Fields support checkbox, date, dropdown, number, and text types but not calculated formulas. We evaluate each Custom Metric formula during scoping: simple arithmetic metrics map to Trello Custom Fields (number type) where the customer manually enters the result; complex multi-step formulas are flagged as unsupported and documented in the migration inventory for rebuild in a separate FP&A tool. Any Custom Metric that references external HRIS data not available in Trello is excluded from the migration scope.

Mosaic Reports including variance analysis, resource utilization, and FP&A dashboards are stored in the application layer and cannot be programmatically extracted. Trello Premium offers a Dashboard view but it is not a reporting engine comparable to Mosaic's FP&A reporting. We do not migrate Reports. We deliver a written inventory of every Mosaic Report the customer has saved, including its filters, date ranges, and data sources, so the customer's admin can rebuild equivalent views in Trello Premium Dashboard or an external BI tool.

Mosaic maintains native integrations with Gusto and other HRIS platforms that pull live employee and compensation data. OAuth tokens and API credentials for these integrations are stored in Mosaic's platform layer and do not transfer across platforms. We document each connected integration during scoping: integration name, sync frequency, fields mapped, and last successful sync date. The customer re-establishes Gusto connections manually in Trello or a separate HRIS tool post-migration using the documented field mapping as a reference.

Mosaic integrates with Deltek Vision and Vantagepoint for project and financial data. Deltek integration credentials do not transfer to Trello, which has no native Deltek connector. Time entries that originated from Deltek sync are treated the same as any Mosaic Time Entry (mapped to Card Checklist items). If the customer is on a Hosted-to-Cloud Deltek migration path, we note this as a separate Mosaic-Deltek migration that occurs outside the Trello migration scope.

Mosaic tracks Project status as Active, On Hold, Completed, or Archived. Trello Boards have no native status field. We map Active projects to active Boards, On Hold projects to Boards with an 'On Hold' Label, Completed projects to Boards with a 'Completed' Label and optionally archived, and Archived projects to Archived Boards. The customer chooses the archiving strategy during scoping based on whether they want historical project boards visible or hidden.

Mosaic Employees have a Department property pulled from Gusto. Trello Labels serve as the tag equivalent. We create one Trello Label per unique Department value (e.g., 'Engineering', 'Marketing', 'Finance') and apply these Labels to Cards assigned to Employees in each Department. This enables filtering and board views by department without requiring a custom field structure.

Mosaic Employees carry a Role property (e.g., Project Manager, Developer, Designer). Trello Labels map roles to Cards. We create one Label per unique Role value and apply them to Cards to indicate the role responsible for the work. If a Department and Role Label overlap (e.g., both have 'Finance'), we use a prefix convention (Role: Project Manager) to disambiguate.

Mosaic Projects may have attached documents including budget files, contracts, or resource plans. Trello Cards support file attachments up to 250MB per file on Premium. We migrate project-level attachments by associating them with a designated 'Project Documents' Card or a pinned Card with the project summary. Attachments larger than 250MB are flagged in the migration inventory for manual re-upload post-migration.

Mosaic Notes attached to Projects or Phases are migrated as Card Descriptions in Trello. Rich text formatting in Mosaic Notes converts to Markdown in Trello Card descriptions. If the Mosaic Note contains embedded images, these migrate as Card attachments with the image linked in the Card description text. Very long Notes that exceed Trello Card description length are split across multiple Cards with a naming convention (e.g., 'Note Page 1 of 3').