Migrate from JobDiva to Recruit CRM & ATS

JobDiva Candidates map directly to Recruit CRM Candidates. We extract parsed resume fields (skills, experience, education) from JobDiva's structured metadata alongside the binary resume attachment, and write both to Recruit CRM's AI-parsed candidate profile. The original file attaches to the Candidate record. Any parsed field data that cannot map directly to Recruit CRM's standard schema is preserved in a custom field note or migrated as a candidate tag for admin review.

JobDiva CRM Contacts (distinct from ATS Candidates) map to Recruit CRM Contacts. Contact records store client relationships, hiring manager information, and company affiliations. We preserve contact attributes and their associated company relationship by resolving the company lookup before writing contact records. Email, phone, title, and address fields map directly.

JobDiva Companies map to Recruit CRM Companies. Each Company record can have multiple associated Contacts. We preserve the company-contact relationship graph at the destination by creating Company records first, then resolving the company reference when writing Contact records. Company website, industry, and address fields migrate directly.

JobDiva Job orders map to Recruit CRM Jobs. We preserve job status, requirements, assigned recruiters, and pipeline stage. Jobs are created before any associated submittal records so that the job lookup is satisfied at the moment of submittal insert. JobDiva's assigned recruiter resolves to a Recruit CRM user by email match.

JobDiva Submittals map to Recruit CRM's Candidate-Job relationship records that appear in the pipeline. The mapping requires a custom status translation table because JobDiva submittal status values are defined per organization rather than as a fixed enum. We extract all active status values during scoping and build the mapping before migration. Submission date, interview outcomes, and submittal notes preserve with the record.

JobDiva interview schedules are associated with submittals and contain candidate, job, interviewer, date/time, and outcome data. The Get Submittals Detail API returns interview data separately. We link interview records to the corresponding Candidate-Job pipeline entry in Recruit CRM and preserve interviewer assignment, scheduled time, and outcome status.

JobDiva Hotlists are curated candidate lists with custom names and ordered sequences. Recruit CRM does not have a native hotlist object. We re-create hotlist membership using Recruit CRM tags (one tag per hotlist name) applied to Candidate records, preserving the ordered sequence as a tag priority or custom sort field. The customer chooses between tags or a dedicated pipeline stage during scoping.

JobDiva supports custom user fields on Candidates, Jobs, Submittals, and other objects created per organization via the API. We extract the user-defined field schema during scoping, compare against Recruit CRM's custom field capabilities, and pre-create matching custom fields before data import. Fields that cannot map directly (due to type incompatibility) are flagged in the scoping report for admin decision.

JobDiva Events track scheduled activities tied to Contacts, Candidates, or Jobs. Events sync with calendars and generate email alerts. We map events preserving their timestamps, linked entities, and reminder settings. Activity type (call, meeting, task) maps to the corresponding Recruit CRM activity type.

JobDiva CRM includes configurable sales pipelines for tracking business development with customizable stages per organization. Recruit CRM uses a visual Kanban pipeline with configurable stages. We map pipeline stage names and deal associations, remapping custom stage values to Recruit CRM equivalents during migration. If JobDiva pipeline stages do not map cleanly, we document the gap for the customer's admin to configure post-migration.

Resume files, candidate documents, and company files attach to their parent records. We preserve binary attachments and link them to migrated records. Resume parsing metadata is extracted separately from the binary file and written to structured candidate fields. Any document without a valid parent record (orphan attachments) is held in a reconciliation queue for admin review.