Migrate from Jobsoid to BambooHR

Jobsoid Candidates map to BambooHR Employee records. Candidates who were hired become active Employees with their BambooHR Employment History populated from the hire date and job title sourced from the Jobsoid primary job assignment. Candidates in pipeline stages with no hire outcome (rejected, withdrawn, disqualified) are imported as Inactive Employee records with a bamboo_status = 'Candidate - Not Hired' designation and the original source job opening noted in a custom field. We preserve candidate email, phone, address, source attribution, and custom field values field-to-field where field names match or a mapping table is provided during scoping.

Jobsoid allows one Candidate to apply to multiple Jobs with a designated primary position. BambooHR Employee records are single-entity. For candidates with multiple Jobsoid applications, we set the primary application as the BambooHR Employment History entry and store additional application references in a custom text field candidate_prior_jobs__c as a semicolon-delimited list of non-primary job names. This preserves the multi-application context without breaking BambooHR's single-record employee model.

Jobsoid Jobs map to BambooHR Job Openings. We map Jobsoid job status (Open, Closed, Draft) to BambooHR Job Opening status (Open, Draft). Jobsoid location and department assignments map to BambooHR Job Opening location and department fields. We verify the destination BambooHR account's ATS module tier (Core 5 openings, Pro 25, Elite 50) against the migration scope before import and flag any account that will require a tier upgrade or a phased opening import. The BambooHR Jobs API (POST /employees/{id}/hire) is not the same as the Job Openings ATS API; we use the correct /jobOpening endpoints.

Jobsoid allows fully custom stage names and stage counts per pipeline. BambooHR's ATS uses a standardized set of Hiring Status values (Applied, Phone Screen, Interview, Offer, Hired, Not Hired). We consolidate multiple Jobsoid pipeline stages into one or two BambooHR Hiring Status values during scoping—for example, Phone Screen and Technical Interview both map to 'Interview' in BambooHR. We document the stage mapping table and surface any candidate records that will change status as a result of the consolidation before migration runs.

Jobsoid Departments map directly to BambooHR Departments. Both platforms expose departments as organizational lookup values. We extract the full department list from Jobsoid's lookup API and create matching Department records in BambooHR before any Job Opening or Employee import so that the department reference is resolved at insert time rather than through post-migration repair.

Jobsoid Locations map to BambooHR Locations. Both platforms store location as an organizational lookup tied to job openings. We preserve Jobsoid's location name, address (where available), and Google Maps resolution as the BambooHR Location fields.

Jobsoid Divisions map to BambooHR Divisions if the destination account has the BambooHR organizational structure feature enabled (available on Pro and Elite tiers). We check the feature availability during scoping and flag if Division-level reporting is required but the account is on Core tier.

Jobsoid custom candidate field values map to BambooHR custom employee fields. Custom fields are available on BambooHR Premier and Enterprise plans only; Core and Pro tiers use only standard employee fields. If the migration scope includes custom fields and the destination is on a Core or Pro plan, we flag the tier gap during scoping and recommend upgrading before migration. Fields without a destination equivalent are documented in a gap report and preserved as a CSV alongside the migration.

Jobsoid's candidate Source field (referral, job board, direct) maps to a BambooHR custom text field candidate_source__c. Source values are transferred as-is where recognized; unrecognized source labels (custom job board names, specific UTM-tagged sources) are preserved in the field and flagged in the gap report for the customer's admin to standardize post-migration.

Jobsoid candidate activities (interview events, emails, notes) are embedded in the candidate profile and are not independently exportable as a separate API resource. We extract activity text from candidate profile exports where available, or reconstruct a best-effort timeline from the activity block in CSV/Excel exports. These migrate as chronological Employee File notes in BambooHR with the original activity type (Interview, Email, Note) stored in a bamboo_activity_type__c tag. If activity data is critical, we recommend exporting candidate profiles as PDFs before migration to capture the full activity history with formatting intact.

Jobsoid candidate attachments and resumes relocate to BambooHR Employee Files. We extract binary files from Jobsoid exports (or the file storage path if accessible), re-attach them to the corresponding BambooHR Employee record using BambooHR's file upload API, and link by Employee ID. File names and upload timestamps are preserved. If Jobsoid attachments are inaccessible through export alone (browser-only uploads), we recommend downloading through Jobsoid's interface before migration begins.