Migrate from Jobylon to Recruit CRM & ATS

Jobylon Jobs map to Recruit CRM Jobs as the primary record container. Standard fields (title, department, location, description) transfer directly. Per-company custom fields defined at /config/companies/{companyId}/job require pre-migration schema discovery; we query the configuration endpoint per company, then map each custom field to Recruit CRM's job-associated custom fields, preserving the original field label and data type. Active and inactive job status migrates as-is.

Jobylon Applications link a Candidate to a Job and track workflow status through pipeline stages. We migrate the full stage-history timeline with timestamps, preserving stage names as a custom field if they do not map to a Recruit CRM pipeline stage. Application status (active, inactive, withdrawn, rejected) maps to Recruit CRM's candidate job application status field. Lost reasons from inactive stages migrate as tagged properties on the application record.

Jobylon Candidate records map to Recruit CRM Candidates with email used as the primary dedupe key. Where a Candidate has multiple Applications in Jobylon, we merge application histories under a single Recruit CRM Candidate record. GDPR-related fields (consent flags, erasure dates) carry as custom properties unless Recruit CRM's native GDPR fields are available on the customer's plan. Multi-language candidate data migrates without transformation.

Jobylon's free-text pipeline stages per job do not map directly to a standardised Recruit CRM stage set. We conduct a discovery pass to collect every distinct stage name across all pipelines, then map each to the closest Recruit CRM pipeline stage equivalent. Unmapped stage names preserve as a custom field on the candidate job application record for audit. The customer reviews and approves the stage map before migration begins.

Jobylon Scorecards tied to pipeline stages record evaluator ratings and assessor feedback. We export the scorecard schema, rating values, evaluator name, and timestamp. Recruit CRM's candidate rating and evaluation system receives these as structured entries linked to the candidate job application. If the customer uses a custom scorecard template, we map the template fields to Recruit CRM custom fields on the job.

Jobylon Users (recruiters, hiring managers, admins) map to Recruit CRM Users by email match. We resolve the owner reference on Jobs, Applications, and scorecards to the corresponding Recruit CRM User. Any Jobylon User without a matching Recruit CRM User enters a reconciliation queue for the customer's admin to provision before record import continues.

Jobylon Lost Reasons are predefined classification labels assigned when an Application moves to an inactive stage. These have no native Recruit CRM equivalent as a standalone object. We carry them as a tagged text property on the candidate job application record, preserving the original label so the customer's team can filter by loss reason in Recruit CRM's search and reporting.

Free-text evaluator notes and assessor feedback export as structured comment records from Jobylon. We preserve the author, timestamp, and content body, mapping them to Recruit CRM's candidate notes or activity log entries linked to the relevant candidate job application. Author attribution resolves via the User mapping established in the discovery phase.

Jobylon per-company custom fields for Jobs and Applications are discovered via the /config/companies/{companyId}/job endpoint. Dynamic custom fields that require Jobylon support activation are flagged during discovery; if not confirmed as active, we note the gap in the migration scope and exclude them from the field map. We create matching custom fields in Recruit CRM before migration begins, using the job role association to replicate the per-job scoping that Jobylon uses.

Offer letter documents and details are stored as attachments in Jobylon. We export attachment URLs and filenames but do not migrate document content because Jobylon's API does not expose offer letter body content. We recommend the customer's admin downloads offer letter PDFs from Jobylon separately and re-uploads to Recruit CRM after migration or stores them in a document management system linked from the candidate record.