Migrate from JobAdder to BambooHR

JobAdder Candidates map to BambooHR Employee records. We map standard profile fields (name, email, phone, address, employment history, skills) to their BambooHR equivalents. Candidates who are placed employees get their placement history preserved as a custom field block on the Employee record. Candidates who are not yet placed migrate as Employees with an Application record linked to a BambooHR Job Requisition. The Candidate's source tag and pipeline status migrate as custom fields since BambooHR does not have a native candidate sourcing channel taxonomy.

JobAdder Job Orders map to BambooHR Job Requisitions within the ATS module. We preserve job title, description, requirements, status, assigned consultant, and the job board posting history as a text block in a custom field (posting history does not migrate as live integrations). Job Order status values (Active, On Hold, Filled, Cancelled) map to BambooHR Job Requisition status equivalents. The assigned consultant assignment migrates as a BambooHR Hiring Manager assignment.

JobAdder Client records map to BambooHR Company records. Client company name, address, industry, and primary contact details migrate directly. The Client Portal association and BD pipeline status (from JobAdder's Opportunity object) do not map to a BambooHR native field; we store the original BD stage as a custom text field on the Company record and flag that the customer should review whether a separate CRM is needed for active business development tracking post-migration.

JobAdder Contact records (distinct from Candidate records) map to Company contact entries in BambooHR. The contact's name, email, phone, and role at the client company migrate to the contact block on the corresponding BambooHR Company record. Where a Contact shares an email with an existing Candidate record, we resolve the deduplication by preferring the Candidate record and marking the Contact as an inactive company contact.

JobAdder Placements (placed candidates tied to a Job and Client) map to a BambooHR custom object we provision during migration. The custom object preserves bill rate, pay rate, markup percentage, start date, end date, and timesheet period fields as custom numeric and date fields. Placements are linked to the corresponding BambooHR Employee (the placed candidate) and to the BambooHR Company (the client) via lookup relationships. We create this custom object schema in BambooHR before migration begins.

JobAdder Opportunities (business development pipeline records) have no native BambooHR equivalent because BambooHR is not a CRM. We do not create a standalone Opportunity object in BambooHR. Instead, we migrate the Opportunity stage and value as a custom text field on the associated Company record. Active BD pipeline status is preserved as a record for the customer's review; if ongoing CRM activity is required, we recommend a dedicated CRM integration or a separate CRM platform post-migration.

JobAdder User accounts (recruiters and consultants) migrate as inactive BambooHR User records to preserve assignment history on Candidate, Job, and Placement records. The inactive User record carries the consultant's name and email. Active user provisioning in BambooHR must be handled separately by the customer's admin; we provide a provisioning checklist during the reconciliation step. This ensures that Candidate and Placement assignments do not show as unassigned after migration.

JobAdder Task records linked to Candidates, Jobs, or Clients migrate to BambooHR Tasks. We map task title, description, due date, status, priority, and assignee (resolved by email to the corresponding BambooHR User). Completed tasks carry their historical status; open tasks migrate as open. Tasks without a valid assignee go to a reconciliation queue for the customer's admin to resolve before production migration.

File attachments on JobAdder Candidate profiles (CVs, cover letters, certifications, portfolio files) migrate as binary file records associated with the corresponding BambooHR Employee. We preserve original filenames and MIME types. Attachments without an associated Employee record (e.g., attachments on Job Orders) migrate as files attached to the corresponding Job Requisition. Attachment volume and total file size are profiled during discovery to size the migration job appropriately.

JobAdder custom fields on Candidates, Jobs, and Clients migrate as BambooHR custom fields. We discover the full custom field schema during discovery (requiring a test export from JobAdder), generate field-level mappings, and provision the corresponding custom fields in BambooHR before migration. Custom field types (text, number, date, dropdown) map to their BambooHR equivalents. Custom fields referencing JobAdder-specific picklist values require manual value recreation in BambooHR's field configuration.

Tags applied to JobAdder Candidates and Jobs (e.g., sourcing channel, vetting status, skill tags) migrate as comma-separated text in a custom text field on the corresponding BambooHR Employee or Job Requisition. The semantic taxonomy of tags is preserved in the data but must be recreated as a formal taxonomy in BambooHR; we document the full source tag list during scoping for the customer's admin to review.