Migrate from Whitecarrot.io to Crelate

Whitecarrot.io Job records (title, description, requirements, status, location, department) map directly to Crelate Job records. We validate the Recruiter Pro job-count cap during scoping: any migration exceeding 5 active jobs requires either a tier upgrade or an archivation strategy before import. Job associations to pipeline stages map to Crelate's job status workflow. Crelate's branded job portal can be configured post-migration using the migrated job configuration data.

Whitecarrot.io Candidate profiles map to Crelate Contact records. Candidate contact information, application history, stage progressions, and source attribution migrate 1:1. We map Whitecarrot.io stage status values to Crelate Application status equivalents. Any Candidate without an email address is flagged for review before import to prevent orphaned records in Crelate's Contact model.

Whitecarrot.io does not have a separate Company/Account object; employer information lives inside Candidate records. We extract employer names and any associated metadata from Candidate records and merge them into Crelate Company records before Contact import. The resulting Company record is then linked back to the migrated Contact via Crelate's Contact-Company lookup relationship.

Whitecarrot.io screening question sets attached to Jobs migrate as structured question objects with question type (multiple-choice, free text, ranking, single-choice), question text, and conditional routing logic preserved in a structured JSON export. We map these to Crelate Application Form fields: multiple-choice maps to Crelate picklist or multi-select, free text maps to long answer, and ranking maps to Crelate ranking field or custom field type. Conditional routing logic is preserved in field notes and documented for manual reconfiguration in Crelate's form builder.

Whitecarrot.io Skills Test configurations and candidate completion statuses migrate as structured data mapped to Crelate custom fields on Contact records (test name, completion status, score). Test score data transfers as numeric or categorical values depending on the destination field type configured during schema design. Automated scoring rubrics are preserved in a structured export map for the customer's admin to re-implement in Crelate's form scoring if needed.

Whitecarrot.io video interview recordings and metadata (duration, view count, submission timestamp) migrate as binary blob references. We preserve the original download URLs or access links from Whitecarrot.io and store them as structured data on the corresponding Crelate Contact record. Crelate does not have a native video interview player; the customer's team uses the preserved links or downloads the blobs to a storage bucket and links from Crelate. We flag any platform-specific storage limits and recommend a blob storage strategy during scoping.

Whitecarrot.io coding challenge configurations, candidate submissions, and automated scoring results migrate as structured data mapped to Crelate custom fields on Contact records (challenge name, submission status, score). Scoring rubrics are preserved as structured export data for the customer's admin to re-implement if the destination workflow includes automated evaluation steps.

Whitecarrot.io scorecard templates, interviewer responses, and aggregate ratings migrate as Crelate Activity Forms. Multi-interviewer scorecards are preserved with attribution to each interviewer resolved via User email matching. Crelate's field mappings feature (which copies form answers to Contact, Company, or Opportunity fields) is configured during migration to map scorecard values to the appropriate target fields on the candidate's Contact record. Scorecard templates are rebuilt in Crelate's form builder using the migrated structure.

Whitecarrot.io Offer records (compensation details, e-signature status, approval flow states) map to Crelate Opportunity records. Compensation fields map to Crelate Opportunity monetary fields (Amount, probability, expected close date). E-signature status migrates as a custom field; approval flow states are flagged for manual re-triggering in Crelate's approval workflow configuration. We document the original approval chain structure for the customer's admin to rebuild in Crelate.

Whitecarrot.io User accounts and role assignments (Recruiter, Hiring Manager, Interviewer) map to Crelate User records. Role name strings map to equivalent Crelate role names. Users without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Whitecarrot.io psychometric test configurations and candidate results migrate as structured data. Test vendor integration details that do not export in a standard format are preserved in a structured JSON export map rather than mapped directly. The customer's admin uses the export map to reconfigure psychometric testing integrations in Crelate or a connected third-party tool.

Whitecarrot.io report definitions and historical analytics data export as static data snapshots. Custom reports on Teams Pro migrate as saved query configurations. Pre-built job reports transfer as structured data for the customer's admin to rebuild in Crelate's Advanced Reports and Analytics module. We do not migrate report definitions as executable code.