Migrate from VivaHR to Bullhorn ATS & CRM

VivaHR Jobs map directly to Bullhorn JobOrder records. We extract Job title, type, location, description, and status, then create the Bullhorn JobOrder via the Bullhorn REST API. Bullhorn JobOrder requires a Client (Company) reference, so we create or look up the Client record before inserting the JobOrder. VivaHR's custom pipeline stages per Job require a reconciliation step: we map each named stage to a Bullhorn JobOrder status value or a custom JobOrder custom field if the pipeline has more stages than Bullhorn status values by default.

VivaHR Candidates map directly to Bullhorn Candidate records. We extract name, email, phone, skills, work history, education, and the full profile data from VivaHR. Bullhorn's Candidate entity supports custom fields; we pre-create Bullhorn custom fields to receive VivaHR Questionnaire responses and any non-standard properties that do not map to Bullhorn's standard fields. Bullhorn field type character limits (some capped at 100 characters) require truncation or overflow mapping for long-form text fields.

This is the critical join record for this migration. VivaHR attaches Candidates to Jobs with a pipeline stage assignment. Bullhorn maintains the same relationship through a separate JobSubmission entity linking Candidate and JobOrder. We extract every Candidate-Job pairing with its stage, stage-entry date, and stage-change history, then create Bullhorn JobSubmission records pointing to the resolved Candidate and JobOrder. This join table must be loaded after both Candidate and JobOrder exist in Bullhorn.

VivaHR's customizable pipeline stages (available on Growth and Premier) map to Bullhorn JobOrder status values or a Bullhorn custom picklist field if the pipeline exceeds the default status count. Stage probabilities migrate to Bullhorn's lead revenue or job order probability if those fields are enabled. We configure the Bullhorn status values during schema setup so that stage names and counts match the customer's VivaHR configuration.

VivaHR Scorecards are created per Job and contain evaluator ratings of Candidates. Bullhorn does not have a native Scorecard entity. We map Scorecard templates to Bullhorn Candidate custom fields (one field per rating criterion) and preserve individual Candidate ratings as field values. For scorecard templates with multiple criteria, we use a bulleted Note or a custom text area field containing the full scorecard output. The customer chooses the preferred approach during scoping.

VivaHR Questionnaires attached to Jobs collect structured candidate data such as availability, salary expectations, certifications, and custom screening questions. Bullhorn supports custom fields on the Candidate entity. We create Bullhorn custom fields of the appropriate type (text, picklist, date, checkbox) for each Questionnaire question, then populate them during the Candidate migration. Questionnaire templates with conditional logic do not transfer as logic; we document the template for the Bullhorn admin to reproduce.

VivaHR Culture Profiles contain employer brand text, media, and careers page content stored as rich-text and file assets. Bullhorn does not have a Culture Profile equivalent; the careers page content is rebuilt in Bullhorn's Career Portal or an external careers site. We extract Culture Profile content as structured text files and a file manifest (logos, images, employee photos) and deliver them to the customer's Bullhorn admin for re-import into Bullhorn's portal or an external careers page tool.

VivaHR assigns team members to Jobs with specific roles (hiring manager, recruiter, coordinator). Bullhorn tracks ownership at the record level: the JobOrder Owner, the Candidate record Owner, and the JobSubmission assigning user. We map VivaHR hiring team members to Bullhorn User records by email lookup, then assign OwnerId on Candidate and JobOrder, and set the assigning user on JobSubmission. Users without a Bullhorn account go to a reconciliation queue for the admin to provision before the final migration phase.

VivaHR stores candidate application activity such as stage-change timestamps, interview notes, and offer details. Bullhorn captures this as Note records attached to the Candidate and JobSubmission, and as Task records for scheduled follow-ups. We convert VivaHR activity log entries to Bullhorn Note records with a formatted body containing the stage name, date, and any associated evaluator notes, preserving the original timestamp in the Note body.

VivaHR Growth and Premier plans support custom objects tied to the Jobs or Candidates schema. Bullhorn supports Custom Objects (configured in Admin) that can hold additional data on separate record tabs. We pre-create Bullhorn Custom Objects with all required fields, lookup relationships to Candidate or JobOrder, and validation rules before migrating the custom object data via Bullhorn's REST API. Custom Object naming follows Bullhorn conventions with a custom object API name assigned during schema setup.

VivaHR stores skills on Candidate records as free-text or tag-based fields. Bullhorn supports a Skill entity linked to Candidate via a many-to-many relationship. We extract skills from VivaHR, deduplicate the skill list, and create Bullhorn Skill records (or map to existing Bullhorn Skills if the taxonomy already exists), then create CandidateSkill association records linking each Candidate to their skills in Bullhorn.

VivaHR advertises thousands of integrations via Zapier and other platforms, but the integration configurations (triggers, filters, authentication settings) are not migratable records. We document every active VivaHR integration by reviewing the customer's Zapier account, VivaHR settings, and any connected tools, then deliver a written integration inventory with recommended Bullhorn equivalents (Bullhorn's native integrations, Bullhorn App Marketplace add-ons, or Zapier alternatives). The customer's admin rebuilds each integration post-migration.