Migrate from empeon to Crelate

Empeon Employee records map to Crelate Contact. Standard fields (name, email, phone, job title, department, hire date, employment status) map to equivalent Crelate Contact properties. The Empeon employee email address becomes the Contact email and is used as the dedupe key during import. Employment status (active, inactive, terminated) maps to a custom Crelate field for HR visibility. We flag any Employee record without a valid email address for manual review because Crelate relies on email for candidate communication workflows.

Empeon Company-level configuration (organization name, departments, cost centers, job titles, pay grades) maps to Crelate Organization. The organization name from Empeon's Company tab becomes the Crelate Organization name. Department and cost center lists migrate as Crelate Tags or custom picklist fields on Contact for segmentation. This mapping covers the organizational hierarchy only; Empeon Company tab settings do not represent external client companies and should not be confused with Crelate Organizations that represent clients or employers in a recruiting context.

Empeon Input fields (free-text, up to 8 per profile) map to Crelate Contact custom text fields. We parse free-text values during transformation and preserve them as-is. Crelate supports text, number, date, currency, URL, and phone field types at Business tier, so if the Empeon Input field contains structured data (e.g., a date or a numeric ID), we attempt type coercion and flag any values that fail validation for manual correction before import.

Empeon Checkbox fields (yes/no, up to 5 per profile) map to Crelate Contact custom Boolean fields. Checked maps to true, unchecked maps to false. We validate that the Empeon Checkbox label (e.g., 'Safety Training Complete', 'Background Check Done') has a meaningful Crelate equivalent field name and document any label conflicts during scoping.

If the customer's Empeon instance tracks their own organization (the employer company) as a Company record, that maps to a Crelate Organization record representing the hiring company. In recruiting contexts, this Organization record holds the employer brand, job posting history, and client relationship notes. We confirm the customer's Empeon Company data intent during discovery before assigning this mapping.

Bank routing numbers and account numbers from Empeon Direct Deposit profiles are sensitive financial data with no native Crelate field. We export these as encrypted structured data in a separate secure file and provide the customer's finance or HR team with a written re-entry guide. Routing and account data does not migrate into the Crelate Contact record unless the customer explicitly requests it as a restricted custom field with access controls.

Documents attached to Empeon Employee profiles (offer letters, certifications, performance reviews) migrate as Crelate Contact attachments if file access is available via the API Connector or Live Report exports. We export file metadata (filename, document type, upload date, employee reference) and binary content where accessible. The employee email address links each document set to the corresponding Crelate Contact record.

Empeon ESS Hub access is tied to the email address stored in the employee profile. We capture all employee email addresses during discovery and cross-reference them against the Crelate Contact email field. If domain changes or email re-enumeration is planned, we flag mismatches before cutover so that candidate self-service and communication workflows in Crelate are not disrupted post-migration.

Empeon payroll registers, pay periods, gross/net pay amounts, and deduction line items have no equivalent object in Crelate's ATS schema. We export payroll data as structured CSV (chunked by pay period) and deliver a written data dictionary to the customer's HRIS team for configuration in their chosen HRMS. Payroll migration is out of scope for the Crelate migration and should be treated as a separate workstream.

PTO, sick leave, and other accrual balances tracked in Empeon have no Crelate equivalent. Crelate is a recruiting system and does not manage time-off balances. We export current accrual balances and accrual rate rules as structured CSV for the customer's HRIS team to configure in their replacement HRMS. Historical accrual snapshots migrate as a reference file only.

Benefit plan enrollments, carrier assignments, coverage tiers, and enrollment dates stored per Empeon employee do not map to any Crelate object. We export benefit enrollment records as structured CSV and deliver a written data dictionary. The customer's HR team configures benefit data in their replacement HRMS or benefits administration platform as a separate post-migration workstream.

Clock punches, scheduling data (Employee View and Daily View), and timesheet approvals stored in Empeon have no Crelate equivalent. Crelate's Activity model (calls, emails, meetings, tasks) does not cover time-and-attendance records. We export time-and-attendance data as structured CSV for the customer's HRIS team. Scheduling and timesheet configuration is a separate workstream in the replacement HRMS.