Migrate from Jobylon to BambooHR

Jobylon Jobs map to BambooHR Job Openings. The Job title, department, location, and description migrate directly. Jobylon's per-company custom fields on Jobs (configured via /config/companies/{companyId}/job) require pre-migration schema discovery per company account; we query each company's configuration endpoint during discovery, then map custom fields to BambooHR custom fields or the closest standard field. BambooHR's Job Opening caps per tier (5/25/50) are flagged during scoping — customers with more active jobs than the destination tier permits must either upgrade or accept inactive archived jobs in BambooHR.

Jobylon Applications map to BambooHR Applicants attached to a Job Opening. The application date, current stage, source channel, and rejection reason (Lost Reason) transfer. If the Application references a Candidate who already exists as an Employee in BambooHR (hire-from-within scenario), we map to the existing Employee record rather than creating a duplicate Applicant. Jobylon's application-stage history timeline is preserved as a custom note or activity entry on the Applicant record.

Jobylon Candidates deduplicate by email address before migration. Active Candidates with open Applications migrate as BambooHR Applicants attached to a Job Opening. Candidates who have already been hired (identified by a 'Hired' status or a 'hire date' custom field) migrate as BambooHR Employee records with the hire date preserved from Jobylon. We carry any GDPR-related fields (consent status, erasure request dates) as custom fields in BambooHR unless the destination's Compliance Intelligence module provides a native equivalent.

Jobylon pipeline stages are free-text and per-job, with no standardisation across organisations. We map each active stage name to the closest BambooHR Job Opening stage (Applied, Phone Interview, On-site Interview, Offer, Hired, or Rejected). The original Jobylon stage name is preserved in a custom field original_stage__c for audit. Inactive stages with assigned Lost Reasons are mapped to the Rejected stage with the Lost Reason label carried as a custom field rejection_reason__c. Customers review and approve the stage map before cutover to avoid pipeline process mismatches.

Jobylon Scorecards are tied to Pipeline Stages and record evaluator ratings and comments per Application. BambooHR has no native scorecard object, so scorecard ratings and evaluator feedback migrate as custom fields on the Applicant record (e.g., scorecard_rating__c, evaluator_name__c, evaluation_notes__c). The scorecard schema (field names, rating scale) is extracted from Jobylon during discovery and translated into custom field definitions in BambooHR before migration. We flag that BambooHR's hiring module does not surface scorecard data in a structured evaluation view — the data is present as fields on the Applicant but not displayed as a scorecard summary.

Jobylon custom fields are defined per-company via the Partner API and may include dynamic fields that require Jobylon support activation before they appear in the schema. We query the /config/companies/{companyId}/job endpoint for each company during discovery and generate a field map before any data moves. Dynamic fields that are not yet activated are flagged in the discovery report and must be activated by Jobylon support before the migration schema is finalised. BambooHR custom fields are created via the BambooHR API before import begins. The migration does not include dynamic form logic from Jobylon; the form structure must be rebuilt manually in BambooHR's applicant intake form editor.

Jobylon Users (recruiters, hiring managers, admins) map to BambooHR Employee records. We resolve by email match. The migration does not provision BambooHR user accounts — the customer's BambooHR admin creates the destination users and assigns roles (Employee, Admin, Limited) before migration. User permission levels are not migrated because BambooHR's permission model uses role-based access control that must be configured in the destination separately.

Jobylon Lost Reasons are predefined classification labels assigned when an Application moves to an inactive pipeline stage. We carry these as a tagged custom field rejection_reason__c on the Applicant record in BambooHR rather than a native object. The set of unique Lost Reasons across all Pipelines is enumerated during discovery and provided as a picklist of custom field values.

Free-text evaluator notes and assessor feedback are exported from Jobylon as structured comment records with author, timestamp, and body content. We map these to BambooHR Notes attached to the Applicant record, preserving the original author name and timestamp. If the feedback includes structured rating data, we split it into custom fields (rating_value__c, feedback_body__c) rather than storing it solely as a free-text note.

Jobylon offer letter documents are stored as attachments associated with Applications. We export the attachment filenames and URLs but do not migrate the document content itself due to the lack of a bulk document export endpoint in Jobylon's Partner API. The document URLs are provided as a reference list attached to the Applicant record in BambooHR. The customer's team must re-upload offer letter documents to BambooHR manually or via e-signature integration post-migration.