Migrate from Jobvite to Crelate

Jobvite Candidates map directly to Crelate Contacts. We preserve name, email, phone, address, work history, education, skills, and SMS consent status. Crelate's Contact record uses a single unified person record; we merge any Candidate properties that would otherwise appear as separate sub-objects into flattened Contact custom fields. The SMS consent field from Jobvite maps to Crelate's communication consent property and we flag any record with Unknown status for manual admin resolution.

Jobvite Jobs map to Crelate Jobs with published and archived status preserved. We transfer job title, description, requirements, department assignment, location, and posting status. Active Posting status maps to the Crelate Job open/closed flag. Archived jobs migrate with their original posting dates preserved for compliance and audit purposes.

Jobvite Applications link a Candidate to a Job at a specific Pipeline Stage. We preserve stage history, rejection reasons, advancement dates, and interviewer assignments. Stage names are mapped explicitly to Crelate's pipeline stage values for the destination Job, with any non-standard Jobvite stages flagged as custom stages requiring Crelate configuration before import.

Pipeline Stages in Jobvite are configurable per Job. We extract all stage definitions from the Jobvite schema, including stage order, probability percentages, and any custom stage labels, and map them to Crelate's pipeline stage configuration. Stages with non-standard labels (e.g., background check, drug screen) require pre-creation in Crelate's pipeline settings before the migration phase begins.

Jobvite stores company information within the Candidate profile. We extract the embedded company data and create corresponding Organization records in Crelate, then link the Contact to the Organization via a lookup relationship. This preserves the agency-client relationship structure for staffing workflows.

Jobvite Users (Recruiters, Hiring Managers, Interviewers) with role-based permissions map to Crelate Users. We extract active users, resolve by email match, and preserve role assignments. Owner/User assignment on records migrates by resolving the Jobvite owner ID to the Crelate User ID at migration time.

Jobvite Offers are tied to an Application and include compensation details, start date, and approval status. We migrate Offer data to Crelate's Offer object, preserving compensation, start date, and approval history as a log rather than a live workflow record, since the destination system's offer approval automation may differ.

Onboarding is a separate module in Jobvite that may not be active on every account. If the Onboarding module license is active, we export onboarding task lists, new hire paperwork status, I-9/E-Verify records, and assigned onboarding owner, then map these to Crelate's placement task structure. If the module is not active, we confirm during discovery and exclude these records from the migration scope without treating the absence as a failure.

Jobvite custom field definitions (label, type, picklist values) are exported from the schema and mapped to Crelate custom fields created on the corresponding Core Records (Contacts, Jobs). Crelate supports Text, Number (Integer), Number (Decimal), Number (Money), and advanced types. We pre-create all custom field definitions in Crelate before any data import to ensure field types are correctly set and no data is truncated during insertion.

Talemetry Lists (acquired by Jobvite in 2019) exist in a separate data partition from the core ATS objects and are not accessible through standard Candidate API endpoints. We use Talemetry-specific export endpoints where available and map list memberships to Crelate's candidate tagging system, creating list names as Tags on the Contact record so marketing source data is not orphaned.

Talemetry Campaign associations on Candidates are extracted from the separate data partition and stored as custom properties on the Crelate Contact record (e.g., talemetry_source_campaign__c, talemetry_list_name__c). This preserves source attribution for agencies that track recruitment marketing effectiveness without requiring a separate Talemetry integration in Crelate.

Resumes, cover letters, portfolio files, and signed offer documents stored as attachments on Jobvite Candidates and Applications are exported as binary blobs with their metadata (filename, upload date, attached-by user). We import these as Crelate Attachments linked to the corresponding Contact or Job record, preserving the original filename and upload timestamp for compliance.

Jobvite hiring team notes attached to Candidates and Applications migrate to Crelate Notes on the Contact record. Note body, author, and timestamp are preserved. Notes from collaborative hiring scorecards are mapped to Crelate's evaluation or rating fields where applicable, or preserved as Notes if no equivalent Crelate field exists.

Jobvite's Requisition Field Mapping documentation notes that Job Title is the logical driver field for internal-to-external title mapping. If the Jobvite account uses custom Internal Title fields mapped to the job description, we extract this mapping and apply it as a Crelate job field configuration. Any custom field used as a mapping driver is confirmed during discovery and added to the Crelate Job schema before import.