Migrate from JobDiva to Crelate

JobDiva Candidates map to Crelate People records. We extract the full candidate profile including parsed resume fields (skills, experience, education), contact information, and source attribution. JobDiva's Harvester-sourced candidates carry a source tag that migrates to Crelate's candidate source field. The binary resume attachment migrates as a file linked to the Person record. Candidates with only parsed data and no uploaded document are flagged during scoping so the customer can decide whether to source missing documents post-migration.

JobDiva CRM Contacts map directly to Crelate Contacts. We preserve contact attributes, company affiliations, hiring manager relationships, and the contact's associated notes and activities. The mapping resolves the contact's linked Company record before Contact insert so that the relationship graph is intact at destination.

JobDiva Companies map to Crelate Organizations. Each Organization record in Crelate can hold multiple Contacts, mirroring JobDiva's company-contact structure. We import all active and inactive companies referenced by at least one Contact, Job, or Submittal record to maintain referential integrity.

JobDiva Job orders map to Crelate Jobs. The job status, requirements, assigned recruiters, and pipeline stage migrate. JobDiva's job-to-submittal relationship is preserved so that candidate submissions appear in the correct job context in Crelate. Open, filled, and closed job statuses map to Crelate's job status enum with a custom field carrying the original JobDiva status for audit.

JobDiva Submittals track candidate submissions to specific jobs with status transitions, submission dates, and interview outcomes. The primary mapping challenge is that JobDiva submittal status values are organization-specific custom strings rather than a fixed enum. We extract the full set of status values during scoping, build a custom status mapping table, and translate each status to Crelate's Activity Form or Pipeline stage before writing. Submittal-to-job and submittal-to-candidate foreign keys resolve at migration time using the staged record insertion order.

JobDiva Interview schedules associated with submittals map to Crelate Activities. Each interview carries candidate, job, interviewer, date/time, and outcome data from JobDiva's Get Submittals Detail API. We create Crelate Activities with the correct type (Event for scheduled meetings, Task for interview-related follow-ups) and link them to the migrated Person and Job records.

JobDiva Hotlists are curated candidate lists for specific roles or talent pools. Crelate does not have a native hotlist object with ordered sequence, so we create Crelate Tags for each hotlist name and apply them to the corresponding Person records. The ordered sequence of candidates is preserved in a custom ordering field on the Person record that the customer can reference during rebuild of hotlists in Crelate's tagging interface.

JobDiva Events (scheduled activities tied to contacts, candidates, or jobs) map to Crelate Activities. We preserve timestamps, linked entity references, and reminder settings. Events sync with calendars in JobDiva; we migrate the scheduling data and flag for the customer to reconnect calendar integrations post-migration.

JobDiva user-defined fields on candidates, jobs, submittals, and other objects are extracted during scoping with their schema definitions (field type, required flag, picklist values if applicable). We pre-create corresponding custom fields in Crelate's Core Records (Contacts, Organizations, People, Opportunities) using Crelate's custom field API, matching field types where possible and flagging any JobDiva field types that require workaround mapping. The customer reviews the custom field schema before migration begins.

JobDiva's configurable sales pipelines for tracking business development map to Crelate Opportunities. Pipeline stage names migrate as Opportunity stage values, with remapping to Crelate's default stages or custom stages created during Crelate setup. Deal associations and pipeline statistics migrate as Opportunity fields. Pipeline configuration in Crelate is scoped as a pre-migration setup task for the customer's admin.

Resume files, candidate documents, and company files attached to parent records in JobDiva migrate as Crelate Attachments linked to the corresponding Person, Contact, Organization, or Job. Resume parsing metadata (skills, experience, education fields extracted by JobDiva's parser) migrates as structured fields on the Person record, separate from the binary file attachment.

JobDiva Owners referenced on Candidates, Contacts, Companies, Jobs, Submittals, and Events resolve by email match against Crelate Users. Any JobDiva Owner without a matching Crelate User enters a reconciliation queue for the customer to provision before record import resumes. Inactive JobDiva users map to inactive Crelate Users to preserve historical attribution.