Migrate from JOIN to Recruit CRM & ATS

JOIN Candidates map directly to Recruit CRM Candidates. We extract contact info (name, email, phone, location), work history, education, skills tags, source attribution, and current pipeline stage via the JOIN API. The candidate's current stage is resolved against the per-job stage mapping table built at scoping. Any JOIN custom fields on Candidate are extracted as associated_fields and require customer confirmation of the Recruit CRM field ID equivalents before migration.

JOIN Jobs map to Recruit CRM Jobs with title, description, department, location, employment type, and posting status transferred directly. Job status (active, paused, closed) maps to the Recruit CRM status field. Job department and employment type become custom dropdowns or text fields in Recruit CRM depending on the plan configuration.

JOIN Applications link a Candidate to a Job with applied date, referral source, and rejection or offer flags. Recruit CRM models this relationship as a Candidate record with associated Job records via the associated-fields endpoint. We map the application date to the candidate's applied_date on the job association, and the rejection or offer status to the Recruit CRM status field on the associated job.

JOIN does not enforce a universal stage schema — each job carries a custom stage sequence. We extract the full stage list per job during the scan phase and build a customer-specific mapping table. Recruit CRM uses a configurable stage list per job. Where JOIN has fewer stages than the target job, we collapse intermediate stages and preserve stage-entry dates as associated field metadata so timing context is not lost.

Interview evaluations and structured feedback stored in JOIN migrate as Candidate notes or custom fields in Recruit CRM. Where Recruit CRM's job associated fields support structured evaluation data, we populate those fields using the JOIN scorecard values. Free-text interview notes migrate as attached notes on the Candidate record.

JOIN supports employer-defined custom fields on the Job object. These have no standardised schema. We extract the full schema during scan, then map each custom field to a Recruit CRM job custom field equivalent or flag it as a free-text property. Recruit CRM exposes custom fields via the API with explicit field IDs that must be confirmed before import.

JOIN Candidate custom fields migrate to Recruit CRM job associated fields (the per-candidate, per-job property store). The associated_fields endpoint in Recruit CRM accepts field_id and value pairs for each candidate-job combination. We extract all JOIN Candidate custom fields during scan and require the customer to confirm Recruit CRM field ID mappings before migration. Unmapped fields land as free-text associated fields.

Candidate resume files and supporting documents export from JOIN with non-standard filenames derived from internal IDs. We normalise filenames to a consistent convention (CandidateName_JobTitle_Date) during the export phase to prevent filename collisions in bulk downloads and ensure files are identifiable upon ingestion. Files are uploaded to Recruit CRM as linked attachments on the Candidate record.

JOIN Owners map to Recruit CRM Users. We resolve owners by email match. Any JOIN Owner without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive JOIN owners are mapped to inactive Recruit CRM users to preserve assignment history.

JOIN does not expose email threads, scheduled interview events, or activity log entries through a documented API endpoint. Internal activity timeline records cannot be extracted via API and must be exported manually as a CSV from the JOIN dashboard before cutover. We ingest the CSV alongside the API extract and load the activity data as Candidate notes in Recruit CRM. We flag this requirement at scoping and coordinate the manual export timing with the customer.

JOIN Candidate skills tags and source attribution (e.g., LinkedIn, referral, job board) map to Recruit CRM skills fields or custom multi-select fields. Skills are migrated as comma-separated or multi-select values depending on the Recruit CRM field configuration at the destination.