Migrate from Jobvite to BambooHR

Jobvite Job records map to BambooHR Job Opening. The Job title, description, department, and location fields map directly. We extract the job status (Published, Draft, Archived) and map it to BambooHR's open, closed, or draft status. Archived jobs can be migrated as closed Job Openings or exported as a JSON archive depending on the customer's retention policy. Department in Jobvite maps to the BambooHR Job Opening's department field, which must be pre-populated as a BambooHR list value during schema setup.

Jobvite Candidates map to BambooHR Candidates. We preserve name, email, phone, address, work history, education, and skills as free-text fields or custom fields in BambooHR. The SMS consent status field from Jobvite does not have a direct BambooHR analog; we extract it as a custom Candidate field for compliance documentation. Multi-value fields (skills, education entries) are stored as comma-separated text in BambooHR since BambooHR Candidates do not support repeating field structures for these data types.

Jobvite Applications map to BambooHR Applications linked to a Job Opening. The Application's current stage, rejection reason, advancement timestamps, and interviewer assignments migrate as Application metadata. The full stage history is preserved as a custom text field in JSON format so the hiring team's decision timeline is auditable in BambooHR. BambooHR does not support multiple concurrent applications for the same candidate in the same way Jobvite does; if a candidate has applied to multiple jobs, we create separate Application records in BambooHR for each.

Jobvite Pipeline Stages are configurable per Job and do not have a direct equivalent in BambooHR's fixed application stage model. We extract the customer's stage definitions (stage name, order, probability) during scoping and map them to the three to five standard BambooHR application stages (Applied, Phone Screen, Interview, Offer, Hired) with custom stage names noted in a mapping document. Any non-standard stages (background check, drug screen, executive review) are flagged as stages requiring manual interpretation or a BambooHR workflow addition post-migration.

Jobvite Hiring Team members who are not already employees in BambooHR are created as inactive Employee records during migration. The inactive status allows the customer's admin to activate them if they become employees. Interviewers who are external to the company are stored as name and email only since BambooHR does not have a standalone interviewer role object. Active Users in Jobvite are mapped to BambooHR Employee records with the same email so that BambooHR's built-in access provisioning can assign them the appropriate Hiring role once activated.

Jobvite Offer records attached to an Application map to BambooHR Offers. Compensation details, start date, offer status, and approval history migrate as offer metadata. The approval chain from Jobvite is preserved as a custom notes field since BambooHR Offers do not have a native approval workflow model. If the customer has extended offers as documents attached to the Application, those documents migrate as Employee Files on the resulting BambooHR Employee record after the offer is accepted and the employee is hired.

Jobvite Onboarding module records (task lists, new hire paperwork status, I-9/E-Verify records) are exported as a structured data document rather than migrated as live records. BambooHR's onboarding is structured differently with its own task list builder. We deliver a written inventory of every active onboarding task, the responsible party, and the completion status at migration time, so the customer's BambooHR admin can rebuild the task list in BambooHR's onboarding builder. Active I-9/E-Verify status is preserved as a note on the Employee record for compliance purposes.

Jobvite Users (Recruiters, Hiring Managers, Admins) map to BambooHR Employees. Active users with a BambooHR license are created as active Employees; inactive Jobvite users are created as inactive Employees. We match by email address and flag any Jobvite Users without an email for manual resolution. Role and permission mappings from Jobvite are preserved as a separate document for the customer's admin to reconfigure in BambooHR's employee permission settings.

Resumes, cover letters, portfolio files, and signed offer documents attached to Jobvite Candidates and Applications migrate as Employee Files in BambooHR. We export the binary blob alongside its metadata (filename, upload date, attached-by user) and attach each file to the corresponding Employee record in BambooHR. Files without an associated Employee (e.g., offer documents for candidates who were not hired) are migrated as Candidate Files on the BambooHR Candidate record.

Talemetry candidate Lists and Source tracking exist in a separate data partition in Jobvite and are not accessible through the standard Candidate API. We use Talemetry-specific export endpoints where available and map the list membership to a custom Candidate field in BambooHR called Source List. Talemetry Campaign associations are mapped to a custom Source Campaign text field. The customer should decide during scoping whether to preserve Talemetry list membership data as structured metadata in BambooHR or as a separate marketing source note for rebuild in a dedicated marketing platform.