Migrate from Cavu HCM to BambooHR

Cavu HCM employee records export from the Employer on Demand portal include name, address, job title, department, hire date, compensation, employment status, and emergency contacts. We map these fields to BambooHR's Employee object, using the employee email address as the primary dedupe key. BambooHR requires a unique email per employee; we flag any Cavu records with missing or duplicate emails during reconciliation and resolve with the customer's HR administrator before import. Employment status (active, inactive, terminated) maps directly, with termination date preserved in BambooHR's Termination Date field.

Historical payroll data including earnings, deductions, taxes, and direct deposit details export in batch from the Cavu payroll module. BambooHR Payroll does not store granular historical payroll records as a native object; instead, we load annual earnings summaries and current compensation into BambooHR's Compensation and Employment History custom fields. Garnishment orders and Workers' Comp rate codes export separately and are documented in a written reference file for the customer's HR administrator to configure in BambooHR Payroll or retain in a separate system of record.

Cavu HCM pay schedule configuration (weekly, bi-weekly, semi-monthly, monthly) and associated GL mapping export cleanly and map directly to BambooHR's pay frequency setting. Pay period start and end day configuration migrates 1:1. This is the most straightforward object in the migration because both platforms expose pay schedule as a configuration object with no conditional logic.

Cavu HCM PTO accrual balances and usage history export per employee across multiple leave types (vacation, sick, personal). We map accrual balances to BambooHR's Time Off module, preserving accrual rates and available balance. Historical usage events (approved time-off requests) migrate as individual Time Off records in BambooHR with status set to Approved and the original dates preserved. Leave type names map to BambooHR's configured Time Off types; if Cavu uses custom leave type names, we document them for the customer's BambooHR admin to create matching types before migration.

Benefit elections (health, dental, vision, 401k) export per employee with effective dates and coverage tier selections. We sequence enrollments chronologically to preserve active coverage states at the time of migration and flag any mid-year election changes. Benefits data migrates into BambooHR's Benefits module, with carrier name, plan name, coverage level (employee, employee+spouse, family), and monthly cost preserved. BambooHR's Benefits module requires carrier and plan configuration in the admin settings before employee elections can be loaded; we handle this sequencing during the configuration phase.

Federal, state, and local tax withholding setups, including LDG (Legislative Data Group) assignments for multi-state employers, export from Cavu's tax configuration module. We map these to BambooHR's tax withholding setup, preserving federal EIN, state registration numbers, and jurisdiction-specific withholding rates. Multi-state tax configurations require per-state setup in BambooHR; we document the full list of active jurisdictions from Cavu and sequence the BambooHR tax configuration so that all required states are enabled before any employee tax records are imported.

Time and attendance records export from Cavu's time-tracking module including clock-in/clock-out events, hours worked, overtime, and any edited or approved entries. We map these to BambooHR's Time Tracking module, preserving original timestamps and overtime flags. Entries that were edited or approved after initial submission are flagged with a migration note field so the customer's HR administrator can review BambooHR's approval workflow equivalents. BambooHR Time Tracking is an add-on module; we verify its activation during the scoping phase.

Employee documents including new hire forms, tax withholdings, I-9s, and performance reviews export as individual files with metadata from Cavu's Document Storage module. We preserve folder structure and file naming conventions during extraction, then load documents into BambooHR's Files section attached to the corresponding Employee record. PDF and image formats migrate without transformation; files with unrecognized formats are flagged in the reconciliation report. BambooHR's file storage limits vary by plan tier; we verify storage availability during scoping.

Talent management stores applicant data including application status, screening results, and onboarding task completion. We migrate the most recent application per candidate and preserve the pipeline stage from Cavu as a custom field in BambooHR's ATS module. BambooHR's ATS is an optional add-on; if the destination account does not include ATS, we deliver applicant data in a structured CSV with field mapping notes for manual import or for a future ATS implementation. Onboarding task completion migrates as a custom field on the Employee record if ATS is not present.

Workforce scheduling data exports as shift records with employee assignment, start/end times, and location. BambooHR does not have a native shift scheduling module in its standard or Payroll plans. Recurring schedule templates are extracted and documented in a written schedule reference file that the customer's HR administrator can use to configure BambooHR's Time Tracking or a third-party scheduling tool. Active shift assignments at migration cutover are preserved as a custom field reference so that the current schedule is not lost during transition.