Migrate from OnBlick HR Compliance to Zoho Recruit

OnBlick Employee records map to Zoho Recruit Candidates. We extract first name, last name, email, phone, address, department, job title, employment status, hire date, and termination date. The Candidate record becomes the primary container for the employee's post-migration identity in Zoho Recruit. If the same person has both an OnBlick employment record and a Zoho Recruit candidate history from a prior recruiting process, we flag duplicates for manual resolution before import.

Work Authorization history (visa type, start date, expiration date, issuing country, status) maps to custom fields on the Candidate module: wa_visa_type__c (picklist), wa_start_date__c (date), wa_expiration_date__c (date), wa_status__c (picklist: Active, Expired, Pending Extension). We preserve the full authorization timeline so the customer's admin can build expiration alerts using Zoho Recruit's workflow tools. We explicitly flag that resetting expiration dates to the current date will destroy the lead-time baseline OnBlick maintained at 6 months.

OnBlick H-1B case objects (petition status, LCA case number, filing date, RFE history, approval/denial records) have no native Zoho Recruit equivalent. We map these to a custom module H1B_Case__c (Enterprise tier) or structured multi-line notes on the Candidate record (Standard tier). Each approach requires pre-migration schema design. Custom modules in Zoho Recruit Standard are not available; the customer must be on Enterprise for standalone H-1B case tracking, or we use a Notes-based approximation on the Candidate.

LCA records (case number, prevailing wage, job title at filing, SOC code, wage level, employment location, filing date) map to custom fields on the Candidate or the H1B_Case__c custom module. We preserve the SOC code and wage level that was certified at filing time, not the current equivalent O*NET code, to maintain audit consistency for DOL reviews. The iCert Registry case number maps to lca_case_number__c (text).

OnBlick PAF PDFs are auto-assembled composite documents from certified LCAs, O*NET SOC codes, and FLC wage data. Zoho Recruit does not have a native PAF object. We export the assembled PAF PDF files and attach them as ContentDocument records linked to the Candidate via ContentDocumentLink. The underlying component data (LCA fields, wage levels, SOC codes) migrates to the H1B_Case__c custom module fields so the PAF can be regenerated in Zoho Recruit if needed.

Form I-9 records (Section 1 and Section 2 completion data, authorized representative assignments, reverification history) are legally sensitive compliance artifacts with federal retention obligations (3 years after hire or 1 year after termination). We export the complete I-9 record set as structured data and as PDF attachments linked to the Candidate. The retention obligation transfers explicitly in the migration inventory as a compliance handoff document. Zoho Recruit does not have a native I-9 schema; the I-9 data lives as attached documents and a custom field set (i9_section1_date__c, i9_section2_date__c, i9_reverification_date__c) on the Candidate.

Form I-983 data (training plan, site supervisor, STEM employer information, curriculum objectives, evaluation dates) maps to custom fields on the Candidate module or a separate I983__c custom module on Enterprise. Field mapping includes i983_training_plan__c (text area), i983_supervisor_name__c (text), i983_supervisor_email__c (email), i983_evaluation_1_date__c (date), i983_evaluation_2_date__c (date). The form's government-mandated structure is preserved in the field names.

SOC occupation codes and O*NET titles sourced at LCA filing time map to custom fields on Candidate: soc_code__c (text), soc_title__c (text). We preserve the historical SOC code and wage level from the LCA filing date, not the current O*NET equivalent, to maintain consistency for DOL audit reviews. Current O*NET data that OnBlick pulls for new LCAs does not migrate because Zoho Recruit has no SOC predictor engine.

OnBlick timesheet records (work hours, project associations, supervisor assignments, approval status) map to Zoho Recruit Task records with custom fields: ts_project_code__c (lookup or text), ts_hours_worked__c (number), ts_supervisor__c (text), ts_approval_status__c (picklist). We preserve line-item detail as separate Task records linked to the Candidate. Note that Zoho Recruit is an ATS and does not have a native payroll or timesheet approval module; this mapping provides record continuity but not workflow equivalence.

Leave management data (PTO balance, vacation accrual, holiday records) maps to custom fields on the Candidate module or a custom module Leave_Request__c. Leave policy rules and accrual methods vary across systems; we map leave types to nearest-equivalent Zoho Recruit picklist values and flag any non-transferable policy logic in the migration inventory for the customer's admin to rebuild in Zoho Recruit's Blueprint if required.

Documents associated with immigration cases, PAFs, I-9 records, and employment files stored in OnBlick's HR Drive export as files and attach to the corresponding Zoho Recruit Candidate record via ContentDocumentLink. We maintain the folder hierarchy from OnBlick as a naming convention (e.g., CASE-{CandidateID}/{DocumentType}/{Filename}) so the customer's admin can reconstruct the document structure after migration.

OnBlick eSignature audit trails (signer identity, timestamp, IP address, document reference) transfer as structured custom fields on the Candidate or attached document record: esig_signer__c (text), esig_timestamp__c (datetime), esig_document_id__c (text). The actual Signeasy signature images do not carry forward unless OnBlick exports them as image attachments; we flag this limitation in the migration inventory so the customer's admin can retrieve original signed documents directly from Signeasy if needed.

OnBlick user accounts and role-based access control assignments map to Zoho Recruit Users by email match. OnBlick role definitions (HR Admin, Hiring Manager, ESS, Immigration Specialist) are documented in the migration inventory as Zoho Recruit role equivalents for the customer's admin to configure post-migration. SSO configuration does not migrate; we provide the SSO requirements (SAML or OAuth endpoint details) for the customer's admin to configure in Zoho Recruit Setup > Security Controls.