Migrate your Scout by Rebelware data

Jobs serve as parent containers for all candidate activity. We map Job records including title, description, department, location, and status. Job Board Integrations are preserved as configuration metadata on the Job record. Standard fields migrate cleanly; custom properties require explicit mapping at scoping.

Candidates are the primary records in Scout's data model. We map contact information, work history, and candidate status fields. Custom properties on Candidates require value-mapping against the destination schema. We flag any deprecated or internal-only fields that should not be exported.

Applications link Candidates to Jobs and carry Pipeline Stage data. We preserve the stage history and transition timestamps. Where destination systems use a different stage model, we map stages explicitly during the scoping call rather than leaving them to default assignment.

Scout uses a configurable pipeline with named stages such as Applied, Screening, Interview, Offer, and Hired. Stage names and counts vary by organization configuration. We require an explicit stage-mapping table from the customer before migration to ensure records land in the correct equivalent stage on the destination platform.

Interview Notes are free-text records attached to Candidates by individual interviewers. We extract the note content, author, and timestamp. If the destination system has structured note templates rather than free-form notes, we map the extracted content into the closest available field and flag any data that does not fit.

Candidate ratings are numerical scores assigned by interviewers or the hiring team. We preserve numeric ratings and their associated user assignments. Where the destination does not have a native rating field, we store the score as a custom numeric property on the Candidate record.

Scout supports flexible roles and user access levels. We map User records including name, email, role designation, and permission scope. Role names and permission structures differ significantly between Scout and most destination ATS platforms, so we require an explicit role-mapping session before migration to align access levels correctly.

Scout integrates with LinkedIn, Indeed, and other major job boards for posting and resume sourcing. We preserve integration configuration records and flag which ones require re-authentication or manual reconnection on the destination platform, since OAuth tokens and API credentials cannot be transferred between systems.

Scout generates performance reporting on job openings and applicant pipeline metrics. We extract report metadata and summary data. The destination platform's reporting structure may differ, so we map available metrics to the closest equivalent and flag any Scout-specific metrics that have no direct equivalent in the target system.

Scout supports custom fields on Candidates and Applications. We map custom field definitions and values, but each destination platform has its own custom field schema. We require a custom field mapping table from the customer before migration to ensure values land in the correct destination field.