Migrate from Jobvite to Recruit CRM & ATS

Jobvite Jobs map directly to Recruit CRM Jobs. We preserve job title, description, requirements, department, location, status (published, archived), and opening count. Jobvite's custom fields on Jobs migrate to Recruit CRM custom fields on the Job object. Pipeline stage definitions from Jobvite map to Recruit CRM's pipeline stages with stage names and ordering preserved. Archived Jobs migrate as archived records with the original archive date.

Jobvite Candidates map to Recruit CRM Candidates. We preserve name, email, phone, work history, education, skills, source attribution, and SMS consent status. Jobvite's candidate custom fields migrate to Recruit CRM candidate custom fields. When Jobvite stores client contact information on a Candidate record (for agency CRM use cases), that data migrates to the Recruit CRM Contact sub-object within the Candidate record.

Jobvite Applications link a Candidate to a Job at a specific Pipeline Stage. Recruit CRM does not have a separate Application object; the candidate-job association and stage history are managed within the Candidate record or as Activity log entries. We merge Application records into the corresponding Candidate record, preserving the applied Job reference, pipeline stage at time of application, stage advancement dates, rejection reasons, and interviewer assignments. Multiple Applications per Candidate (re-applications across roles) each create a separate pipeline entry on the Candidate record.

Jobvite pipeline stages are configurable per Job. We extract stage definitions (stage name, order, probability percentage, rejection reason flags) and configure matching Recruit CRM pipeline stages per Job. Non-standard stages such as background check, drug screening, or offer stage are mapped explicitly to Recruit CRM stage values. If Recruit CRM does not have an equivalent stage, we create it as a custom stage and document the mapping.

Both Jobvite Candidates and Jobs support custom fields. We export custom field definitions from Jobvite (label, field type, picklist values) and pre-create matching custom fields in Recruit CRM before any data import. Custom field IDs in Recruit CRM are required as targets during import. Picklist fields from Jobvite are mapped to Recruit CRM picklist or multi-select picklist fields with values preserved verbatim.

Jobvite Users (Recruiters, Hiring Managers, Interviewers) map to Recruit CRM Users. We reconcile by email address. Any Jobvite User without a matching Recruit CRM User goes to a reconciliation queue for the customer's admin to provision before record import. Hiring Team assignments on Applications migrate as User assignments on the Candidate record or Job record in Recruit CRM. Role-based permissions from Jobvite map to Recruit CRM role assignments.

Jobvite Offers are tied to an Application and include compensation details, start date, and approval status. Recruit CRM represents offers as Deal records attached to the Candidate. We migrate offer details (compensation amount, currency, start date, offer status, approval history) into Recruit CRM Deal fields. Approval history logs migrate as Deal Activity notes rather than live approval workflow records, since Recruit CRM's approval model differs from Jobvite's.

Jobvite's Onboarding module is a separate paid license and may not be active in every account. If active, we export onboarding task lists, new hire paperwork status, I-9/E-Verify records, and assigned onboarding tasks. Onboarding data migrates to Recruit CRM's Onboarding module if the destination account has this module active. If Recruit CRM Onboarding is not provisioned, onboarding task data is exported as a structured CSV inventory for the customer's admin to rebuild manually.

Resumes, cover letters, portfolio files, and signed offer documents are stored as attachments on Jobvite Candidates and Applications. We export binary blobs alongside metadata (filename, upload date, attached record type and ID). During Recruit CRM import, we upload files to the Files object and link them back to the corresponding Candidate or Job record by ID resolution. Large attachments are chunked for upload to stay within Recruit CRM API payload limits.

Talemetry Lists and Campaigns sit in a separate data partition outside Jobvite's standard Candidate API. We use Talemetry-specific export endpoints to retrieve candidate Lists, Campaign memberships, and source tracking data. In Recruit CRM, Lists migrate to Hotlists and Campaign associations migrate as custom fields or Hotlist memberships on the Candidate record. This layer is migrated last because Talemetry cross-references require all Candidate records to already exist in Recruit CRM with stable IDs.