Migrate from Webrecruit to Recruit CRM & ATS

Webrecruit candidate profiles including contact details, application history, stage progression, and GDPR consent flags map directly to Recruit CRM Candidates. The consent timestamp and boolean flag from Webrecruit migrate to custom fields on the Recruit CRM Candidate record to ensure UK regulatory compliance post-migration. Candidates with withdrawn or expired consent are flagged in the migration output and excluded unless the customer explicitly requests otherwise.

Webrecruit job records (title, description, department, location, status, posting dates) map to Recruit CRM Job records via the Recruit CRM Jobs API endpoint. Active and archived jobs migrate with status preserved; the customer decides whether to publish migrated jobs immediately or stage them for review. We flag any jobs with custom fields that lack equivalents in Recruit CRM for manual field creation post-migration.

Each Webrecruit Application links a Candidate to a Job with a timestamp and current stage. We preserve the full application timeline including rejection dates, withdrawal status, and stage history. The mapping resolves Candidate and Job references in Recruit CRM by performing a pre-import lookup to establish slugs before linking application records.

Webrecruit pipeline stages map to Recruit CRM stages on a 1:1 basis where stage names align. Bespoke stages such as aptitude tests, competency assessments, and other non-standard evaluation steps flag as unmappable and are documented separately. These stages require manual reconfiguration in Recruit CRM; we provide a stage inventory with names and sequence positions for the customer to recreate.

Webrecruit hiring managers assigned to jobs map to Recruit CRM User records by email match. We extract hiring manager assignments from job records and create User references in Recruit CRM, resolving any hiring manager that lacks a corresponding user account to a reconciliation queue for the customer to provision before final import.

CVs, cover letters, and attachments stored per Webrecruit application migrate as files attached to the corresponding Recruit CRM Candidate or Application record. File blobs are exported from Webrecruit and re-uploaded via the Recruit CRM file API with the parent record type and ID resolved before each attachment insert.

Webrecruit custom fields vary by account and require field-level mapping during scoping. We export field definitions and values, then map them to Recruit CRM custom fields of equivalent type (text, number, date, picklist, checkbox). Fields without a matching Recruit CRM equivalent are flagged in the migration output for manual re-creation by the customer post-migration.

Webrecruit stores candidate GDPR consent as a boolean flag with a timestamp per record. UK law requires this status to be preserved in the destination system. We export consent timestamp and flag alongside each candidate record and map them to dedicated custom fields in Recruit CRM. Suppression list compliance and withdrawal request handling are documented for the customer's admin to configure post-migration.

Webrecruit user accounts (name, email, role, permissions) map to Recruit CRM Users. We resolve users by email address during import and map Webrecruit role names to the closest Recruit CRM permission set. The customer's admin reviews role mapping during scoping and approves the mapping before user import begins.

Webrecruit approval workflows define job requisition routing from creation to posting. These do not migrate as executable code. We export workflow step definitions and document the sequence, approvers, and conditions for the customer's admin to recreate in Recruit CRM's workflow builder post-migration.