Migrate from Simplicant to BambooHR

Simplicant Jobs map to BambooHR Jobs. We export job title, description, department, location, and current pipeline stage. The BambooHR Job must be created before any Applicants are imported so that the jobId reference is satisfied on the applicant record. Job status (open, paused, closed) migrates as-is. Simplicant's jobRequisitionId becomes a custom field in BambooHR for reconciliation.

Simplicant Candidate records map directly to BambooHR Applicants. We preserve first name, last name, email, phone, application date, source attribution, stage history, and any attached evaluation scores. The Applicant is linked to the corresponding BambooHR Job record via jobId lookup. Application history and stage progression are stored as custom fields or in a notes section where BambooHR's applicant schema does not natively capture pipeline traversal.

Simplicant Departments migrate as BambooHR Departments. Department is a foundational lookup field on both Jobs and Employees, so we import departments before Jobs and before any Employee records. Department name and any department head assignment map directly.

Simplicant Locations migrate as BambooHR Locations. Like Departments, Location is a lookup field used across Jobs and Employees. We import Locations before Jobs and Employees so that the geographic metadata is available as a reference value during record creation.

Simplicant Interview Packets bundle structured evaluation forms with scoring. BambooHR's applicant model does not have a native structured evaluation form equivalent. We map completed interview packet responses to BambooHR Applicant custom fields where the customer's BambooHR plan supports them, or to a structured note attached to the applicant record. We flag any form schema that cannot be represented in BambooHR's flat field model during scoping.

Simplicant Offer records (salary, start date, terms, e-signature status) map to BambooHR Offers where the customer's BambooHR plan includes the Offers feature. Offer status (pending, accepted, declined, retracted) migrates. E-signature audit trails are linked records that may require additional handling depending on document storage availability in Simplicant and plan tier.

Simplicant Hiring Pipelines define stage sequences per job type. BambooHR Jobs have configurable stages. We map Simplicant pipeline stage names and order to BambooHR Job stage names, flagging any stages with custom automation rules (auto-reject, auto-advance) that have no BambooHR equivalent. The customer rebuilds pipeline automation logic in BambooHR's workflow tools post-migration.

Simplicant stores structured screening scores and evaluation ratings per candidate per stage. We export the raw score data and map it to BambooHR applicant custom fields or to the closest native rating field. Score ranges and weighting logic (which vary by organization and form) are preserved as metadata in a custom field for reference during BambooHR admin review.

Simplicant User accounts (recruiters, hiring managers, interviewers) with role-based permissions are mapped to BambooHR Employee records. We use email as the match key. Where a Simplicant User has no corresponding BambooHR Employee (e.g., an external interviewer who is not an employee), we flag the record for the customer's admin to decide whether to create a minimal Employee record or handle assignment within BambooHR's sharing model.

Simplicant Onboarding Records with completed task sequences and assignee rules migrate as BambooHR Onboarding checklists. BambooHR's onboarding is task-based rather than workflow-driven, so complex branching automation with conditional rules does not transfer. We preserve task completion status and assignee data; the customer rebuilds any conditional onboarding logic in BambooHR's task configuration post-migration.

Simplicant resumes, cover letters, and HR files are extracted from document storage where plan tier enables export. We map these as file attachments on the corresponding BambooHR Applicant record. Availability depends on whether the Careers Site API or bulk export is enabled on the Simplicant plan; manual export fallback may be required, which extends the data extraction timeline.

Simplicant custom fields on Jobs and Candidate profiles migrate to BambooHR custom fields. Custom field definitions and data types are inferred from the Simplicant export results. In BambooHR, custom field IDs must be fetched per-account via GET /v1/meta/fields — they cannot be hardcoded across customers. We retrieve the meta field list during scoping, create matching custom fields in the BambooHR account, and use the per-account field IDs during data import.