Migrate from Screenloop to Bullhorn ATS & CRM

Screenloop Candidate records (name, email, phone, location, application date, source, stage history log) map to Bullhorn Candidate. The stage history log transfers as a structured text field or as a series of Note records with timestamps, depending on the volume. Bullhorn CandidateId becomes the parent reference for all related Interview, Scorecard, Reference, and Background Check records that follow. Deduplication uses email as the primary key; we flag duplicate email addresses in a reconciliation report before final import.

Screenloop Job records (title, department, location, employment type, description, active vs. closed status) map to Bullhorn JobOrder. Job-specific custom fields extract during the audit phase and map to Bullhorn custom fields on JobOrder. Active status preserves as JobOrder status; closed jobs import with their final status for historical pipeline reporting. We flag any job-specific integration settings (e.g., job board distribution) that require manual reconfiguration in Bullhorn.

Screenloop's configurable pipeline stages (e.g., Applied, Screening, Interview, Offer) map to Bullhorn JobOrder Status values and, for placement-driven workflows, to Placement Track Status values. Stage ordering and stage-specific rules export from Screenloop and recreate as Bullhorn Status picklist values ordered to match the original pipeline flow. Stage transition timestamps become Note records or a custom activity log depending on the destination Bullhorn edition's Custom Object headroom.

Screenloop Scorecards contain structured ratings, free-text feedback, and AI-generated notes from the Interview Intelligence layer. We extract the rating criteria and weights per job and map them to Bullhorn custom fields on a Custom Object (e.g., scorecard_rating_overall__c, scorecard_communication_score__c). If the destination Bullhorn edition is Bullhorn ATS (2 Custom Object limit) and the customer has multiple scorecard templates, we consolidate into a single Custom Object with template-type and section fields, and store the free-text feedback as Notes attached to the Candidate. Bullhorn Support must provision the Custom Object using the Custom Object Setup Sheet before migration begins.

Screenloop Interview Records (scheduled date, interviewer assignment, interview type, duration, outcome) map to Bullhorn Note and Task records attached to the Candidate. The Interview Intelligence transcript text migrates as a Note with the body set to the full transcript. Audio recording files cannot be programmatically extracted from Screenloop; we flag this during scoping and advise the customer to request audio files directly from Screenloop support if required for compliance or legal retention purposes. Bullhorn's standard Task record covers interview scheduling and outcome tracking.

Screenloop's Modern Referencing feature collects referee name, relationship to candidate, submission date, and soft-skill feedback. This maps to a Bullhorn Custom Object (e.g., CandidateReference__c) with fields for referee name, relationship, submission date, and feedback summary. If the destination Bullhorn edition does not have Custom Object capacity remaining after scorecard and background check mapping, the feedback migrates as a Note attached to the Candidate with a standardized prefix for identification.

Screenloop Background Check records include check type, provider, status, and outcome summary. The structured result data maps to a Bullhorn Custom Object (e.g., BackgroundCheck__c). Raw PDF reports from third-party providers cannot be pulled programmatically from Screenloop; we flag this as a document retrieval step and advise the customer to request exports directly from their background check provider. Bullhorn does not natively integrate with all background check vendors; we document the vendor list for manual re-integration post-migration.

Screenloop's Interviewer Training library tracks module completion per user and assessment scores. This data maps to a Bullhorn Custom Object (e.g., InterviewerTraining__c) attached to the User record, with fields for module name, completion date, and score. The actual training content (video, slides, assessments) does not transfer; Bullhorn does not host training content natively. We provide a mapping of module names to Bullhorn's own training resources and recommend the customer rebuild training materials in Bullhorn's learning management or link to external hosting.

Screenloop User accounts (name, email, role — Admin, Hiring Manager, Recruiter, Interviewer, team assignment) map to Bullhorn User. Owner-to-candidate associations preserve so interview attribution remains intact after migration. We match by email as the dedupe key. Any Screenloop user without a matching Bullhorn User record goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import begins. Inactive Screenloop users migrate as inactive Bullhorn Users to preserve historical assignment data.

Screenloop custom fields on Candidates, Jobs, and Interviews (text, number, date, single-select, multi-select) export with their data types and current values. We apply a field-level mapping step during the audit phase, converting Screenloop field types to the closest Bullhorn equivalent: single-select maps to Bullhorn picklist, multi-select maps to Bullhorn multi-select picklist or a Custom Object with a related list, number maps to Bullhorn number or currency depending on context. Bullhorn field name length limits (40 characters) may require truncation of longer Screenloop custom field names.

Screenloop accumulates stage changes, interview outcomes, and note additions as candidate pipeline events. There is no documented bulk-export endpoint for historical transaction logs, so we reconstruct stage history by exporting individual candidate records where accessible. Large accounts (10,000+ candidates) may experience incomplete event timelines; we flag gaps in the audit report and advise requesting historical export assistance from Screenloop support before migration begins. The reconstructed history migrates as a series of dated Note records on each Candidate in Bullhorn.

Screenloop attachments on Candidates and Jobs (resumes, cover letters, portfolio files) are exported as files from the admin CSV export. Bullhorn stores these as ContentDocument records linked via ContentDocumentLink to the Candidate or JobOrder. We map the file name, type, and binary content, and set the ContentDocumentLink visibility to AllUsers or InternalUsers depending on the file's intended audience. Orphaned attachments (files with no parent record) are flagged in a separate report for manual disposition.