Migrate from VivaHR to BambooHR

VivaHR Jobs map to BambooHR Job Openings in the ATS module. We preserve job title, job description (rich text), location, employment type, and department from VivaHR's Job fields. Job Opening status (Open, Closed, Draft) migrates directly. BambooHR's Job Opening API name is jobOpeningId. Note that BambooHR's ATS is a module within the HRIS rather than a standalone product; we configure the ATS module during destination setup and verify the customer's BambooHR plan includes ATS access (Core includes ATS with 5 openings, Pro with 25, Elite with 50). VivaHR's active job posting count should be verified against BambooHR's tier cap before migration.

VivaHR Candidates attached to a Job map to BambooHR Applicants under the corresponding Job Opening. We preserve candidate name, email, phone, resume (as file attachment), stage history, application date, source, and referral information. VivaHR's questionnaire responses migrate as custom fields on the BambooHR Applicant record. The applicant status in BambooHR (Applied, Phone Screen, Interview, Offer, Hired, Rejected) maps from VivaHR's pipeline stage names, with the customer confirming stage-to-status mapping during scoping. Candidate records that have no associated Job in VivaHR require a decision: either link to a placeholder Job Opening or treat as inactive records pending Job creation.

VivaHR's customizable hiring pipeline stages map to BambooHR's Hiring Pipeline stages. BambooHR supports pipeline configuration within the ATS module, but the stage values and probabilities must be explicitly mapped because VivaHR stage names (e.g., Applied, Recruiter Screen, Hiring Manager Interview, Offer) rarely match BambooHR's default status values. We define the pipeline configuration in BambooHR during destination setup and map each VivaHR stage to a BambooHR stage with matching order and optional probability. If the customer uses multiple VivaHR pipelines (Growth and Premier plans), each becomes a separate BambooHR Hiring Pipeline with its own stage configuration.

VivaHR Scorecards are per-Job evaluation templates with rating criteria attached to Candidates. BambooHR has no native scorecard object on Applicants. We export scorecard templates and Candidate ratings as custom fields on the BambooHR Applicant record. Each VivaHR scorecard criterion (e.g., Technical Skills, Communication, Culture Fit) becomes a custom field with the candidate's numeric or text rating preserved. We create the custom fields in BambooHR during schema setup and document the original scorecard template structure for the customer's admin to reference during hiring.

VivaHR Job-specific questionnaires collect structured candidate data via custom questions. Questionnaire questions and answers migrate to BambooHR Applicant custom fields. Multiple-choice and text answer types map to BambooHR dropdown and text field types respectively. The mapping is field-by-field; we document the original questionnaire structure during extraction so the customer can rebuild equivalent questions in BambooHR's application form builder if the native builder does not support the same question types.

VivaHR Culture Profiles contain employer brand content (text, images, videos) displayed on the branded careers page. BambooHR does not have an equivalent Culture Profile object. We export Culture Profile media files and text content as a downloadable asset package with file naming that preserves the original structure. The customer manually re-imports these assets to BambooHR's careers page builder or a separate careers site. We flag this as a manual rebuild item in the migration handoff document.

VivaHR Hiring Team members assigned to a Job (with roles such as Recruiter, Hiring Manager, Interviewer) map to BambooHR User records in the destination HRIS. We match by email address and preserve the VivaHR role assignment as a custom field or note on the BambooHR User. Owner assignment on Job Openings migrates by resolving the email match to the BambooHR User who will be the job owner. Any VivaHR Hiring Team member without a matching BambooHR User account goes to the reconciliation queue for admin provisioning before record import.

VivaHR is an ATS and does not store post-hire employee records (employment details, payroll, benefits, time-off, performance). If the customer has VivaHR candidate records with an offer stage, those candidates can be migrated as Applicants who become new Employees in BambooHR. The employee record creation (first name, last name, start date, compensation, department, manager) must be completed manually in BambooHR or sourced from a separate HR system because VivaHR does not maintain this data. We flag this gap in the migration scope and advise the customer to verify their post-hire data source before cutover.

VivaHR advertises integrations via Zapier and other platforms, but these are configuration records rather than migratable data. We document each active integration by name and connection type during discovery and deliver an integration inventory as part of the handoff document. The customer rebuilds integrations in BambooHR using BambooHR's native integrations (150+ partner apps) or Zapier. Workflows, automations, and candidate outreach sequences are configuration items that do not migrate; we deliver a written inventory with recommended BambooHR equivalents for the customer's admin to rebuild.

VivaHR stores candidate activity such as stage change timestamps, email communications, and internal notes. We export activity timestamps as date fields on the BambooHR Applicant record. Internal notes migrate as Note records linked to the Applicant. Email communication history migrates as Notes with the email content preserved. BambooHR's applicant activity feed stores stage changes and timestamped events; we map VivaHR stage history to BambooHR's native status history. Note that BambooHR's ATS activity model is less granular than VivaHR's engagement model; we document the mapping and flag any activity types that do not have a native BambooHR equivalent.