Migrate from StaffingSoft to BambooHR

StaffingSoft Candidate records map to BambooHR Employee records if the candidate was placed (via Assignment) and the employee is active in the HR system. Unplaced candidates map to BambooHR Applicant records in the ATS module. Contact details, employment history, skills, and status fields migrate 1:1. Any StaffingSoft candidate custom properties (e.g., sourcing channel, internal rating) migrate as BambooHR custom fields fetched via GET /v1/meta/fields before import. The StaffingSoft candidate status (active, inactive, placed) determines whether the record lands in BambooHR Employees or Applicants.

StaffingSoft Job Orders map to BambooHR Job postings. Requirements, qualifications, opening dates, and pipeline stage assignments migrate as BambooHR job fields. Job status (open, filled, cancelled) maps directly. The posting URL list from StaffingSoft's job board cross-posting history is preserved as a note field in BambooHR because posting credentials must be re-entered in BambooHR's job distribution settings. Any custom fields on the Job Order migrate as BambooHR custom fields scoped to the Job object.

Assignment is the core staffing entity in StaffingSoft's Staffing Edition, linking a Candidate to a Job Order with bill rate, pay rate, start date, and end date. BambooHR has no native Assignment object — placement data lives on the Employee record. We store StaffingSoft's bill_rate and pay_rate as BambooHR custom fields on the Employee record (custom numeric fields fetched via GET /v1/meta/fields during scoping), and start_date/end_date map to BambooHR's hireDate and a custom end_date__c field for temp or contract placements. Assignment status (active, completed, terminated) maps to BambooHR employmentHistoryStatus.

StaffingSoft Client records (company name, contact information, address, billing preferences) map to BambooHR as the employing organization context on the Employee record. In StaffingSoft's HR Edition the client object represents the employer; in BambooHR the employer context is implicit in the single-tenant account structure. Client address and billing details that cannot map to standard BambooHR Employee fields are stored as custom fields on the primary HR contact employee record.

Resume files stored in StaffingSoft's document management module are exported as file binaries and re-attached to the corresponding BambooHR Employee record. BambooHR's Document module supports employee file attachments including resumes. File naming conventions in StaffingSoft vary by deployment — we normalize file names to {employeeName}_{documentType}_{date} format before upload. PDF and DOCX formats transfer cleanly; formats not supported by BambooHR are flagged for the customer's admin to review.

StaffingSoft user accounts including recruiter assignments, team structures, and permission roles map to BambooHR Employee records. Owner IDs on StaffingSoft records (Candidate, Job Order, Assignment) are resolved by matching email against the BambooHR destination user list. Any StaffingSoft user without a matching BambooHR employee is held in a reconciliation queue for the customer's admin to provision before record import resumes. BambooHR user permissions are scoped per the BambooHR account's admin configuration post-migration.

StaffingSoft custom fields on candidates, job orders, and assignments require field-level mapping. We fetch the full BambooHR field metadata via GET /v1/meta/fields during scoping to retrieve custom field IDs, then map each StaffingSoft custom field type (text, dropdown, date, numeric) to the equivalent BambooHR custom field type. Lookup dependencies that reference StaffingSoft internal IDs are resolved to human-readable values or flagged as requiring manual verification. Custom field availability varies per BambooHR account, so IDs are fetched per customer rather than hardcoded.

Interview feedback, scorecards, and scheduling notes stored as activities against the StaffingSoft candidate record are extracted as note content and attached as BambooHR Notes on the corresponding Employee or Job Application record. Stage-specific ratings migrate as custom fields on the Job Application. Any StaffingSoft interview rating scale values are mapped to BambooHR custom picklist values created during schema setup.

StaffingSoft configurable pipeline stages per job order or globally map to BambooHR job application stages. Stage names and order transfer directly. StaffingSoft stage-specific automations (e.g., auto-email on stage entry) do not migrate and must be rebuilt in BambooHR's workflow builder post-migration. We document each StaffingSoft stage automation as part of the handoff inventory.

StaffingSoft custom report definitions and saved filters are not exportable as portable artifacts. We export report data as CSV from StaffingSoft before migration as a reference snapshot. BambooHR reporting is rebuilt using the BambooHR reporting interface with HR Insights dashboards. We provide a mapping table from each StaffingSoft report name to its equivalent BambooHR report configuration during the handoff.