Migrate from Wizehire to BambooHR

WizeHire Jobs map to BambooHR Job Openings. The job title, description, location, department, and status (open/closed/paused) transfer directly. BambooHR's plan tier determines the maximum open job openings (5 on Core, 25 on Pro, 50 on Elite), so we flag any account exceeding the target tier limit before migration. WizeHire's job board distribution settings (100+ sites) are not carried over; these require manual reconfiguration within BambooHR's job board integration settings post-migration.

WizeHire Candidate profiles (name, email, phone, resume file URL, application date) map to BambooHR Applicants. The candidate's primary applied-to job becomes the initial BambooHR Job Opening assignment. Where a single person has applied to multiple WizeHire job postings (creating duplicate WizeHire records), we identify these during the pre-migration deduplication step and present the customer with a consolidation decision before loading into BambooHR, since BambooHR also creates separate applicant records per application unless manually linked.

WizeHire Application records track a Candidate's progression through pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) with timestamps at each transition. We preserve the stage label and transition timestamps as BambooHR Custom Fields on the Applicant record (e.g., wh_stage__c, wh_screening_date__c, wh_offer_date__c) since BambooHR's native ATS tracks current stage but does not store a full stage-transition audit trail per Applicant without custom fields.

WizeHire stores DISC+ personality profile results (Dominance, Influence, Steadiness, Conscientiousness dimensions) as structured data per Candidate. BambooHR has no native DISC+ or personality assessment field. We export the DISC+ dimension scores as numeric custom fields (wh_disc_d__c, wh_disc_i__c, wh_disc_s__c, wh_disc_c__c) on the BambooHR Applicant record, and we flag that the customer should configure a BambooHR partner assessment integration if ongoing DISC+ testing is required post-migration.

WizeHire hiring managers create scorecards with custom evaluation criteria per Job or per Application. Scorecard templates (criteria names and weightings) and per-candidate scores transfer as custom text or numeric fields on the BambooHR Applicant record (e.g., wh_score_overall__c, wh_score_criteria_1__c). We export the criteria labels as part of the record structure so the customer's admin can map them to named custom fields in BambooHR. Scorecard templates themselves do not have a native BambooHR equivalent and are handled as configuration records in the migration inventory.

WizeHire stores custom pre-screening question text and candidate responses per application. We export question text and candidate answers as a set of custom fields on the BambooHR Applicant record (e.g., wh_sq_question_1__c, wh_sq_response_1__c). BambooHR does not have a native screening question library object, so each question-response pair is stored as a separate custom field pair. The customer's admin recreates the question library within BambooHR's custom field editor as part of post-migration configuration.

WizeHire integrates with third-party background check providers and stores a pass/fail flag and provider name per Candidate or Application. We export the background check status and provider as a custom text field on the BambooHR Employee record (for hired candidates) or Applicant record (for in-process candidates). BambooHR's Compliance module handles I-9 and E-Verify but does not store legacy background check results from an external ATS; these load as historical reference fields requiring admin review post-migration.

WizeHire Interview Guides are structured text documents attached to Jobs that outline questions and evaluation criteria. BambooHR has no native interview guide object. We export interview guide content as structured text records and handle them as configuration data in the migration inventory, with a recommendation to the customer to rebuild these as BambooHR onboarding task templates, hiring checklist items, or a linked document library accessible from the Job Opening record.

Hiring team notes on WizeHire Candidate profiles (author name, note body, timestamp) map to BambooHR Note records linked to the Employee or Applicant. We preserve the note body, author, and timestamp. Notes attached to hired candidates link to the BambooHR Employee record; notes on active applicants link to the Applicant record.

WizeHire users apply tags to filter and categorize Candidates. We export tag labels as a comma-separated text field or as BambooHR custom list fields on the Applicant record (e.g., wh_candidate_tags__c). The customer's admin decides during scoping whether to store tags as a text field or as defined list values for filtering in BambooHR's applicant views.

WizeHire provides over 100 industry-tested job description templates stored as organizational configuration assets. We export template titles and body text as structured records in the migration inventory. BambooHR does not have a native job template library; the customer's admin uses the exported templates as reference content when creating new Job Openings in BambooHR's editor.

WizeHire's default hiring pipeline (Applied, Screening, Interview, Offer, Hired, Rejected) is customizable per account. We export the custom stage names and their ordering. BambooHR's ATS uses customizable stages per Job Opening; we map the exported stage names to BambooHR stage labels and document any stage that has no direct equivalent in the customer's BambooHR plan tier for admin review.

WizeHire user accounts (hiring managers, admins) are exported with name, email, and role. We map these to owner assignments on BambooHR Job Openings and Applicants by email match. Any WizeHire user without a matching BambooHR user account goes to a reconciliation queue; the customer's BambooHR admin provisions the account before migration continues. Archived WizeHire users are mapped as inactive BambooHR users to preserve historical ownership.

WizeHire's in-app candidate messaging threads may have delivery reliability gaps according to user reports. We flag message history for explicit scoping during discovery: if reliable message records exist in WizeHire, we export them as Note records or email-style entries on the corresponding BambooHR Applicant or Employee. If message history is inconsistent or inaccessible, we document the gap in the migration inventory and advise the customer to confirm with WizeHire support whether a full message export is available before we proceed.