Migrate from VivaHR to Recruit CRM & ATS

VivaHR Jobs map to Recruit CRM Job records. The VivaHR job title, type (full-time, part-time, contract), skill level, and location fields map to their Recruit CRM equivalents. Active job posting status and the job description (rich text) migrate directly. Pipeline assignment in VivaHR (which pipeline the job uses) maps to the Recruit CRM Pipeline Stage assignment. VivaHR's job-level Scorecard templates link to the Job record and carry over as associated custom fields in Recruit CRM. The active job posting limit on VivaHR Standard (5 jobs) does not affect migration; the destination Recruit CRM tier determines the posting ceiling.

VivaHR Candidates map to Recruit CRM Candidates. Core profile fields (name, email, phone, LinkedIn URL, resume attachment) migrate directly. VivaHR stores candidates attached to Jobs within the pipeline; we preserve the candidate-to-job association using Recruit CRM's candidate-job linked record structure. The candidate's current pipeline stage in VivaHR maps to the corresponding stage in Recruit CRM's equivalent pipeline. Email opt-in status migrates to Recruit CRM's contact preference fields.

VivaHR customizable pipelines (available on Growth and Premier plans) map to Recruit CRM pipeline stages. Stage names are preserved as the customer defined them in VivaHR. If VivaHR and Recruit CRM stage counts differ, we map by sequence order and flag any orphaned stages for the customer's admin to reconcile. Stage probability percentages from VivaHR carry over as informational custom fields since Recruit CRM manages stage probabilities at the pipeline configuration level.

VivaHR Scorecards are job-specific evaluation templates with rating criteria and candidate ratings. We map each Scorecard criterion to a custom field on the Recruit CRM Candidate object. The rating value for each criterion migrates as the field value on the specific candidate-job combination. Scorecard template structure (criteria names, weightings) is preserved in a separate mapping document for the customer's admin to configure as custom fields in Recruit CRM if the template structure is needed beyond the individual ratings.

VivaHR Questionnaires attached to Jobs collect structured candidate responses. These map to Recruit CRM associated custom fields using the POST /v1/candidates/associated-field/{candidate}/{job} endpoint. Each questionnaire question becomes a field_id in Recruit CRM, and the candidate's response becomes the value. We extract the field IDs during data discovery, create matching custom fields in Recruit CRM, then populate them during migration. Multi-select questionnaire answers map to comma-separated values or the destination's multi-select format.

VivaHR Culture Profiles represent employer brand content (text descriptions, media assets, company values) displayed on the branded careers page. These are not relational database records but content assets. We export Culture Profile content as structured rich-text documents and re-import as Notes attached to the customer's Recruit CRM account or as content within Recruit CRM's career page builder. Media assets (images, videos) migrate as file attachments. The customer configures the destination Recruit CRM career page post-migration using the migrated content as source material.

VivaHR Hiring Team assigns users to a Job posting with specific roles (hiring manager, recruiter, interviewer). Team membership maps to the Recruit CRM Assignee field on the Candidate record and the Owner field on the Job record. We resolve VivaHR user email addresses against Recruit CRM user accounts during migration. If a VivaHR team member does not have a corresponding Recruit CRM user, they are added to a reconciliation list for the customer's admin to provision before final migration.

VivaHR stores company information associated with Candidates (current employer, previous employer). These map to Recruit CRM Company records. The company name, industry, website, and size fields migrate directly. If a Candidate has multiple associated companies in VivaHR, we create multiple Company records in Recruit CRM and link them via candidate-company association records.

VivaHR tracks a Candidate's movement through pipeline stages with timestamps. We preserve this as activity log entries in Recruit CRM, with the stage change recorded as a timeline event tied to the Candidate record. The original stage entry date becomes the activity timestamp. This is informational migration only; Recruit CRM rebuilds its own stage history from actual pipeline movements going forward.

VivaHR candidate automations (email triggers, follow-up sequences, status update rules) are configuration data rather than records. These do not migrate to Recruit CRM because the automation engine and rule syntax differ. We deliver a written inventory of every active VivaHR candidate automation, documenting its trigger conditions, actions, and target candidates, so the customer's admin can rebuild equivalent automations in Recruit CRM's automation module post-migration.