Migrate from empeon to Recruit CRM & ATS

Empeon Employee records map to Recruit CRM Candidate profiles. Standard fields (first name, last name, email, phone, department, job title, hire date, employment status) migrate directly. The candidate's current job title and department in Empeon become the Candidate's current position fields in Recruit CRM. Email address from Empeon becomes the primary contact email; phone becomes the mobile or office phone. Employment status (active, terminated, on leave) does not map to a Recruit CRM field and is stored as a custom field empeon_status__c for reference.

Empeon Payroll Register exports (pay periods, gross pay, net pay, deduction line items, tax withholding amounts) cannot map to a native Recruit CRM object because Recruit CRM is an ATS, not a payroll system. We export the payroll register as structured rows and attach it as a Note on the corresponding Candidate record, preserving pay period, earnings, deductions, and net pay in a formatted text block. If the customer requires payroll data for compliance or re-hire verification, we recommend a separate payroll export delivered as a PDF package alongside the ATS migration.

Empeon PTO, sick leave, and other accrual balances per employee migrate as Read-only custom fields on the Candidate record in Recruit CRM. We export current balance, accrual rate, and carryover rules as structured key-value pairs. Historical balance snapshots are not migratable as a timeline; a summary note with the most recent balance snapshot is attached instead. Accrual rules (accrual rates, carryover caps, usage thresholds) do not migrate as configuration and are documented for the customer's admin to rebuild in Recruit CRM's custom field formulas or as a separate reference document.

Benefit plan name, carrier, coverage tier (employee, employee plus spouse, family), and enrollment effective date migrate as custom fields on the Candidate record. We flatten multi-tier benefit elections into individual checkboxes or picklist values. Plan names and carrier codes that differ between Empeon and any downstream benefits system are preserved as free-text strings with the original Empeon value noted. Benefit enrollment data is read-only post-migration in Recruit CRM since the ATS does not manage benefits administration.

Empeon free-text Input custom fields map to Recruit CRM text custom fields. We enumerate all active Input fields during scoping and create matching text fields in Recruit CRM before migration. Because Empeon Input fields store unstructured free text, we cannot guarantee data quality in the destination and flag this in the mapping documentation. Checkbox fields map directly to Recruit CRM checkbox custom fields.

Empeon Checkbox custom fields map directly to Recruit CRM checkbox custom fields with no transformation required. We confirm the checkbox state (checked/unchecked/unset) and migrate the boolean value. Any Empeon Input field that was used to store yes/no data (free-text 'yes' or 'no' rather than a native checkbox) is parsed and coerced to a boolean during transformation before inserting into Recruit CRM.

Bank routing numbers and account numbers are sensitive fields that do not have a destination in Recruit CRM. We flag them as sensitive, encrypt them at rest during migration, and suppress them from any non-production export. We attach a masked summary (last four digits of account number only) as a private Note on the Candidate record for compliance record-keeping. The customer should re-collect direct deposit information through Recruit CRM's onboarding flow or a separate HRIS if they intend to run payroll through a new system.

Empeon clock punches and scheduling data (Employee View and Daily View) have no native equivalent in Recruit CRM. We export attendance summaries by employee and attach them as Notes on the Candidate record. Advanced Scheduling assignments (shift patterns, rotation rules) are documented as a separate configuration inventory for the customer's admin. Recruit CRM's interview scheduling does not replace Empeon's time-and-attendance functionality; these are separate systems.

Documents attached to Empeon employee profiles (offer letters, performance reviews, certifications, I-9 forms) migrate as file attachments on the corresponding Candidate record in Recruit CRM. We export binary content and file metadata (filename, MIME type, upload date). Recruit CRM's file attachment limits apply; documents exceeding the platform limit are flagged during scoping and migrated to a customer-owned cloud storage bucket with links embedded in the Candidate record instead.

Empeon Company-level configuration (departments, cost centers, job titles, pay grades) can be migrated as reference data into Recruit CRM's Client or Company records if the customer uses Recruit CRM to track client organizations or staffing assignments. Department names become Recruit CRM Custom Fields on the Client object. Pay grades and cost centers are documented as a separate configuration sheet for the customer's admin to set up as lookup lists in Recruit CRM.

Empeon ESS Hub credentials and self-service access are tied to the employee's email address in the Empeon Workforce profile. These credentials do not map to Recruit CRM's candidate portal authentication. We document all ESS Hub registrations during scoping and flag that candidates must re-register or be provisioned access separately in Recruit CRM. The ESS email-must-match requirement in Empeon is a known risk that we cross-reference during scoping to flag any domain mismatches.