Migrate from Eploy to Recruit CRM & ATS

Eploy Jobs (requisitions) map directly to Recruit CRM Jobs. We preserve job title, department, location, salary bands, and the job-to-workflow linkage. Eploy's custom job fields migrate as custom fields in Recruit CRM, with the field schema discovered during scoping. The job's workflow assignment is not a native Recruit CRM concept; we capture it as a tag or pipeline stage name for the customer to configure after migration.

Eploy Candidate records map to Recruit CRM Candidates with full contact details, application history, skills, and status preserved. Eploy's candidate_id becomes the dedupe key. We flag any custom properties added to the candidate schema and create corresponding custom fields in Recruit CRM before import. Candidate documents attach via Recruit CRM's file upload endpoint after the candidate record is created.

Eploy stores a candidate's application to a job as a separate record; Recruit CRM links candidates to jobs and exposes per-job associated fields via POST /v1/candidates/associated-field/{candidate}/{job}. We map Eploy's application status and stage to Recruit CRM's associated_fields structure, with field_id values pre-discovered from the destination schema during scoping.

Eploy workflow stages are organisation-defined and discovered by aggregating distinct stage values from active jobs during scoping. Recruit CRM uses pipeline stages on its Kanban board. We build a customer-confirmed mapping table during scoping that maps each Eploy stage name to the destination pipeline stage. Stage transition timestamps migrate as associated field values or custom fields on the candidate-job association.

Hiring manager assignments in Eploy (which user is tied to which job and stage) map to Recruit CRM User records assigned as owners or collaborators on Job and Candidate records. Role-based permissions that do not have a Recruit CRM equivalent are documented for the customer's admin to configure post-migration.

Active offer records from Eploy (salary, start date, role details, e-signature status) migrate as structured data on the associated Candidate or Job record in Recruit CRM. E-signature audit trails migrate as document attachments where the API exposes them. Recruit CRM does not have a native Offer object; we document the customer-chosen target field for this data during scoping.

Eploy's onboarding module may expose a partial schema via API. We query the onboarding endpoints explicitly during discovery. Records that return partial schemas (reference collection status, contract status, compliance documents) are flagged and recommended for manual CSV export as a complement to the API-driven migration. Recruit CRM has no native onboarding module, so onboarding data requires a post-migration process decision.

Eploy referral records link an employee to a referred candidate with reward status. We preserve referral attribution by populating a referral source field on the Candidate record in Recruit CRM, using the referring employee name as a text field or linking to a Recruit CRM User record if the employee exists as a user.

Eploy Talent Pools are saved candidate collections. We migrate pool memberships as tags on the Candidate record in Recruit CRM, preserving the pool name as the tag value. If Recruit CRM introduces segment functionality, we map pool-to-segment during scoping.

Organisations add custom fields to Jobs, Candidates, and other objects in Eploy. We detect the full custom property schema during discovery and create corresponding custom fields in Recruit CRM before migration. For custom properties with picklist values, we replicate the picklist options in Recruit CRM's field configuration.

Eploy assessment scores and results attach to Candidate records as structured data. We migrate available assessment fields as custom fields on the Candidate record. Visual or graphic scores that do not have a structured API representation are mapped to text equivalents with the original value preserved in a notes field.

Resumes, cover letters, and compliance documents attach to Candidates and Jobs in Eploy as download URLs. We enumerate all attachment URLs, download each file to temporary storage, then upload each to Recruit CRM's attachment endpoint linked to the corresponding Candidate record. Large volumes of attachments (common in compliance-heavy sectors) extend migration time and require storage headroom. We batch document migration after the primary record import completes.