Migrate from Whitecarrot.io to Recruit CRM & ATS

Whitecarrot.io Job records migrate to Recruit CRM Job Position. Job title, description, requirements, department, location, and employment type transfer directly. Job status (Draft, Open, Paused, Closed) maps to Recruit CRM status values. We flag the count delta during scoping: if the Whitecarrot.io Recruiter Pro plan holds 5 or fewer active jobs, migration lands cleanly on Essential; if more than 5 open jobs exist, we recommend upgrading to Recruit CRM Business before migration to avoid truncation.

Candidate profiles, contact information, application history, and stage progressions migrate 1:1. Whitecarrot.io stage names map to equivalent Recruit CRM pipeline stages using a migration-time transform. Email addresses serve as the dedupe key. Candidate source attribution and UTM fields migrate as custom fields if populated in Whitecarrot.io.

Whitecarrot.io screening question sets attached to jobs migrate as structured question records. Each question type (multiple-choice, free text, ranking) maps to an equivalent Recruit CRM custom field type. Answer data populates the corresponding custom field on the Candidate record. Conditional routing logic in Whitecarrot.io is documented in a mapping note rather than recreated, since Recruit CRM does not support conditional question branching at the candidate level.

Skills test configurations, test links, and candidate completion statuses migrate as structured records. Test score data transfers to Recruit CRM custom number fields. If the score is a pass/fail binary, it maps to a custom checkbox field. Automated scoring rubrics are preserved as a JSON attachment on the Candidate record for audit. We flag any test link that expires after migration since the original test URL may not remain active.

Video interview recordings and metadata (duration, view count, submission timestamp) migrate as binary blobs attached to the Candidate record in Recruit CRM. We preserve the original Whitecarrot.io access URL as a custom text field in case the destination platform requires re-authentication. Recruit CRM does not have a native video interview player; we document the playback format (mp4, webm) so the customer knows which format they are receiving.

Coding challenge configurations, candidate submissions, and automated scoring results migrate as structured data. Score rubrics and output formats (GitHub link, file attachment, test result JSON) are preserved as a structured JSON attachment on the Candidate record. Automated scoring values migrate to custom number fields on the Candidate. We flag any challenges that rely on Whitecarrot.io's integrated execution environment since that environment does not exist in Recruit CRM.

Scorecard templates and interviewer responses migrate to Recruit CRM as structured custom fields on the Candidate or as Notes with structured headers. Multi-interviewer scorecards are preserved with attribution to each interviewer. Aggregate ratings transfer to a custom number field. We map the scorecard section names to Recruit CRM custom field labels for readability.

Offer records migrate to Recruit CRM Offer with compensation details, e-signature status, and approval flow states preserved. Offer approval workflows in Whitecarrot.io are documented as a workflow inventory item: Recruit CRM's offer management supports approval flows but the configuration is manual. We flag any offers in Pending or Approved state that may require re-triggering of the approval sequence in Recruit CRM.

Psychometric test configurations and candidate results migrate to Recruit CRM custom fields. Test vendor integration details that are Whitecarrot.io-specific do not transfer since they are tied to Whitecarrot.io's own integrations. We migrate the result data (scores, completion status, vendor name) as structured custom fields so the customer retains the evaluation history even if the vendor connection must be re-established in Recruit CRM.

Whitecarrot.io User accounts and role assignments (Recruiter, Hiring Manager, Interviewer) migrate to Recruit CRM Users. Role name strings map to equivalent Recruit CRM permission sets. We resolve Users by email match during migration. Any Whitecarrot.io user without a matching Recruit CRM account is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Whitecarrot.io Career Site Builder configurations export as structured JSON records rather than rendered HTML pages. We provide the full JSON export and a field-level map so the customer's Recruit CRM admin can reconstruct the career site in Recruit CRM's site builder. Branding settings (logo, colors, fonts) migrate as configuration values that must be re-entered manually. This is a manual rebuild step, not an automated migration.

Active job board posting configurations (which boards, which jobs, posting history) migrate as structured reference records. We do not transfer active posting URLs, authenticated job board sessions, or LinkedIn/Indeed account credentials, which are tied to Whitecarrot.io's own integrations. The customer must re-authenticate each job board in Recruit CRM's integrations settings before reposting. We provide a posting configuration checklist to guide this step.