Migrate from SmartRecruiters to BambooHR

SmartRecruiters Candidate records map to BambooHR Applicant records. The mapping pulls firstName, lastName, email, phone, location (city/state/country), and social profile URLs. Screening answers stored against the candidate profile migrate as custom fields on the BambooHR Applicant if the BambooHR account has matching custom field definitions; otherwise they are flagged for manual entry. Tags and consent decisions are preserved as BambooHR custom fields or applicant notes.

SmartRecruiters Job Postings map to BambooHR Jobs. The job title, location, department (mapped via SmartRecruiters department ID to a BambooHR Department), employment type, and description body transfer directly. SmartRecruiters experience level and job function are mapped to the BambooHR Job Description or stored as custom fields. Active and paused posting status maps to BambooHR open and closed job status. Historical job postings closed before migration land as closed jobs in BambooHR.

SmartRecruiters Applications link a Candidate to a Job Posting and carry pipeline stage, source channel, and application date. In BambooHR, the Application is represented by the Applicant record itself linked to a Job, rather than as a separate application object. We map the SmartRecruiters application date to the BambooHR Applicant submission date, source to a custom field, and pipeline stage to a custom field or hiring stage if BambooHR's Applicant Tracking is configured with stages. SmartRecruiters Application status of Hired maps to BambooHR's Hire Completed workflow trigger.

SmartRecruiters custom fields are organization-scoped with no standard set; they are only discoverable at runtime via the /configuration endpoint. We run a mandatory pre-migration discovery pass to enumerate every SmartRecruiters custom field (fieldId, valueLabel pairs) before mapping begins. Each discovered field is then evaluated against the destination BambooHR account's existing custom field definitions. New BambooHR custom fields are created in the applicant's field set before import to prevent silent value loss during insert.

SmartRecruiters User records (recruiters, hiring managers, admins) map to BambooHR Users by email address. Role assignments (recruiter versus hiring manager) are preserved in a custom field on the BambooHR User or in the BambooHR Job requester field. A SmartRecruiters User without a matching BambooHR User is held in a reconciliation queue for the customer's admin to provision the account before record import proceeds.

SmartRecruiters Departments are referenced by ID and label on Job Postings and carry a description. We map the department ID-to-label and look up the corresponding Department in BambooHR (created during BambooHR onboarding) to assign the correct department reference on each migrated Job. If a SmartRecruiters Department has no BambooHR equivalent, it is created as a new BambooHR Department before job migration begins.

Candidate attachments from SmartRecruiters (resumes, cover letters, portfolio files) are downloaded via the SmartRecruiters Attachment API and re-uploaded as files linked to the corresponding BambooHR Applicant record. File names and MIME types are preserved. SmartRecruiters does not expose attachment content as base64 in all API responses; we use the /attachments/{attachmentId}/content endpoint with streaming retrieval to avoid incomplete file pulls on large binary files.

SmartRecruiters Interview Scorecards capture structured evaluation data (rating, strengths, concerns, recommendation) embedded in candidate evaluation records. BambooHR has no native scorecard object. We export scorecard data as structured notes attached to the BambooHR Applicant, with a template format (Evaluator Name, Date, Rating, Recommendation, Comments) so the evaluation content remains readable. We flag this as a manual-handoff item for your admin to rebuild in BambooHR's hiring notes or a third-party evaluation tool.

SmartRecruiters assigns per-job hiring team members with roles (recruiter, hiring manager, interviewer, sourcer). BambooHR's job structure supports a single job owner and a requester field but does not have structured multi-role team assignment. We map the SmartRecruiters hiring team to a combination of BambooHR job ownership and a custom multi-select field listing the team members and roles. This is documented during migration for your admin to finalize in BambooHR's job settings.

SmartRecruiters Interview Records include scheduling information, interviewer assignments, date and time, and outcome notes. We map interview date, interviewer name, and disposition to a formatted note attached to the BambooHR Applicant. SmartRecruiters scheduling links (calendar invites) do not migrate as functional calendar events; they are preserved as reference links in the interview note.

SmartRecruiters Offer records include compensation details, status, and candidate linkage. BambooHR has no standalone Offer object. We map offer status (extended, accepted, declined, withdrawn) and compensation details to formatted notes on the BambooHR Applicant record. Offer status of Accepted can be used to pre-populate the BambooHR Hire Completed workflow trigger.

SmartRecruiters supports structured screening questions on job postings and applications. Screening answers stored at the application level migrate as custom fields on the BambooHR Applicant. The mapping is field-by-field: each SmartRecruiters screening question maps to a BambooHR custom field of the matching type (text, select, or checkbox). If the BambooHR account does not have the corresponding custom field, we create it during the pre-migration schema setup phase.