Migrate from Scout by Rebelware to Crelate

Scout Jobs migrate to Crelate Jobs as parent containers for all candidate activity. We map title, description, department, location, status, and salary range (where present). Job board distribution settings from Scout are preserved as configuration metadata but require re-authentication with each board in Crelate. Crelate's salary range fields on Job postings support state compliance requirements and migrate where source data is present.

Scout Candidates map to Crelate People records. Contact information, work history, and candidate status fields transfer directly. Custom properties on Scout Candidates require a custom field mapping table against Crelate's People custom fields; we build this table during scoping and validate type compatibility (text vs. picklist vs. date) before import. People records are inserted before Applications so that the parent lookup is satisfied at insert time.

Scout Applications link Candidates to Jobs and carry pipeline stage data. In Crelate, the Application appears as an Activity record associated with the People record and linked to the Job. Stage history and transition timestamps migrate as custom fields on the Activity record where Crelate's native stage model does not capture the full history. The source Job ID is preserved as a custom field for reconciliation.

Scout pipeline stages are organization-configurable with no standard naming convention. We request a screenshot of Scout's pipeline configuration during scoping and build an explicit stage-mapping table before any candidate records are exported. Each Scout stage maps to a Crelate pipeline stage value or, where the destination system uses a different stage model, we place the record in the closest equivalent and flag the mapping for admin review. Stage probability percentages migrate where present in Scout.

Scout Interview Notes are free-text records attached to Candidates by individual interviewers. We extract note content, author, and timestamp. Crelate's Activity Forms support structured field mapping where the destination has defined rating or evaluation fields; free-text note content is placed in Crelate's Activity body field. Any structured rating values embedded in Scout note text are flagged during validation for manual population into Crelate's structured fields. Interviewer attribution migrates as the Activity author.

Scout Candidate ratings are numerical scores assigned by interviewers or the hiring team. We preserve numeric ratings and their associated user assignments. Where Crelate has a structured rating field on the People record or an Activity Form, we map ratings directly. Where no native rating field exists, we create a custom People field (e.g., scout_rating__c) to preserve the values and flag for admin review.

Scout Users migrate to Crelate User records by email match. Role designation and permission scope from Scout map to Crelate User Roles and permissions configured in Settings | Advanced Settings | User Roles. API access must be enabled for non-admin migration users in Crelate Advanced Settings before the migration begins. Users without a matching Crelate User go to a reconciliation queue for admin provisioning.

Scout integrations with LinkedIn, Indeed, and other job boards use OAuth tokens scoped to Scout's application and are not transferable to Crelate. We extract the integration configuration as metadata and document which boards were connected in Scout. Re-authentication with each job board is required in Crelate and is included in the migration cutover checklist as a manual step for the customer's admin.

Scout performance reports contain job-level and pipeline-level metrics. Report metadata and summary values migrate as Crelate Saved Searches and custom Reports. Crelate's Advanced Reports and Analytics (included in Business tier) covers pipeline metrics, time-to-hire, and source attribution. Complex historical reports with specific calculation logic may require manual recreation in Crelate's reporting builder.

Scout custom fields on Candidates and Applications migrate to equivalent Crelate custom fields on People and Activity records. We build a custom field mapping table during scoping that specifies source field name, destination field API name, data type, and any value transformation required. Crelate's Business tier supports up to 10 Advanced Custom Fields; larger custom field schemas may require Business Plus or Enterprise tier. Picklist values require an explicit value map where source and destination picklist values differ.

Scout engagement records beyond Interview Notes (general tasks, notes attached to Candidates or Applications) migrate to Crelate Activity records. Task status, priority, due date, and assignee migrate. Attachments referenced in Scout note content migrate as Crelate document attachments linked to the Activity record where the destination supports file storage on the Activity object.

Scout tags used for candidate classification migrate to Crelate Tags. Crelate supports Tags on People, Jobs, and Activities with tag categories that map to Scout's tag taxonomy. During scoping we confirm whether Scout tags are used for pipeline segmentation (in which case they may warrant a dedicated picklist field in Crelate) or for general labeling (in which case native Tags are sufficient).