Migrate from Scout by Rebelware to BambooHR

Scout Job records map to BambooHR Job postings within the ATS module. We map Job title, description, department, location, and status directly. Job Board Integrations (LinkedIn, Indeed) cannot be transferred as OAuth tokens are scoped to Scout's application and are not portable. We preserve the integration configuration as metadata in the migration report and document which job boards were connected so the customer can re-authenticate within BambooHR's distribution settings. Job status (open, paused, closed) maps to BambooHR's job status field.

Scout Candidate records map to BambooHR Applicants in the ATS module. We map contact information (name, email, phone), work history, and status fields directly. BambooHR's ATS module maintains Applicants as distinct from the core BambooHR Employee records that are created during onboarding after a hire is confirmed. We flag this distinction during scoping: if the customer expects candidate records to automatically convert to Employee records, that conversion step is manual in BambooHR and must be handled as a post-migration process, not as part of the data migration.

Scout Applications link Candidates to Jobs and carry the pipeline stage and application timestamps. We map Applications to BambooHR's ATS application records, preserving the stage assignment and stage-transition timestamps. BambooHR's ATS uses a configurable pipeline stage model that must be explicitly mapped to Scout's current stage configuration before any Application records are placed. We require a screenshot of Scout's current pipeline setup during scoping and build the explicit mapping table before production migration begins.

Scout uses a fully customizable pipeline with organization-specific stage names and counts. There is no universal Scout stage model; 'Phone Screen' in one organization may not exist in another. We request the current pipeline configuration screenshot during scoping and build an explicit stage-mapping table for BambooHR's ATS pipeline stages. Stages that have no equivalent in BambooHR's default model are flagged for the customer to decide whether to create a custom stage or consolidate into an existing one.

Scout Interview Notes are unstructured free-text fields attached to Candidates by individual interviewers. BambooHR's ATS module has structured evaluation fields and a notes area on Applicants, but it does not enforce a fixed template for interviewer feedback. We extract the note content, author, and timestamp from Scout and place them in BambooHR's Applicant notes section or a designated custom text area. Where the source note contains structured rating values or scoring that could be parsed, we extract and populate the corresponding BambooHR custom field. Any note content that does not fit a structured field becomes a free-text fallback flagged for manual reconciliation during validation.

Scout Candidate Ratings are numerical scores assigned by interviewers or hiring managers. BambooHR's ATS module does not have a native structured rating field, so we create a numeric custom field on the Applicant record during schema setup and map the rating values into it. Where ratings are associated with specific stages or evaluators, we append evaluator context to the custom field's metadata. Customers who rely on aggregated scoring dashboards in Scout should be aware that BambooHR's native reporting does not include a rating aggregation view; this may require a custom report or a third-party integration.

Scout User Roles with names, permission scopes, and user assignments require explicit mapping to BambooHR's role and access model. BambooHR does not have a direct Scout equivalent for ATS-specific hiring role permissions; instead, BambooHR uses a combination of HRIS employee roles and ATS-specific administrative settings. We map Scout user names and emails to BambooHR Employee records and document the Scout role assignments as metadata so the customer can configure the corresponding access levels in BambooHR's Settings > Employee Permissions and ATS administration areas.

Scout integrates with LinkedIn, Indeed, and other major job boards using OAuth tokens scoped to Scout's application. These tokens cannot be extracted or transferred to BambooHR. We preserve a configuration record listing which job boards were connected, the job postings that were distributed, and the last-sync date. The customer must re-authenticate each job board within BambooHR's job distribution settings after migration. We include this step explicitly in the cutover checklist delivered alongside the migration.

Scout generates performance reporting on job openings and applicant pipeline metrics including source, time-to-hire, and pipeline conversion rates. We extract report metadata and summary data from Scout's performance reports and place them as descriptive records in BambooHR's Reports section or as documentation records. BambooHR's reporting structure differs from Scout's; the customer rebuilds the specific report layouts using BambooHR's report builder. We provide the source metrics from Scout as a reference so the rebuild accurately reflects the original measurement dimensions.

Scout supports custom fields on Candidates and Applications with string-based property names. BambooHR uses a numeric field ID model: custom field definitions must be fetched per-customer via GET /v1/meta/fields before any data can be written. We create the matching custom field definitions in BambooHR during schema setup, fetch the resulting numeric field IDs, and use those IDs to populate values during data migration. Value mapping for dropdown, multi-select, and checkbox custom fields requires a value translation table that we build during scoping, as Scout's enumerated values may differ from BambooHR's allowed values.