Migrate your iRecruit data

Jobs are the primary object in iRecruit. Each job supports configurable knock-out questions, internal/external visibility flags, and social/job-board auto-posting settings. We migrate job postings with their current status (open, closed, draft) and preserve the job-specific questions as custom fields on the Job object.

Candidates apply to one or more Jobs and carry a rich profile including resume, application date, source, and stage progression. We map candidate records including all application history across multiple jobs they may have applied to.

Enterprise tier supports Advanced Requisition Request and Approval via secure link and email approval. Requisition approval routing is stored as a workflow state on the requisition record. We preserve approval history and the current approval status, but the email-based approval mechanism itself does not migrate — it is reset to pending for the new owner's review.

iConnect is the paperless onboarding module handling I-9, tax forms, document signing, and benefits enrollment. Onboarding records are tied to the candidate after offer acceptance. We migrate onboarding record status, completed checklist items, and document references, but the active e-signature sessions and in-progress form links must be restarted post-migration.

iRecruit stores mass personalised email templates tied to specific candidate stages. Template body text and subject lines migrate as-is, but active sending queues and scheduled send-time triggers do not carry over and must be reconfigured in the destination ATS.

Enterprise tier provides EEO and affirmative action reporting with a click of a button. The generated report data is derived from candidate demographic fields and hiring outcomes. We migrate the underlying data fields needed to regenerate these reports in the destination system, but the report outputs themselves must be rebuilt.

Work Opportunity Tax Credit qualification flags and category assignments are stored per candidate. We preserve the WOTC category, qualification date, and credit amount range fields so the customer's accounting records remain complete. Actual credit capture depends on the destination payroll system supporting WOTC tracking.

iRecruit supports standard integration to Sage HRMS and MyPayrollHR via a custom export file format. Customers on other HRIS platforms have built bespoke exports. We migrate the data schema and field mappings from any existing custom export configuration, then generate a mapping specification for the destination HRIS.

Knock-out questions are defined per job and determine whether an applicant is automatically disqualified. These are stored as field-level configurations on the Job. We capture each knock-out question's field name, operator (equals, contains, etc.), and disqualifying value so the same screening logic can be replicated in the destination ATS pipeline stages.

User accounts in iRecruit represent recruiters, hiring managers, and admins. Role assignments (recruiter, hiring manager, admin) and team associations migrate as user-level properties, but session-based permissions tied to iRecruit's internal auth do not carry over and must be reassigned in the destination system.