Migrate from JobDiva to Zoho Recruit

JobDiva Candidates map directly to Zoho Recruit Candidates. The parsed resume fields (skills, work history, education, certifications) map to Zoho's Candidate structured fields, while the raw PDF/DOCX attachment migrates as a file link on the Candidate record. JobDiva's Harvester-sourced candidate data migrates as standard candidate records with the original source noted. Any legacy candidates with only parsed data and no attached file are flagged in the scoping report so the customer's team can decide whether to request document uploads post-migration.

JobDiva's ATS-CRM hybrid stores candidate-contact data on a single Candidate object. Zoho Recruit separates ATS Candidates from CRM Contacts. We extract JobDiva Candidates with client-company affiliations (identified by having Submittals tied to client Jobs rather than just sourcing-activity records) and create Zoho Recruit Contact records alongside the Candidate record. The customer's admin confirms during scoping whether all candidates should generate Contacts or only those with active client-facing relationships.

JobDiva CRM Contacts (distinct from ATS Candidates) store hiring manager information, client relationships, and company affiliations. These map 1:1 to Zoho Recruit Contacts. We preserve the contact's email, phone, title, company association, and any custom fields. The Contact-to-Client linking in Zoho Recruit is resolved at import time using the company lookup.

JobDiva Companies store client organization records with multiple associated contacts. These map to Zoho Recruit Client records. The company name, website, industry, and address fields migrate directly. We resolve all Contact lookups to the newly created Client record at import time before inserting Contact records, ensuring referential integrity across the CRM module.

JobDiva Job orders map to Zoho Recruit Job Openings. The job title, requirements, status, assigned recruiter, and department fields migrate directly. JobDiva's job pipeline stage (order, interview, offer, etc.) maps to Zoho Recruit's hiring pipeline with the stage mapping table built during scoping. Active job orders migrate with Open status; closed jobs migrate with their original status for historical reporting.

JobDiva Submittals track candidate submissions to specific jobs with per-organization custom status values. We extract the full set of custom status strings during scoping, build a status mapping table that translates each to the nearest Zoho Recruit pipeline stage equivalent, and apply it during migration. Submittal dates, submission-to-interview timelines, and interview outcomes migrate as related records. If the customer's JobDiva instance uses a non-standard submittal workflow with multiple stage branches, we document the structure for manual rebuild in Zoho Recruit's Blueprint.

JobDiva interview schedules (candidate, job, interviewer, date/time, outcome, feedback) map to Zoho Recruit Interview records linked to the candidate and job opening. We resolve parent record lookups (CandidateId, JobOpeningId) during import. Interview feedback forms migrate as notes or custom fields depending on whether the feedback uses structured or free-text format in JobDiva.

JobDiva Hotlists are curated ordered candidate lists for specific roles or talent pools. Zoho Recruit does not have a direct hotlist object, but candidate lists with custom names and ordered membership replicate the function. We map hotlist name to Zoho Candidate List name, and preserve the ordered sequence of candidate membership. The customer's admin decides whether to recreate hotlists as tagged candidate lists or as Zoho Recruit's folder-based candidate organization after migration.

JobDiva user-defined fields exist on Candidates, Jobs, Submittals, and other objects, defined per organization via API. We extract the full custom field schema during scoping, create equivalent custom fields in Zoho Recruit (up to 50 per module on Standard, 300 on Enterprise), and map data types accordingly. Multi-select picklists in JobDiva map to Zoho multi-select picklists; date fields map to Zoho date fields; text fields map to Zoho text or long-text depending on length. Any fields exceeding Zoho's per-module limit are flagged for the admin to prioritize.

JobDiva Events track scheduled activities tied to contacts, candidates, or jobs, syncing with calendars and generating email alerts. Calendar-type events migrate to Zoho Recruit Event records with StartDateTime, EndDateTime, and Location preserved. Task-type events migrate to Zoho Recruit Task records with Status, Priority, and ActivityDate preserved. Reminder settings and linked entity associations migrate as lookup references to the parent record in Zoho.

JobDiva timesheet records from the BillingPayTimesheet API track hours worked by placed candidates. Zoho Recruit does not have a native timesheet object in the ATS-CRM staffing module. We migrate timesheet records as custom fields on the relevant Job Opening or as a separate Zoho custom object if the customer configures one. Where accessible, we preserve candidate name, job reference, hours worked, billing period, and pay rate. If timesheet data requires a standalone timesheet module, we recommend evaluating Zoho Books integration as a separate configuration step.

JobDiva's CRM sales pipelines track business development deals with customizable stages. Zoho Recruit's Forecasting module (Professional+ staffing tier) handles placement revenue tracking. We map JobDiva pipeline stage names to Zoho Opportunity stage names and preserve deal associations. If the customer uses JobDiva's sales pipeline for candidate-independent business development deals, we recommend mapping these to Zoho Opportunities in the CRM module with a dedicated record type.

Resume files, candidate documents, and company files attach to their parent records in JobDiva. Binary attachments migrate to Zoho Recruit as linked files on the corresponding record (Candidate, Job Opening, or Contact). Resume parsing metadata is extracted separately from the binary attachment and mapped to structured candidate fields, not as a file.