Migrate from iRecruit to Crelate

iRecruit Jobs map directly to Crelate Jobs. Each job in iRecruit carries configurable knock-out questions, internal/external visibility flags, and social/job-board auto-posting settings. We map the job status, posting dates, department, and location fields 1:1. Job board distribution settings from iRecruit (Indeed, SimplyHired, Monster, Jobs.com) require reconfiguration in Crelate's job distribution panel post-migration because distribution credentials and posting templates are destination-platform-specific.

iRecruit Candidates map to Crelate Contacts. The candidate profile includes resume, application date, source, and stage progression across all jobs applied to. We migrate the full application history, preserving each job-to-stage mapping. Candidates who applied to multiple jobs in iRecruit will have multiple Application records in Crelate linked to the same Contact. Crelate's Standard Resume Parsing on Business plan processes uploaded resumes into structured fields automatically after migration.

iRecruit Requisitions (Enterprise-tier Advanced Requisition Request and Approval via secure link) map to Crelate Opportunities. The requisition approval routing state and approval chain from iRecruit are preserved as custom fields and notes in Crelate because Crelate's approval workflows are configured per Opportunity workflow and may differ from iRecruit's linear routing model. Customers with multi-location or multi-department requisitions should plan for Crelate Opportunity Record Type configuration during migration.

iConnect onboarding records include I-9 forms, tax documents, benefits enrollment workflows, and e-signature session state tied to a candidate record. Active e-signature sessions cannot transfer because they are authenticated against iRecruit's infrastructure. We preserve the onboarding checklist state (which steps are complete, which are pending), all completed document metadata, and form field data so Crelate Hire can restart the onboarding workflow from the correct stage. The customer must send new onboarding invite emails from Crelate on go-live day; we provide a CSV of candidate email addresses and their last completed onboarding stage to support that step.

iRecruit mass personalized email templates tied to specific candidate stages migrate as template body text and subject lines. Active sending queues and scheduled send-time triggers do not transfer. Crelate's Email Templates (included at Business tier) support merge fields, and we map iRecruit merge field names to Crelate equivalent tokens during migration. The customer's admin reviews and re-activates templates post-migration in Crelate's Email Templates section.

Work Opportunity Tax Credit qualification flags, WOTC category, qualifying date, and credit amount range migrate as custom fields on the Crelate Contact record. The actual credit capture depends on the customer's payroll provider actively processing WOTC submissions. We flag each qualifying hire in the migration report and include the re-enrollment deadline (typically 28 days from hire date). The customer must manually re-submit qualifying hires to their payroll provider's WOTC program post-migration; failure to do so within the filing window forfeits the credit.

iRecruit Enterprise provides EEO and affirmative action reporting derived from candidate demographic fields and hiring outcomes. We migrate the underlying demographic data (gender, ethnicity, veteran status, disability status) as custom fields on the Contact record so Crelate's EEO/OFCCP/VEVRAA Surveys and Reports feature can generate equivalent compliance reports post-migration. Survey response rates and report generation snapshots do not transfer; the customer generates new reports in Crelate after migration.

iRecruit knock-out questions are defined per job requisition, not as global fields. Each job carries its own set of disqualifying questions with answer options. We extract every distinct knock-out question across all jobs, map them to Crelate Custom Questionnaires under Settings > Custom Forms, and then attach the correct questionnaire to the corresponding job in Crelate post-migration. Candidates who applied to multiple jobs retain separate answer sets per job in our migration staging layer.

iRecruit User accounts (recruiter, hiring manager, admin roles) map to Crelate Users. Role assignments and team associations migrate as user-level properties. Session-based data (active logins, API tokens tied to user sessions) does not transfer. We match users by email address and hold unmatched users in a reconciliation queue for the customer's admin to provision in Crelate before record import proceeds.

Candidate source tracking (how the applicant found the job: job board, referral, direct, social) migrates to Crelate's Candidate Source Tracking fields. Source values that are free-text in iRecruit may need standardization to Crelate's picklist during migration; we flag unmapped values for admin review.

iRecruit supports standard integration to Sage HRMS and MyPayrollHR via a custom export file format. Customers on other HRIS platforms have built bespoke export schemas. We migrate the data schema and field definitions from any existing iRecruit export configuration so the customer can replicate the export logic in Crelate's Advanced Data Export and Data Plus features (included on Business tier). We do not build the destination export pipeline itself.

iRecruit notes and activity entries attached to candidate or job records migrate to Crelate Notes linked to the Contact record. Note timestamps and author attribution are preserved. Active note-sharing permissions from iRecruit require reconfiguration in Crelate's sharing settings post-migration.