Migrate from Smart Recruit Online to BambooHR

Smart Recruit Online Candidate records map to BambooHR Candidate records with the candidate's name, email, phone, location, and employment preferences preserved. Application history attached to the candidate (status changes, timestamps, assigned hirers) migrates as part of the candidate record or as linked application records depending on the BambooHR ATS data model at the time of migration. We preserve the Smart Recruit Online candidate ID in a custom field for audit traceability. Custom field values from Smart Recruit Online's CustomField array map to BambooHR custom fields only if the field type is supported (single-select dropdown or short text); unsupported field types are flagged during scoping.

Smart Recruit Online Job records map to BambooHR Job Posting records. We preserve the job title, description (with HTML formatting stripped or preserved depending on BambooHR's job board format support), location, department, function, type of employment, experience level, and any CustomField values. Job status (Open, Closed, Draft) migrates as the BambooHR Job Posting status. The Smart Recruit Online reference number becomes the BambooHR job reference field.

Smart Recruit Online Posting records (job advertisements linked to Jobs via jobAdId) are migrated as content within the BambooHR Job Posting. The actual distribution to job boards (Indeed, LinkedIn, ZipRecruiter, etc.) is Smart Recruit Online-controlled and does not transfer as live board listings. We provide a job board reposting checklist as part of the migration handoff package so the customer can manually republish active jobs to their chosen boards in BambooHR.

Smart Recruit Online Application records (linking a Candidate to a Job with current status) map to BambooHR Application records. Application status history, stage timestamps, and assigned hirers migrate. Pipeline stage names and values from Smart Recruit Online must be mapped to BambooHR's application status options during the pre-migration field audit. Applications with no matching candidate or job in the destination are held in a reconciliation queue.

Smart Recruit Online Hirer records (internal users who create or own Jobs and Applications) map to BambooHR Employee records or User accounts depending on migration scope. If the scope includes onboarding records, hirers become Employees in BambooHR with their own employee profiles. If the scope is ATS-only, hirers become BambooHR User accounts with appropriate permissions for hiring access. We resolve by email match against the BambooHR destination.

Smart Recruit Online pipeline stages are tenant-configured and vary by job. We extract the current stage definitions during the pre-migration audit and map them to BambooHR application status values. Stage order and associated automations are documented for the customer to manually configure in BambooHR. Stage probability percentages do not have a direct BambooHR equivalent and are preserved in a custom field if required for reporting continuity.

Smart Recruit Online Department and Function (structured fields on Job objects with id and label) map directly to BambooHR Department values. We migrate these as reference data during the foundation data phase before any candidate or application records. Any department not yet existing in BambooHR is created during migration.

Smart Recruit Online CustomField objects (fieldId/valueId/valueLabel) map to BambooHR custom fields only where field type is compatible. BambooHR supports single-select dropdown and short text custom fields. Multi-select, checkbox, date, and numeric custom fields from Smart Recruit Online are flagged during scoping as unsupported. For picklist-style custom fields, we validate value-label continuity and map the Smart Recruit Online value labels to BambooHR dropdown options. The migration team builds a full custom field audit report during scoping showing every custom field, its type, and the recommended mapping or flag for manual action.

Smart Recruit Online workflow rules, approval chains, and stage-triggered actions are configuration objects, not data records. We do not migrate workflow definitions as data. We export the workflow definitions as a written inventory document listing each active workflow, its trigger conditions, actions, and the recommended BambooHR workflow or BambooHR ATS stage automation equivalent. The customer's HR admin rebuilds these manually in BambooHR post-migration.

Smart Recruit Online offer records (available on higher tiers) with status and details migrate to BambooHR as part of the Employee record created upon hire. Offer templates and approval workflows require manual setup in BambooHR. We preserve offer status history, offer details (compensation, start date, title), and any notes in custom fields on the BambooHR Employee record. The BambooHR integration with Smart Recruit Online (listed on BambooHR Marketplace) supports automatic creation of new employees in BambooHR from hired candidates, which can be enabled post-migration.

Resume files and attachments associated with Candidates and Applications can be exported from Smart Recruit Online. We preserve file metadata (filename, upload date, file type) but file URLs require re-hosting since source storage is Smart Recruit Online-controlled. We provide the exported files in a structured directory and the customer uploads them to BambooHR or a linked document storage system post-migration.