Migrate from EPAY HCM to Recruit CRM & ATS

EPAY's candidate records from the recruiting module (applicants to job openings) map to Recruit CRM Candidate records. We extract name, email, phone, address, work history, education, and skills from the EPAY candidate profile. The EPAY employee record (for applicants who became employees) does not migrate to Candidate — only the recruiting module applicant data moves. We preserve EPAY application status as a custom field since EPAY pipeline stages may not map directly to Recruit CRM's Kanban stages.

EPAY job postings (requisitions created within EPAY's recruiting module) map to Recruit CRM Job records. We transfer job title, description, location, employment type, salary range, and job status. EPAY job openings with multiple locations or distributed work arrangements map to individual Recruit CRM Jobs per location or to a single Job with location detail in the description. We flag any EPAY job that has been filled or archived so the customer can decide whether to include historical placements in Recruit CRM.

EPAY applications (candidate-to-job mappings) map to Recruit CRM job applications linked to the corresponding Candidate and Job records. EPAY application stage history (applied, screened, interviewed, offered, hired, rejected) maps to Recruit CRM pipeline stages, though we advise the customer to review stage alignment during scoping because EPAY stage naming conventions vary by customer configuration.

EPAY resumes and candidate document attachments migrate to Recruit CRM Candidate file attachments. We extract the document, convert to PDF if needed, and attach to the Candidate record via the Recruit CRM Files API endpoint. Resume parsing results from EPAY (structured fields extracted from resume content) migrate as custom fields on the Candidate record.

EPAY interview ratings and scorecards attached to candidate applications map to Recruit CRM Note records linked to the Candidate or Job Application. We advise the customer that Recruit CRM does not have a native scorecard object at Pro tier; Business or Enterprise tier enables more structured evaluation tracking. We document the scorecard field structure from EPAY for the customer to configure in Recruit CRM's custom fields.

EPAY's company records within the recruiting module map to Recruit CRM Company records (clients). We transfer company name, industry, size, website, and contact information. EPAY company records created in the HR context (employer organizations) are distinguished from recruiting-context client companies and do not migrate unless the customer specifically identifies client accounts to move.

EPAY contacts associated with recruiting client accounts map to Recruit CRM Contact records linked to the corresponding Company (Client). We transfer name, title, email, phone, and relationship type. EPAY contacts associated with employees (internal HR contacts) do not migrate unless the customer identifies them as client-side recruiting contacts.

Notes attached to EPAY candidate records migrate to Recruit CRM Note records linked to the Candidate. We preserve note text, author (mapped to Recruit CRM user by email match), and creation timestamp. Notes are migrated before the Candidate record is finalized in Recruit CRM to maintain the activity timeline.

EPAY skills, competencies, and tags on candidate profiles map to Recruit CRM custom Skills fields or tags depending on the Recruit CRM tier. We extract all EPAY skill tags during export and recommend a custom multi-select field in Recruit CRM to preserve the full skills taxonomy rather than relying on a free-text field.

EPAY recruiting workflows and automations (stage-triggered actions, email notifications, assignment rules) do not migrate as executable code. We deliver a written inventory of every active EPAY recruiting workflow with its trigger, conditions, actions, and a recommended Recruit CRM workflow builder equivalent. The customer's admin rebuilds them in Recruit CRM's workflow automation tool post-migration.

EPAY custom fields on candidate, job, and application records map to Recruit CRM Custom Fields. We extract field name, data type, and picklist values from EPAY and recreate them as equivalent Recruit CRM custom fields before migrating any records. Recruit CRM's Custom Field API and Nested Custom Fields endpoint support most standard field types including picklist, text, number, date, and checkbox.