Migrate from EPAY HCM to Crelate

EPAY Employee records contain personal info, employment history, department, location, and job title. Only a subset maps to Crelate Contact: name fields, email, phone, address, current title, and employment history dates. Fields specific to payroll (compensation, pay frequency, deduction codes), benefits (enrollment, coverage tier, carrier), tax (W-4, state withholding, garnishments), and time tracking (accruals, scheduling, job costing) have no Crelate equivalent and are not migrated. For internal mobility scenarios where EPAY employees become Crelate candidates, we map the employee record as a Contact with an additional custom field epay_employee_id__c for reference.

EPAY's recruiting module tracks job postings, applicants, and application status. These map to Crelate Job Order records. The EPAY job title, department, location, and posting status become Crelate Job Order title, client (mapped from EPAY Company), and status. Application stage (applied, screened, interviewed, offered, hired, rejected) maps to Crelate's Submission pipeline stages. We preserve the original EPAY application date and any screening notes.

EPAY's candidate pool and applicant records map to Crelate Contact. Resume content migrates as a parsed Crelate Resume record attached to the Contact via ContentDocumentLink. Skills, certifications, and work history from the EPAY applicant profile map to Crelate's standard Contact fields and any custom fields configured during scoping. Crelate's resume parsing (Standard at Business, Premium limits at Business Plus and Enterprise) processes incoming documents post-migration.

EPAY maintains organizational structure including company name, location, department, and cost center. These map to Crelate Company records. The EPAY company identifier becomes a custom field epay_company_id__c for reconciliation. If EPAY's organizational units represent hiring clients (for staffing firms), they map to Crelate Client records with Company as the parent.

EPAY's submission and placement tracking maps to Crelate Submission records attached to a Contact and a Job Order. The EPAY submission status, submission date, assigned recruiter, and placement outcome (if applicable) migrate as Crelate Submission fields. Placement fee and billing status from EPAY — relevant for staffing firms — map to custom Crelate fields or to the Crelate Business transaction tracking if the customer's Business Plus or Enterprise tier supports it.

EPAY stores interview schedules, interviewer feedback, and evaluation scores. These migrate to Crelate Activity records (meetings and tasks) linked to the Contact and Job Order, with evaluation content stored as Notes or as custom Activity form responses. Interview scores from EPAY numeric rating systems map to custom Crelate fields or to Activity form custom fields configured during schema design.

EPAY recruiter and hiring manager assignments on job postings and applications map to Crelate User records by email match. We resolve the OwnerId reference at migration time. Any EPAY recruiter without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before the production import.

EPAY benefit enrollment records — plan names, coverage tiers, enrollment dates, dependent information, carrier details — have no Crelate equivalent. We export the enrollment data as a CSV reference file for the customer's HR team to use when re-enrolling employees in the destination HR platform (separate engagement). Benefits data does not load into Crelate.

EPAY payroll run records, earnings, deductions, taxes, net pay by pay period, pay stubs, and tax filing history have no Crelate equivalent. We export payroll history as a PDF and CSV reference file for the customer's payroll team and recommend retaining EPAY access or a payroll archive service for lookback. Active garnishment orders and deduction codes require manual verification in the destination HR platform before the first payroll run.

EPAY clock-in/clock-out data, overtime records, accrual balances, scheduling rules, and job costing assignments have no Crelate equivalent. We export attendance summary data as a CSV reference file for the destination HR or time-tracking platform. Accrual balances (PTO, sick, holiday) require manual entry or API import into the destination system by the customer's HR team.

EPAY pay rates, salary histories, pay frequency, bonuses, pay adjustments, and effective-dated compensation changes have no Crelate equivalent. We export the compensation timeline as a CSV reference file. The customer's HR team or the destination HR platform administrator enters compensation data during onboarding in the new system.

EPAY performance review cycles, 360-degree feedback, journaling entries, and review status tracking have no Crelate equivalent. We export review history and scores as a CSV reference file. The destination HR platform handles performance management going forward. Review cycle configuration does not migrate.