Migrate from Webrecruit to Zoho Recruit

Webrecruit Candidate records map to Zoho Recruit Candidate. We preserve contact details (name, email, phone, address), application history, stage progression timestamps, and the GDPR consent flag. Webrecruit stores consent as a boolean flag with a timestamp; we map this to Zoho's Candidate Email Opt-in field and add a custom field consent_timestamp__c holding the original Webrecruit consent datetime for UK GDPR audit trail. Candidates with withdrawn or expired consent are flagged in a separate suppression list and migrated only on explicit customer instruction.

Webrecruit Job records map to Zoho Recruit Job Opening. We transfer job title, description (mapped to Zoho's rich-text Description field), department, location, status (Open/Closed/On Hold), and posting dates. Zoho Recruit requires a Status field; Webrecruit's status values are mapped to Zoho equivalents (Active maps to Open, Archived maps to Closed). If Webrecruit jobs include custom requisition fields, these map to Zoho custom fields configured before migration.

Webrecruit Application records (linking a Candidate to a Job with a timestamp and current stage) map to Zoho Recruit Candidate Submissions. Each submission preserves the application date, current stage in the Webrecruit pipeline, rejection date if applicable, and withdrawal status. Zoho links Submissions to Candidates and Job Openings via internal IDs that we resolve during migration using the email-deduped Candidate lookup and the job-title-matched Job Opening lookup.

Webrecruit's pipeline stages (Application Received, Screening, First Interview, Second Interview, Offer, Hired, Rejected) map to Zoho Recruit Interview Stages. We map each named stage to the closest Zoho equivalent and create custom stage names in Zoho's pipeline configuration if no standard equivalent exists. Bespoke stages such as aptitude tests, competency assessments, or structured exercises that are not native to Webrecruit's pipeline cannot be carried as pipeline stages in Zoho either; we migrate assessment results as candidate attachments or notes and document them in the post-migration handoff.

Webrecruit Hiring Managers are assigned to jobs and can leave feedback on candidates. We map Hiring Manager assignments to Zoho Recruit Interviewer records linked to the corresponding Job Opening. Hiring Manager contact details (name, email, role) transfer as Interviewer records, and any feedback left in Webrecruit migrates as Zoho Candidate notes or evaluation records attached to the relevant Submission. If the Hiring Manager email does not match an existing Zoho Recruit User, we create an Interviewer record without User linkage and flag it for the customer's admin to assign a Zoho user post-migration.

Webrecruit CVs, cover letters, and application attachments migrate as Zoho Recruit Attachments linked to the corresponding Candidate record and Candidate Submission. We export document blobs from Webrecruit, preserve the original filename and MIME type, and re-attach them in Zoho under the Attachments section of the relevant record. Document export depends on the migration method: API export preserves binary attachments; CSV fallback may require the customer to provide a separate document bundle for bulk attachment re-upload.

Webrecruit approval workflows define how a job requisition moves from creation through internal approval to posting. These are process-level configurations that do not export. We deliver a written inventory of every active Webrecruit workflow including its trigger, approval steps, step owners, and conditional branching logic. The customer's Zoho Recruit admin uses this inventory to rebuild equivalent workflows using Zoho's Blueprint or custom function capabilities post-migration.

Webrecruit's connections to BreatheHR, CIPHR, and other third-party services are connection-level OAuth or API token configurations that live in the Webrecruit platform and do not export or migrate. We document which integrations are active in Webrecruit, their purpose, and the reconnection steps required in Zoho Recruit. Re-establishing each integration requires the customer's admin to re-authenticate and reconfigure the connection in Zoho's marketplace. This is covered in the post-migration checklist delivered alongside the migration report.

Webrecruit User accounts (name, email, role, and permissions) map to Zoho Recruit Users. We extract all Webrecruit Users and attempt to match by email against the destination Zoho Recruit account's existing user list. Unmatched users go to a reconciliation queue for the customer's Zoho admin to provision before record import resumes, because Owner and Interviewer assignments on records require a valid Zoho User ID.

Webrecruit account-specific custom fields are exported as field definitions (name, type, options) and values per record. We map these to Zoho Recruit custom fields, creating the equivalent Zoho field in the relevant module (Candidate, Job Opening, or Submission) before migration. Fields without a direct Zoho equivalent are flagged in the mapping document for manual re-entry or stored as text-area candidate notes. Validation rules, required-field enforcement, and picklist constraints in Zoho are configured before import to prevent silent field rejections during data load.

Webrecruit's fixed-fee recruitment advertising campaigns (separate from the ATS) involve job ad creative, targeting, and placement contracts that sit outside the candidate database. These do not migrate. We document active job advertising spend, board placements, and campaign dates so the customer's Zoho admin can reproduce posting schedules using Zoho Recruit's job board distribution module post-migration. The written handoff includes board-specific posting instructions for the 75+ boards Zoho Recruit supports natively.

Webrecruit branded careers page configurations, job listing page designs, and candidate-facing content do not migrate. We document the current careers site URL, page structure, and branding assets (logo, colors, copy) in the handoff document so the customer's web team or Zoho admin can rebuild the careers site using Zoho Recruit's Careers Page builder or a third-party careers site CMS. The FlitStack AI migration scope does not include careers site rebuild.