Migrate from Mosaic HCM to BambooHR

Mosaic HCM Employee records map directly to BambooHR Employee records. Standard properties — first name, last name, date of birth, hire date, termination date, job title, department, location, work email, mobile phone — migrate cleanly via BambooHR's API or CSV import. The hire date maps to BambooHR's hireDate field; the original hire date for employees with re-hire events maps to a custom date field. Custom employee properties (built during Mosaic HCM implementation) require discovery enumeration before mapping; we store them as BambooHR custom fields with the original Mosaic HCM field name preserved in the field label for audit traceability.

Mosaic HCM stores multiple legal entities (EINs) on a single database instance. Each Mosaic HCM EIN maps to a separate BambooHR company account (separate tenant subscription). We request the EIN field in every Mosaic HCM export and validate entity assignment per employee before loading into the corresponding BambooHR company. If the organization is consolidating to a single BambooHR company (which BambooHR natively supports for single-entity employers), we strip the EIN tag and assign all employees to one company. Multi-EIN splits require the customer to provision additional BambooHR company accounts before migration begins.

Effective-dated pay records in Mosaic HCM (salary, hourly rate, bonus, equity entries) map to BambooHR's payRate field and, where the customer licenses BambooHR Payroll, to compensation history entries. We extract the current effective compensation record as the active pay rate and store historical pay changes as a dated compensation table in a custom section. BambooHR does not natively store a full effective-dated compensation ledger — we handle this by creating a custom table structure and loading historical comp changes as dated entries for audit and reporting purposes.

PTO, leave, and accrual balances from Mosaic HCM map to BambooHR's Time-Off module. We extract the accrual ledger balances as of the migration date, including carryover amounts and any negative balance flags. Each Mosaic HCM accrual plan type (PTO, sick, personal) maps to the corresponding BambooHR time-off policy. Note that BambooHR's time-off module handles current balances and policy rules; historical accrual transactions (the detailed accrual-and-usage log) are not a standard BambooHR object and are delivered as a supplemental CSV for the customer's records.

Medical, dental, vision, and supplemental benefit plan assignments map to BambooHR's Benefits module (if licensed) or are delivered as a structured enrollment CSV. We map plan name, coverage tier (employee only, employee plus spouse, family), and dependent information to BambooHR's benefits data structure. Historical enrollments at period boundaries are included for compliance audit purposes. Benefits plan configurations (carrier, plan type, contribution amounts) require the customer's benefits broker to configure the plans in BambooHR before enrollment data is loaded; we deliver the enrollment data in a format the broker can use to pre-populate.

Beneficiary and dependent records from Mosaic HCM (name, date of birth, relationship, SSN) map to BambooHR's dependent records linked to the employee. SSN is stored as a custom protected field in BambooHR with field-level access restricted to HR admin users. We extract dependent records alongside the benefits enrollment export so that the relationship structure is intact in BambooHR.

Mosaic HCM payroll histories (YTD earnings, federal and state tax withholdings, garnishments, direct deposit allocations) are extracted as period-end snapshots after compliance sign-off from Mosaic HCM's team. These are loaded as read-only compensation summary records in BambooHR's custom fields for the current and prior tax year. Note: BambooHR is not a payroll processor by default; organizations moving payroll from Mosaic HCM either activate BambooHR Payroll (a licensed add-on) or migrate payroll to a separate platform. We handle the payroll data mapping in either direction, but the payroll processing decision is made before migration scoping.

Mosaic HCM's integrated document repository (offer letters, signed I-9s, performance reviews, onboarding forms) is extracted as files and associated with the correct employee record in BambooHR. We use BambooHR's Employee Files API to upload each document with an appropriate file category (Onboarding, Performance, Benefits, Legal). Documents are uploaded as binary files via BambooHR's file upload endpoint, which requires an admin-level API key with employee file write permissions.

Mosaic HCM Positions define headcount budget and FTE allocation alongside the employee occupying them. In BambooHR, the equivalent is the Job Title field (a picklist) combined with a custom Positions table if the customer needs headcount budgeting. We map the position title to BambooHR's jobTitle field and flag positions with headcount budget data for the customer's admin to configure in a supplemental positions table or a separate spreadsheet.

Mosaic HCM's configurable workflow engine covers onboarding step sequences, approval chains, and task routing. These are platform-specific and do not export as data. We run a discovery session with the Mosaic HCM administrator to enumerate every active workflow, document its trigger conditions, steps, approvers, and downstream actions, and deliver a written map recommending equivalent BambooHR automation paths. The customer's HR admin rebuilds the workflows in BambooHR or via a workflow automation partner post-migration.

Mosaic HCM custom fields built during implementation (any field not in the standard UKG Ready schema) are enumerated in a discovery session before migration. We map each custom field to a BambooHR custom field with the equivalent data type (text, date, number, dropdown). The original Mosaic HCM field label is preserved in the BambooHR custom field label so the customer's admin can audit the mapping. Note that Mosaic HCM conditional logic on forms (showing or hiding fields based on other field values) does not export and is documented separately as a BambooHR form logic recommendation.