Migrate from Cavu HCM to Crelate

Cavu HCM employee records export from the Employer on Demand portal with name, address, job title, department, hire date, and compensation fields. We map these to Crelate Person records, using email as the primary deduplication key. Because Cavu maintains separate portal logins for employer and employee views, a single individual may appear in multiple portal exports; we run email-based deduplication before insert and flag any records with identical names but different SSNs for the customer's HR administrator to resolve.

The Cavu HCM employer entity maps directly to a Crelate Organization record. The organization's legal name, address, and business type export cleanly from the portal and load as a single Organization record in Crelate. We use the employer legal name as the Organization Name and preserve the full postal address in Crelate's address fields.

Cavu HCM's talent management module stores applicant data including application status, screening results, and onboarding task completion. We migrate the most recent application per candidate into Crelate's Job record with the application status preserved as a custom field and the pipeline stage mapped to a Crelate Job status. Screening results and onboarding task completion migrate as Activity records linked to the Job, maintaining the candidate's progression history.

Cavu employee documents including new hire forms, tax withholdings, and performance reviews are extracted as files and attached to the corresponding Crelate Person record. We retain folder structure metadata in custom fields on the Person record so the customer's recruiters can locate documents without manual re-filing. Any compliance-required documents are noted in the migration inventory for the customer's admin to verify completeness post-load.

Time and attendance records export from Cavu's time-tracking module as clock-in and clock-out events. We map these to custom fields on the Crelate Person record, preserving the most recent entry's hours and overtime flags. We flag any entries that were edited or approved after the fact in a separate custom field to preserve audit context for the customer's payroll administrator.

Benefit elections including health, dental, vision, and 401k with effective dates are stored as custom fields on the Crelate Person record. We sequence elections chronologically to show the active coverage state at migration time. Crelate's ATS model does not represent benefit enrollment as a structured object, so historical enrollment details are preserved as structured text fields rather than a native data type; the customer's HR administrator reviews the custom field contents for completeness.

PTO accrual balances and usage history per employee are extracted as structured custom fields on the Crelate Person record. Multiple leave types including vacation, sick, and personal with accrual rules that vary by employee class are preserved in custom fields as references for the customer's HR administrator. We do not create a native leave management workflow in Crelate since Crelate is a recruiting ATS and does not have a PTO management module.

Historical payroll data including earnings, deductions, taxes, and direct deposit details are preserved in a structured summary as custom fields on the Crelate Person record. Garnishment orders and Workers' Comp rates require separate extraction and are stored as structured text custom fields for the customer's finance team reconciliation. We do not recreate a payroll processing workflow in Crelate; the payroll summary is provided for record continuity only.

Pay schedule configuration including weekly, bi-weekly, semi-monthly, and monthly frequencies along with GL mapping export cleanly and are stored as structured fields on the Crelate Organization record. Crelate does not have a native pay schedule object; the configuration is preserved as reference data for the customer's finance team.

Federal, state, and local tax withholding setups including LDG assignments for multi-state employers are stored as structured custom fields on the Crelate Person record. Field-level mapping handles Cavu's internal tax jurisdiction codes by creating a corresponding picklist or text custom field in Crelate for each tax configuration type. Multi-state employers with complex LDG assignments may require additional custom field creation time during schema design.

Workforce scheduling data including shift records with employee assignment, start and end times, and location are extracted as structured records. We map these to a combination of custom fields on the Crelate Person record (for current shift patterns) and Activity records (for historical shift entries), preserving the temporal history. Recurring schedule templates are extracted separately and provided as a written inventory for the customer's admin to reconstitute as Crelate Workflows if applicable.

Cavu HCM employer-level company data (distinct from the employer entity) representing client businesses or divisions within the organization map to Crelate Organization records. We map company name, industry, address, and any client-specific custom fields to the corresponding Organization fields. Parent-child company hierarchies in Cavu are preserved as Organization hierarchy custom fields in Crelate.