Migrate from Wizehire to Crelate

WizeHire Jobs map to Crelate Job records. Each Job carries title, description, status, location, and department. We map WizeHire's job status (Open, Closed, Paused) to Crelate's Job status field and preserve the original posting date and any internal job ID as a custom field for reconciliation. Job templates and industry-specific posting structures export as structured text and are delivered as configuration documents for the customer's admin to recreate as Crelate Job templates.

WizeHire Candidate records map to Crelate Contact records. The critical step is candidate deduplication: WizeHire creates a separate Candidate record each time the same person applies to a different Job. We identify duplicate Candidates by matching on email address and flag them for customer review before loading. The customer decides whether to merge duplicates into a single Crelate Contact with multiple application records, or to keep them separate. We cannot automatically merge because WizeHire does not expose a candidate deduplication API, and the merge decision affects how Crelate's submission history renders.

WizeHire Application records link a Candidate to a Job and store status progression through pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) with timestamps at each stage transition. We map Application status to Crelate's Candidate Submittal status field and preserve the stage history as custom date fields or a notes block attached to the submittal record. The Application creation date becomes the Crelate submission date.

WizeHire stores DISC+ personality profile results per Candidate as structured data (Dominance, Influence, Steadiness, Conscientiousness dimensions). Crelate has no native DISC+ field. We export the four DISC+ dimension scores and the composite profile type and map them to four numeric custom fields on the Crelate Contact record (disc_dominance__c, disc_influence__c, disc_steadiness__c, disc_conscientiousness__c) plus a text custom field for the profile type. The customer's admin creates these fields in Crelate during the schema design phase before migration begins.

WizeHire hiring manager scorecards with custom criteria map to Crelate Activity Forms. We export scorecard templates as configuration documents listing the evaluation criteria and scoring rubric, and map individual candidate scores to Crelate Activity Form entries attached to the Candidate Submittal record. Crelate's Activity Forms support custom field types including numeric ratings, which align with WizeHire's numeric score values. Scorecard templates are not reusable assets in Crelate's ATS; we deliver them as a written template inventory for the customer's admin to configure manually.

WizeHire Job-level custom screening questions and Candidate responses per application export as question-and-answer pairs. We map these to Crelate's custom field schema on the Contact or the Candidate Submittal, depending on whether the question applies to the person or the application. Crelate's custom questionnaire and application form builder supports short/long answer, picklist, and numeric field types. We generate a field mapping spreadsheet during scoping that the customer's admin uses to pre-create the destination fields before migration.

WizeHire stores background check pass/fail flags and provider names on the Candidate or Application record. These migrate as a custom picklist field on the Crelate Contact record (bg_check_status__c with values Pass, Fail, Pending, Not Started) and a text field for the provider name. Full background check reports are third-party documents that WizeHire does not store as exportable files; we note this limitation and recommend the customer maintain the original report files outside the ATS migration scope.

WizeHire's default pipeline (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Crelate's configurable pipeline stages. We export the stage names and their order, then configure matching stage values in Crelate's Job pipeline settings before migration. Custom stage labels from the customer's WizeHire account are preserved in a custom field on each submittal for audit and reporting continuity.

WizeHire Candidate notes from hiring team members (stored with author and timestamp) map to Crelate Notes attached to the Contact record. Notes migrate as plain text with author name and timestamp preserved. We flag notes that were added after the most recent Application status change to ensure they appear in the correct chronological position in Crelate's activity timeline.

WizeHire tags applied to filter and categorize Candidates migrate to Crelate's Contact labels or tags. We export the full tag list per Candidate and map each tag to a Crelate Contact label. If the customer uses a large number of unique tags, we recommend they review and consolidate tags during scoping to avoid exceeding Crelate's label field capacity.

WizeHire provides over 100 industry-tested job templates as account-level organizational assets. These export as structured text records. Crelate does not have a native reusable job template library feature. We deliver job templates as a written inventory document organized by industry and role type, which the customer's admin can use to populate Crelate's job description fields manually or via Crelate's bulk import for future job postings. Templates are out of scope as a data load into Crelate's configuration.

WizeHire Interview Guides attached to Jobs outline structured interview questions and evaluation criteria. These export as structured text per Job. Crelate does not have a native Interview Guide object. We deliver interview guides as written configuration documents linked to the corresponding migrated Job for the customer's admin to reference or enter into Crelate's job-level notes. Interview guides are out of scope as native Crelate records because no equivalent object exists in the destination system.