Migrate from Eploy to Crelate

Eploy Jobs map to Crelate Job records with title, department, location, salary bands, and workflow assignment preserved. Eploy's job-to-workflow linkage maps to Crelate's pipeline stage assignment. Custom job fields migrate as custom fields on the Crelate Job object. Department and location hierarchies from Eploy map to Crelate's organisational taxonomy if the customer uses Crelate's multi-office configuration.

Eploy Candidates map to Crelate Person records. Contact details, application history, skills, notes, and status transfer directly. Eploy's candidate-to-job application links map to Crelate's Application records attached to the Person. Duplicate detection uses email as the primary key with name and phone as secondary checks.

Eploy workflow stages are customisable per organisation with no canonical list in the API. We discover active stage values by querying Eploy Jobs and aggregating distinct stage names during scoping, then build a mapping table to Crelate pipeline stages with customer confirmation. Stage transition timestamps migrate as audit data attached to the Application record in Crelate.

Eploy Offers (salary, start date, role details, e-signature status) map to Crelate Offers attached to the relevant Application. E-signature audit trails transfer where the API exposes them. If Eploy Offer status is conditional or withdrawn, we preserve that status in Crelate Offer and flag any corresponding Application for admin review.

Eploy's onboarding module (reference collection, contracts, compliance documents) may live in a separate schema with partial API exposure. We query the onboarding endpoints explicitly during discovery. Records accessible via API migrate to Crelate Hire if the customer holds that subscription. Onboarding records in Eploy's module that return incomplete schemas are flagged in a gap report with a recommendation to export the remaining data as a CSV complement to the API migration.

Eploy referral records link an employee to a referred candidate and include reward status. We map referral attribution to Crelate's referral source field on the Person record and preserve the referring employee name and reward status as structured fields. If the referring employee is not a Crelate User, we store the referral attribution on the candidate Person record.

Eploy Talent Pools are saved candidate collections used for future roles. We migrate pool memberships as Crelate Tags on the Person record, with the pool name preserved as the tag name. The customer chooses during scoping whether to create Crelate Segments (dynamic) or static Tags (manual) based on how they use talent pools in Eploy.

Eploy hiring manager assignments tie specific users to jobs and workflow stages. We migrate these as Crelate User assignments to the relevant Job records, with access permissions mapped to Crelate's role-based sharing model. Any role-based permissions that do not translate directly (e.g., granular stage-specific access) are documented for admin configuration post-migration.

Organisations add custom fields to jobs, candidates, and other objects in Eploy. We detect and map custom property schemas during scoping discovery, then create corresponding fields in Crelate. Field types are mapped: Eploy text to Crelate text, Eploy dropdown to Crelate picklist, Eploy date to Crelate date. Any Eploy custom fields without a clear Crelate equivalent are flagged for the customer to choose between creating a new custom field or collapsing the data into a notes field.

Assessment scores and results attach to candidate records in Eploy. We migrate available assessment data as structured custom fields where the API exposes them. Visual scores or formatted assessment outputs that cannot be mapped to structured fields migrate as document attachments linked to the Person record in Crelate.

Resume, cover letter, and compliance documents attach to candidates and jobs in Eploy. These are served as download URLs, not inline blobs. We enumerate all attachment URLs, download each file to temporary storage, then upload each to Crelate's attachment endpoint, preserving the original filename and linked record association. Large volumes of attachments extend migration time and require sufficient storage headroom; we flag this in scoping if the candidate-to-attachment ratio exceeds 10:1.

Email and SMS threads tied to candidates in Eploy migrate to Crelate Activity records as email or note entries on the Person record. Email content and timestamps transfer as Activity entries; SMS content migrates similarly if the API exposes it. Plain text formatting is preserved; rich HTML formatting may flatten during transit, and we document this in the validation checklist.