Migrate your Employ data

Jobs are the primary recruiting object in Employ, holding title, description, department, location, and status. Standard fields are stable and exportable via CSV or API. We map Job ID and posting status to the destination equivalent.

Candidates are the core person record in Employ, holding contact information, work history, and AI-generated evaluation data. AI interview scores are stored as metadata on the Candidate. We preserve the full candidate profile including score fields as custom properties in the destination.

Applications link a Candidate to a Job and track which stage of the hiring pipeline the applicant occupies. We preserve application history, stage timestamps, and any notes attached to the application.

Employ allows customizable pipeline stages per job. Stage names and counts vary by customer configuration. We map named stages to the destination pipeline stages, flagging any stages with no direct equivalent for manual assignment.

AI-generated interview evaluations are tied to the Candidate record but not exposed as a standalone object. We extract these as structured fields on the Candidate, which requires field-level mapping to any destination that does not have a native AI score property.

Employment eligibility verification records are associated with the hired Employee. They contain sensitive compliance data. We carry them as encrypted attachments to preserve audit trail integrity during migration.

Once a candidate is hired, the record transitions to an Employee object with employment details. We map Employee fields to the destination HRMS, preserving start date, department, manager, and employment status.

Employ assigns Users to roles such as Recruiter, Hiring Manager, and Admin. We extract role assignments and map them to destination role structures, which vary by target platform.

Employ supports custom fields on Jobs, Candidates, and Applications. These require field-level discovery during the scoping phase since there is no published schema documenting which custom fields exist per customer.

Job postings distributed to third-party job boards are tracked as configuration settings in Employ rather than as data records. We do not migrate these configurations as they are destination-specific; we instead recommend re-publishing job postings after migration.