Migrate from Employ to Recruit CRM & ATS

Employ Candidates map to Recruit CRM Candidates. The core contact fields (name, email, phone, work history, education) migrate directly. AI interview scores generated by Employ's AI Recruiter are stored as metadata on the Candidate; we extract these during the data audit, create a custom field on the Recruit CRM Candidate object, and write the score values during the load phase. We use the Recruit CRM Candidates API endpoint (POST /v1/candidates) for initial creation and update associated fields via the /associated-field endpoint with field_id and value pairs.

Employ Jobs map to Recruit CRM Jobs. Title, description, department, location, and job status transfer directly. We create Recruit CRM Jobs first during migration so that Job IDs are available for resolving Application-to-Job lookups during the Candidates and Applications load phases. Job posting status (Open, Closed, Draft) maps to Recruit CRM's status field.

Employ Applications link a Candidate to a Job and track pipeline stage. We map Applications to Recruit CRM's candidate-job association, preserving stage history and stage-entry timestamps as activity records. The Application-to-Candidate and Application-to-Job lookups are resolved using the IDs created during the earlier Job and Candidate load phases. Application notes migrate as Comments or activity entries against the Candidate record.

Employ allows per-customer pipeline stage configurations with no standard schema. We extract every active stage name during discovery and match them to Recruit CRM pipeline stages. Any Employ stage without a direct Recruit CRM equivalent is flagged for manual assignment before the Applications load phase to prevent candidates landing in a null or default stage. Stage-entry timestamps are preserved as activity records in Recruit CRM.

Employ AI Recruiter generates interview evaluation scores as metadata on the Candidate record, not as a standalone object. We identify all Candidates with AI scores during the data audit, extract the structured score values, create a custom field on the Recruit CRM Candidate object, and write the scores during the Candidate load phase. The field name is agreed with the customer during scoping. This extraction step is the primary reason migrations with high AI-evaluated candidate volume require additional time during discovery.

Employ I-9 and E-Verify records are regulatory compliance documents associated with the hired Employee. We carry these as encrypted file attachments linked to the Candidate or Employee record in Recruit CRM rather than triggering re-verification. Before migration, the customer confirms whether Recruit CRM will accept pre-completed I-9 forms; some compliance configurations require manual re-entry at the destination, which we flag explicitly in the pre-migration compliance summary. The original document files are base64-encoded and uploaded as ContentDocument records.

Employ Employee records created after a candidate is hired (holding start date, department, manager, employment status) map to Recruit CRM Candidates with a hired status flag. We preserve the employment start date, department, and manager as fields on the Recruit CRM Candidate record. If Recruit CRM is used purely as an ATS, hired candidates remain as Candidates with status fields; if the agency uses Recruit CRM for internal placements, the record structure is agreed with the customer during scoping.

Employ Users assigned as Recruiters, Hiring Managers, or Admins map to Recruit CRM Users. Role names from Employ are mapped to Recruit CRM role equivalents during scoping. We extract all User records and email addresses to create a reconciliation queue: any Employ User without a matching Recruit CRM User is held for the customer to provision before record migration proceeds.

Employ supports custom fields on Jobs, Candidates, and Applications with no published schema documenting which fields exist per customer. We conduct a field-level discovery during scoping, extracting the complete list of active custom fields and their data types from the source export. We create matching custom fields on the Recruit CRM equivalent objects (via the Recruit CRM API or admin interface) before the load phase begins. Custom field creation is a prerequisite for the Candidate and Application phases.

Employ tracks job board distribution settings as platform-specific configuration rather than as data records. These settings are not transferable to Recruit CRM because the destination's job multiposting configuration (available on Enterprise, reaching 5,000+ channels) requires re-authentication and re-setup by the customer. We document the list of configured boards in the migration summary and recommend setting up Recruit CRM's Job Multiposting on the Enterprise plan after go-live.