Migrate from Screenloop to Crelate

Screenloop Candidate records (name, email, phone, location, application date, source) map directly to Crelate Contact. Stage history reconstructs from Screenloop's pipeline stage-transition log and migrates as Crelate Activity records with timestamps preserving the original stage-entry date. We apply Crelate's Field Mappings during import so that mapped custom candidate fields copy to Contact columns; unmapped fields remain as Activity Form Responses searchable via advanced query.

Screenloop Job postings (title, department, location, employment type, description, status) map to Crelate Job records. Active versus closed status preserves. Any Screenloop job-specific custom fields migrate as Crelate Custom Fields on the Job record type, with the customer's admin configuring field mappings in Settings | Custom Forms post-migration if those fields appear on application intake forms.

Screenloop's configurable pipeline stages (Applied, Screening, Interview, Offer, etc.) export with their ordering and stage-specific rules. Stage-to-stage transition timestamps migrate as Crelate Activity records with ActivityType set to Pipeline Stage Change, preserving the original Screenloop timestamp for audit. Crelate's custom Recruiting Workflow (20-activity limit on Business tier) should be configured before migration to capture future stage progression.

Screenloop scorecards include structured ratings, free-text feedback, and AI-generated notes. We extract the full scorecard schema (rating criteria, weighting, free-text fields) per job during the audit phase and output a mapping spreadsheet. Crelate Application Forms are recreated by the customer's admin using the mapping spreadsheet as a guide; the rating criteria align to Crelate Custom Fields on the Contact record. We do not migrate scorecard templates as executable code.

Interview records (scheduled date, interviewer assignment, interview type, duration, outcome) map to Crelate Activity records with ActivityType = Interview. Interviewer assignment resolves by matching the Screenloop interviewer email to a Crelate User record. The AI-generated scorecard note from Screenloop's Interview Intelligence layer migrates as a long-text Activity Form Response on the Crelate Activity. Raw audio recording files cannot be pulled programmatically and are flagged for direct request to Screenloop support.

Screenloop Interview Intelligence generates transcripts stored in the proprietary Interview Intelligence layer. We export the transcript as structured text and load it into Crelate as a multi-line Activity Form Response attached to the Interview Activity record. The transcript is searchable in Crelate but does not appear as a native field on the Contact. We advise customers to verify transcript export completeness with Screenloop support before migration.

Screenloop's Modern Referencing feature collects referee name, relationship, submission date, and soft-skill survey responses. Reference records migrate to Crelate as Activity records with ActivityType = Reference, preserving referee name and relationship. Survey response content migrates as Activity Form Responses. Reference submission URLs do not transfer; the customer's admin recreates reference request workflows in Crelate using email templates.

Background check records (check type, provider, status, outcome summary) migrate as Crelate Activity records with ActivityType = Background Check. We export the structured result data and flag that raw PDF reports from third-party providers (Checkr, Sterling, etc.) must be requested directly from the provider or re-initiated in Crelate's background check integration. Outcome status fields map to Crelate Activity Form custom fields for structured visibility.

Screenloop's Interviewer Training library completion records per user (module name, completion date, assessment score) migrate to Crelate as custom fields on the Contact record. The actual training content (videos, slides, assessments) does not transfer; we provide a content audit spreadsheet listing each completed module so the customer's admin can re-assign training in Crelate's built-in training tools or a third-party LMS.

Screenloop User accounts (name, email, role: Admin, Hiring Manager, Recruiter, Interviewer) map to Crelate User records. We resolve by email match. Owner-to-candidate associations preserve so interview attribution remains intact in Crelate. Users without a matching Crelate account go to a reconciliation queue for the customer's admin to provision before the production migration phase begins.

Custom fields on Candidates, Jobs, and Interviews export with their data types (text, number, date, single-select, multi-select) and current values. Crelate custom fields are pre-created in the destination environment before data load. Field type compatibility is verified during mapping: Crelate field mappings cannot map a date field to a monetary field, so mismatched types are flagged and resolved in the mapping spreadsheet before import.

Screenloop tags stored as multi-checkbox candidate properties migrate to Crelate multi-select picklist fields on the Contact record. We pre-create the picklist values matching the source tag vocabulary during the schema design phase. Tags used for content classification on Job records migrate to Crelate Job custom fields with the same treatment.