Migrate from Mosaic HCM to Crelate

Mosaic HCM employee records map to Crelate Contact records when the employee is sourced as a candidate or when the migration scope includes recruiting data. Standard Mosaic HCM properties (first name, last name, DOB, hire date, job title, department, location) map to corresponding Crelate Contact fields. Employee status (active, terminated) maps to a custom Contact field for recruiting pipeline segmentation. Custom employee properties enumerated during discovery migrate as Crelate custom fields (text, numeric, monetary, picklist, or date type per Crelate's field-type restrictions). We resolve Mosaic HCM's EIN assignment per employee against Crelate's organizational structure before bulk import.

Mosaic HCM multi-EIN configurations bundle all employees under a single database export without entity separation unless explicitly requested. We ask Mosaic HCM's team to include the EIN field in every export and validate that each employee record carries the correct legal entity assignment. Crelate maps legal entities to Organizations or to custom Company groupings depending on the customer's structure. Misassignment at this step creates duplicate candidate records and pipeline contamination in Crelate.

Mosaic HCM position records (headcount budget, FTE allocation, job title hierarchy) map to Crelate Job records when the migration scope includes open requisitions or job-order data. Position title becomes the Job Name; FTE allocation becomes headcount on the Job; department maps to a custom Job field. UKG Ready position data is separate from the employee record, so we extract positions as a distinct export and correlate them to the recruiting workflow by department and location.

When Mosaic HCM's ATS module is in use, candidate application records (application status, source, associated job posting, interview stages) migrate to Crelate Contact records with a candidate flag. Application status from Mosaic HCM maps to a custom Crelate field tracking pipeline stage. Job applications migrate as Activity records or Opportunity records in Crelate depending on whether the customer uses Crelate's ATS-only or ATS-plus-sales workflow. Inactive candidates are migrated with a status field set to Inactive to preserve historical data without inflating the active pipeline.

Effective-dated pay changes, salary, hourly rate, bonus, and equity entries migrate as Crelate custom fields on the Contact record (monetary type for salary fields, numeric for equity). Crelate's default Contact schema includes salary fields; additional Mosaic HCM compensation dimensions (bonus structure, equity grant dates, pay change effective dates) are added as custom fields during migration. Compensation data is sensitive; we flag this as a restricted export requiring the same compliance sign-off as payroll data and note it for separate coordination with Mosaic HCM's team.

Employee documents stored in Mosaic HCM's document repository (offer letters, I-9s, performance reviews, signed forms) migrate as file attachments linked to the corresponding Crelate Contact record. We extract documents as files, rename them with a consistent naming convention (ContactID_DocType_Date), and attach them via Crelate's document management interface or API. Resume files associated with candidate records migrate as the primary Contact attachment.

Payroll data (YTD earnings, tax withholdings, garnishments, direct deposit allocations) has no structural equivalent in Crelate's ATS data model and is not migrated. We do not load payroll records into Crelate because Crelate is not designed to process payroll and mixing payroll data into a recruiting CRM creates data contamination. We flag payroll history as a separate migration workstream to the customer's HR admin, recommending a dedicated HRMS destination (Workday, ADP, UKG Ready standalone) for payroll and benefits data.

Benefits plan assignments, coverage tiers, and dependent information have no equivalent in Crelate's Contact schema. We do not migrate benefits enrollment data to Crelate. We deliver a written inventory of Mosaic HCM benefits plan names, enrollment periods, and coverage tier mappings as a reference document for the customer's HR admin to recreate in a benefits administration tool or their new HRMS.

Time entries and PTO/leave accrual balances do not migrate to Crelate. Crelate's activity model tracks recruiting activities (calls, emails, interviews, placements) rather than workforce timekeeping. We deliver a written inventory of accrual balances as of the migration date for the customer's HR admin to record in the destination HRMS or payroll system.

Mosaic HCM configurable workflows (onboarding steps, HR approval chains, task routing, benefits enrollment workflows) are platform-specific and do not export as data. We document every active Mosaic HCM workflow with its trigger, conditions, actions, and approver chain as a written inventory delivered to the customer's HR admin. Crelate's custom recruiting workflows are documented separately and the customer's recruiting leadership rebuilds them in Crelate post-migration.

Recruiting activity history from Mosaic HCM (calls, emails, meetings logged against candidate or employee records) migrates to Crelate Activity records linked to the corresponding Contact. Crelate Activity supports custom activity types; we map Mosaic HCM activity types to Crelate's activity type taxonomy. Activity timestamps and disposition data preserve in custom fields. Note that payroll-related or HR-specific engagement records (performance review meetings, manager one-on-ones) are out of scope for Crelate migration and are flagged for the HR admin inventory.

Mosaic HCM custom fields built during implementation (enumerated during the mandatory discovery session) map to Crelate custom fields on the appropriate entity. Crelate restricts custom field types: short/long answer (text), numeric, decimal, monetary, date, picklist (single or multi-choice). Mosaic HCM properties that use unsupported types are converted to the nearest Crelate equivalent or dropped with a documented rationale. Custom field logical names for API access are assigned per Crelate's Advanced settings convention.