Migrate from Mosaic HCM to Recruit CRM & ATS

Mosaic HCM's ATS module stores candidate records with application status, source, and associated job postings. We extract all active and recently inactive candidates and map them to Recruit CRM's Candidate object. The candidate's email address is the dedupe key; we resolve duplicates by email match and flag records with the same name and email for manual reconciliation before load.

Open and recently closed job postings in Mosaic HCM map to Recruit CRM's Job object. Fields including job title, department, location, employment type, and job description transfer directly. We preserve the original posting date and any internal job ID from Mosaic HCM as a custom field for audit traceability. Closed jobs more than 90 days past close date are archived rather than migrated unless the customer explicitly requests them.

The association between a candidate and a job posting in Mosaic HCM maps to Recruit CRM's Application object. Application status (applied, screening, interview, offer, hired, rejected) maps to Recruit CRM's pipeline stage values. We resolve the parent Candidate and Job references at migration time using email-based and job-title-based lookups respectively.

Mosaic HCM stores internal candidates (current employees applying to new roles) as employee records. We flag these during extraction and map them as internal candidates in Recruit CRM with an internal_candidate flag. Their existing Mosaic HCM employee ID is preserved as a custom field for any future HCM sync.

Mosaic HCM's organizational records for external hiring clients map to Recruit CRM's Client object. Client name, primary contact, industry, and location transfer directly. If Mosaic HCM stores client records as Company or Organization records without a client-specific type, we use the organization's address domain to classify external clients versus internal entities.

Mosaic HCM builds custom fields during implementation—skills taxonomies, source tracking fields, assessment scores, or consent flags. We enumerate every custom candidate property during the discovery session and create equivalent custom fields in Recruit CRM before migration. Recruit CRM supports custom fields on the Candidate object via its field management interface; we configure these in the destination org before loading data.

Candidate-facing email templates from Mosaic HCM's talent module export as text or HTML files. We import these into Recruit CRM's Email Templates library, preserving merge fields as Recruit CRM-compatible tokens. We do not migrate automated sequence emails; these are documented as a separate scope for Recruit CRM's automation rebuild.

Employee documents (offer letters, signed agreements, assessment results) stored in Mosaic HCM's document repository are extracted as files and associated with the correct candidate record in Recruit CRM. File naming preserves the original document type and date. We use Recruit CRM's file upload API to attach documents to the corresponding Candidate record after the base record is loaded.

Benefits enrollment data (medical, dental, vision, 401k elections, dependent information) is HRMS-specific and has no place in a recruitment ATS. We do not migrate benefits data. If the customer's compliance team requires a benefits enrollment history for audit purposes, we export the data as a standalone file and deliver it separately from the ATS migration scope.

Mosaic HCM's configurable workflow engine automates recruiting steps, approval chains, and task routing. These workflows are platform-specific and do not export as data. We document every active workflow—its trigger, conditions, and actions—during discovery and deliver a written inventory with recommended Recruit CRM automation equivalents. The customer's admin rebuilds them in Recruit CRM's workflow builder post-migration.