Migrate from iRecruit to Zoho Recruit

iRecruit Job records map to Zoho Recruit Job Openings. Each iRecruit Job carries its own knock-out question set and custom screening questions defined at the job level; these map to Zoho Custom Fields attached to the Job Opening module. We create the custom fields in Zoho during the schema phase before any candidate import begins. Social and job-board auto-posting settings from iRecruit do not transfer; we document the posting configuration for manual re-entry in Zoho Recruit's job board connectors.

iRecruit Candidate records map to Zoho Recruit Candidates. The iRecruit Candidate profile (resume, application date, source, stage progression, multi-job application history) migrates as a primary Candidate record with a rich field mapping. Zoho Recruit requires Last Name as a mandatory field; we flag any iRecruit Candidate without a last name value and substitute 'Not Provided' per Zoho's import requirement before insert. Multi-job applications from a single Candidate become multiple Candidate subform entries or linked Job Openings per the customer's preferred structure.

iRecruit Enterprise Advanced Requisition Request records migrate to Zoho Recruit Job Requisitions module or Job Openings marked with the approval workflow flag. The requisition approval routing state (approval chain, current stage, approval date) migrates as custom fields on the Job Opening record. Zoho Recruit's Blueprint workflow handles the approval routing post-migration; the legacy approval history is preserved as a read-only field for audit.

iRecruit iConnect onboarding state migrates to Zoho Recruit Candidate Checklist items and custom onboarding status fields. Active e-signature sessions, in-progress I-9 forms, and benefits enrollment workflows cannot transfer as live authenticated sessions; we preserve the completion state, document list, and field data as checklist entries. The customer sends new onboarding invite emails from Zoho Recruit on go-live day to restart the process from the preserved checkpoint. This is a manual step on the customer's side post-migration.

iRecruit mass personalized email templates (body text, subject lines, stage-triggered send rules) are inventoried with their stage association and template body copied into a migration deliverable document. Active sending queues and scheduled send-time triggers do not migrate because they depend on iRecruit's internal email sending infrastructure. The customer's admin recreates templates in Zoho Recruit's Email Templates section, optionally using the inventory as a reference copy.

iRecruit EEO and affirmative action report data (candidate demographic fields and hiring outcome flags at the record level) migrates to Zoho Recruit Candidate custom fields. The report generation itself (the one-click EEO report output) does not migrate as a report artifact; we preserve the underlying data so the customer can build equivalent affirmative action reporting in Zoho Recruit using custom report types or Zoho Analytics.

iRecruit WOTC qualification records (qualification category, qualifying date, credit amount range) migrate to Zoho Recruit Candidate custom fields. We flag to the customer that the WOTC credit capture must be re-submitted to their destination payroll provider manually within the WOTC filing window (typically 28 days post-hire) because the credit capture depends on the payroll system's WOTC module, not the ATS. Failure to re-submit forfeits the credit.

iRecruit knock-out questions are defined per job and determine automatic candidate disqualification. These map to Zoho Recruit Custom Fields on the Job Opening module with a boolean or picklist type. The disqualification logic (what happens when a candidate fails a knock-out question) does not migrate as automation; we document each knock-out question with its disqualification condition so the customer's admin can rebuild it as a Zoho Workflow Rule with a field-update action post-migration.

iRecruit user accounts (recruiters, hiring managers, admins) map to Zoho Recruit Users with role assignments preserved as profile and role assignments in Zoho. User provisioning in Zoho is a prerequisite before any other record import because OwnerId references must be satisfied at insert time. We extract distinct owner emails from all iRecruit records and reconcile against the destination Zoho Recruit account's user list. Any owner without a matching Zoho Recruit User account goes to a reconciliation queue for manual provisioning before record migration resumes.

iRecruit's Sage HRMS and MyPayrollHR export file schema migrates as a documented export configuration for the customer's admin to re-implement in Zoho Recruit's CSV export builder. We preserve the field mapping from the legacy export so the downstream payroll or HRIS integration can be re-established with the same field names and order. Any custom export files built for other HRIS platforms are inventoried as schemas only; the actual export pipeline requires manual re-configuration in Zoho Recruit.

iRecruit allows a single Candidate to apply to multiple Jobs with potentially different knock-out question answer sets per application. When a Candidate has applied to multiple jobs, we create a primary Candidate record in Zoho Recruit and attach multiple Job Application subform entries (one per distinct job) with the application-specific answer data stored on the subform. This preserves the per-application answer context that would otherwise be flattened in a simple field mapping.

Many iRecruit customers rely on saved Exporter report definitions to define exactly which data scope they care about preserving. We extract the customer's existing saved report definitions and use them as the scope specification for the CSV export. Each saved report definition becomes a corresponding import file in the Zoho Recruit module import, preserving the same field selection and filter criteria the customer had in iRecruit. If no saved reports exist, we build the export scope in collaboration with the customer's iRecruit admin during discovery.