Migrate from Jobylon to Crelate

Jobylon Job records map to Crelate's Position object (the Crelate equivalent of a Job or req). Standard fields (title, department, location, employment type) migrate directly. Per-company custom fields configured via Jobylon's /config/companies/{companyId}/job endpoint are pre-discovered during scoping and created as Crelate custom fields on Position before migration. Job status (active/closed/draft) maps to Crelate Position status.

Jobylon Applications map to Crelate Opportunities. Each Application represents a Candidate's progression through a Job's pipeline. We map application status to the nearest Crelate Opportunity stage, preserve the submission date as a custom field (original_application_date__c), and link the Opportunity to the corresponding Position via Crelate's job lookup. Active and inactive stage names require explicit mapping because Jobylon stages are free-text per company.

Jobylon Candidate records map to Crelate Contact. Candidates in Jobylon may have multiple Applications across Jobs. We deduplicate by email, merging application histories into a single Contact record with multiple Opportunity associations. GDPR-related fields (consent granted date, erasure request date) are carried as custom Contact properties (gdpr_consent_date__c, gdpr_erasure_date__c) since Crelate handles consent via its own GDPR tooling but accepts custom fields for historical compliance data.

Jobylon pipelines are per-Job and fully configurable with free-text stage names. We map active source stages to Crelate Opportunity stage values configured as a custom picklist on the Opportunity object. Inactive stages with assigned Lost Reasons are preserved as termination labels in a custom field (original_lost_reason__c). Stage ordering is preserved via Crelate's stage probability weights. This requires an extended discovery phase to enumerate all stage name variants across the customer's Jobs.

Jobylon Scorecards are tied to Pipeline Stages and record evaluations by specific Users (evaluators) with numeric ratings and free-text feedback. Crelate has no native scorecard object, so we map scorecard data to custom fields on the Opportunity: evaluator name (scorecard_evaluator__c), rating value (scorecard_rating__c), and feedback body (scorecard_feedback__c). Multiple scorecards per Application are flattened into a JSON string stored in a long-text custom field to preserve all evaluator data.

Jobylon custom fields are defined per-company via the Partner API with no global schema. Crelate custom fields are created per-core-record (Contact, Company, Opportunity, Position). We query the /config/companies/{companyId}/job endpoint during discovery for each company, generate a field map, pre-create all Crelate custom fields with matching logical names, then import values during the record migration phase. Dynamic custom fields must be confirmed as activated by Jobylon support before they appear in the API schema.

Jobylon Users (recruiters, hiring managers, admins) map to Crelate Users. We resolve by email match. Any Jobylon User referenced as an Owner or Assignee on Application or Job records without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Permission-level differences between Jobylon's configurable permission tiers and Crelate's user role model are flagged in the discovery report.

Jobylon Lost Reasons are predefined classification labels assigned when an Application moves to an inactive stage. Crelate has no native lost-reason object. We carry these as a custom picklist field (original_lost_reason__c) on the Opportunity record, preserving the source label so the customer's team can review and reconcile after migration.

Jobylon offer letter documents are stored as Application attachments. The Partner API exposes only attachment filenames and URLs, not document content. We export the attachment filenames and URLs as a custom field on the Opportunity (offer_letter_attachment__c) and flag that the actual document content cannot be migrated via API. The customer's admin must re-upload offer letters manually or via Crelate's document upload feature post-migration.

Jobylon assessor feedback (free-text evaluator notes tied to an Application) migrates to Crelate Note records linked via ContentDocumentLink to the parent Opportunity, preserving the author name, timestamp, and feedback body. If the feedback is tied to a specific stage in the pipeline, we add a custom field (feedback_stage__c) to indicate which pipeline stage the feedback was associated with.

Jobylon Candidates may reference a company entity. Where present, these map to Crelate Company records. The Jobylon company name becomes the Crelate Company Name field, used as the dedupe key during import. Company records are imported before Contact records so that the Company lookup is satisfied at the moment of Contact insert.

Jobylon engagement records (call logs, email metadata, meeting records) associated with Applications are exported and mapped to Crelate Task (for calls and general tasks) and Event (for meetings) records. Call disposition, duration, and meeting attendee lists are preserved as custom Task or Event fields. Email content migrates as a Note attached to the relevant Opportunity or Contact.