Migrate from Whitecarrot.io to BambooHR

Active job records in Whitecarrot.io map to BambooHR Job Opening objects if the customer licenses BambooHR's ATS module. Job title, description, requirements, location, and employment type transfer as structured fields. The BambooHR ATS module must be active at scoping because job opening creation requires a corresponding Job Department and Job Location in BambooHR's organizational structure. If the ATS module is not licensed, we transfer job data as a structured JSON export for manual recreation.

Candidate records in Whitecarrot.io map to BambooHR Applicant records if the ATS module is licensed. Contact information, application date, source, and current pipeline stage transfer. Stage labels are mapped to BambooHR Applicant Stage values (Applied, Phone Screen, Interview, Offer, Hired, Rejected). If the ATS module is not licensed, candidate records transfer as structured employee pre-hire records in BambooHR's onboarding section, though the application history and pipeline progression do not have native equivalents.

Whitecarrot.io screening question sets attached to jobs have no direct equivalent in BambooHR. We export the complete screening question structure (question text, answer type, required flag, conditional routing) as a structured JSON document. The customer's BambooHR admin uses this export to recreate screening logic in BambooHR's custom form builder or to create a PDF screening guide attached to the job opening. Skills tests and psychometric test configurations export similarly as structured records for manual rebuild.

Whitecarrot.io skills test configurations, test links, and candidate completion scores do not have a native equivalent in BambooHR. We export the test name, duration, passing threshold, and candidate score as structured data mapped to BambooHR custom fields on the Applicant record if the ATS module is active. Automated coding challenge scoring results export as a JSON attachment. Any third-party test vendor integration details do not transfer between platforms.

Whitecarrot.io video interview recordings and metadata (duration, view count, submission timestamp) do not have a native equivalent in BambooHR. We export video access links or download URLs as structured records and flag any platform-specific storage limits in Whitecarrot.io. The customer's admin must determine whether to store video files in BambooHR's document storage (if the ATS module supports attachments) or in a separate cloud storage solution, then update the candidate record with a reference link.

Whitecarrot.io interview scorecard templates, interviewer responses, and aggregate ratings do not map directly to any BambooHR object. Multi-interviewer scorecard data with attribution to individual interviewers exports as structured JSON. The customer's BambooHR admin rebuilds scorecard templates in BambooHR's custom fields or uses the interview notes section of the Applicant record. Scorecard aggregate scores can be stored as custom number fields on the Applicant record.

Whitecarrot.io offer records including compensation details, e-signature status, and approval flow states have partial support in BambooHR. BambooHR's offer letter feature supports template-based offers with e-signature through an integrated provider (typically DocuSign or HelloSign, which must be configured separately). We export offer data as structured records and map compensation fields to BambooHR custom fields on the new hire's employee record. Offer approval workflow states do not transfer; the customer's admin must configure BambooHR's approval workflows if automated offer sign-off is required.

Whitecarrot.io user accounts (Recruiter, Hiring Manager, Interviewer roles) map to BambooHR employee records with corresponding access levels. We map Whitecarrot.io role name strings to BambooHR permission sets: Recruiter maps to an employee with ATS access, Hiring Manager maps to an employee with hiring workflow access, and Interviewer maps to an employee with interview feedback access. Email addresses serve as the dedupe key for user matching. Any Whitecarrot.io user without a matching BambooHR employee record enters a reconciliation queue.

Whitecarrot.io career site page configurations and branding settings export as structured JSON or page configuration records, not as rendered HTML pages. BambooHR's career page builder stores content differently, so direct page transfer is not possible. We provide a full field-level export map of the Whitecarrot.io career site configuration (page structure, job listings, branding assets, custom CSS if stored) so the customer's admin can reconstruct the site in BambooHR. Active job listings migrate as Job Opening records in BambooHR regardless.

Whitecarrot.io job board posting configurations and posting history migrate as reference records listing which jobs were posted to which boards (LinkedIn, Indeed, niche boards). Active posting URLs and authenticated integrations tied to Whitecarrot.io's own integrations account do not transfer between platforms. We document every active job board posting in a structured export so the customer's admin knows exactly which boards and jobs require re-authentication in BambooHR's job distribution settings.

Whitecarrot.io report definitions and historical analytics data export as static data snapshots. Custom report query configurations from Teams Pro do not transfer as executable report definitions. We export report data as CSV or JSON snapshots at the time of migration. BambooHR's report builder is separate; the customer's admin rebuilds reports using BambooHR's own report templates and custom report builder. Pipeline analytics from Whitecarrot.io do not map to any BambooHR equivalent because BambooHR's analytics focus on employee metrics rather than recruiting funnel metrics.