Migrate from OnBlick HR Compliance to Recruit CRM & ATS

OnBlick employee profiles (name, contact, department, employment status, job title, start date) map directly to Recruit CRM candidate records. We extract effective-dated status transitions and preserve them as Recruit CRM custom status fields or tags. The candidate record becomes the primary person record in Recruit CRM; any active employment relationship from OnBlick maps to a separate employment history custom field set rather than replacing the recruitment-oriented candidate model.

OnBlick work authorization objects store visa type, start date, expiration date, and authorization status. We map these to Recruit CRM custom fields on the candidate record (e.g., visa_type__c, authorization_expiry__c, work_auth_status__c). The 6-month expiration alert logic that OnBlick generates proactively must be rebuilt as a Recruit CRM task workflow or manually monitored by the HR team; Recruit CRM does not have native work authorization alerting.

OnBlick immigration case objects (H-1B petitions, case status, supporting document checklists, reviewer assignments) have no native Recruit CRM equivalent. We split the structured case data (case number, petition type, filing date, status, RFE history) into custom fields on the candidate record, and attach case documents as Recruit CRM file attachments linked to the candidate. Full case history including status transitions migrates as a structured note or as a series of custom status-update fields.

OnBlick LCA records contain wage levels, job titles, prevailing wages, employment locations, and iCert registry references. We extract the certified SOC code, wage level, and prevailing wage as custom fields on the candidate record, and attach the LCA PDF as a document. SOC code and wage data from the certified LCA date is preserved, not the current O*NET equivalent, to maintain audit consistency for DOL reviews.

OnBlick PAF objects are auto-assembled composites of certified LCAs, O*NET SOC codes, and FLC wage data. Recruit CRM has no native PAF object. We export the assembled PAF PDF and the underlying component data as a document attachment on the candidate record, along with a structured note containing the key PAF fields (LCA number, prevailing wage, job title, worksite address). The customer must maintain PAF retention separately or through their immigration counsel.

I-9 records cannot migrate as structured data into Recruit CRM because the platform has no I-9 object or compliance form structure. We export the complete I-9 record set (Section 1, Section 2, reverification history, authorized representative assignments) as document attachments, and document the I-9 retention obligation in the migration handoff report. Federal law requires I-9 retention for 3 years after hire or 1 year after termination, whichever is later. The employer remains responsible for this obligation; we ensure the data is exportable and flagged, not lost.

Form I-983 contains training plan details, site supervisor information, and curriculum objectives required for STEM OPT compliance. We map structured fields (training plan start/end dates, site supervisor name and contact, employer's attestations) to candidate custom fields, and attach the I-983 PDF as a document. The I-983 is a government-mandated form that requires the employer's attestations; we preserve the full form as a completed document rather than attempting to recreate it as a data record.

OnBlick timesheet records capture work hours, project associations, supervisor approvals, and approval status. Recruit CRM does not have a native timesheet object. We migrate timesheet data as Recruit CRM candidate activities (with work hours as a custom field) or as structured notes with project and approval metadata. Recruit CRM's activity tracking is designed for recruitment touchpoints, not payroll timesheets, so the mapping is functional but loses the project-costing depth that OnBlick timesheets support.

OnBlick leave management stores PTO, holidays, and vacation balances by policy. Recruit CRM lacks a leave management module. We map leave balances to candidate custom fields (pto_balance__c, sick_balance__c) and leave history to activity records. Leave policy rules and accrual methods vary by employer; we document the source policy and flag that Recruit CRM does not enforce leave entitlement or trigger accrual calculations.

OnBlick SOC classification records store occupation codes, titles, and wage level mappings sourced from O*NET. These feed into LCA prevailing wage determinations. We preserve SOC code and title as custom fields on the candidate record. Because SOC codes change over time, we preserve the code as certified at the time of the LCA filing, not the current O*NET equivalent, to maintain audit consistency.

OnBlick HR Drive stores immigration case documents, PAFs, I-9 attachments, and eSignature audit trails. We export the full file structure and attach each document to its parent record in Recruit CRM (candidate, job, or client). File naming conventions from OnBlick are preserved so the customer can locate documents post-migration. Electronic signature audit trails (signer identity, timestamp, IP address from Signeasy) are included as a metadata document attached to the signed form.

OnBlick role-based access control maps to Recruit CRM user accounts and team assignments. We extract OnBlick user records, map role names to Recruit CRM team or permission-set equivalents, and flag any role with immigration compliance access that has no direct Recruit CRM equivalent. SSO configuration from OnBlick does not transfer; Recruit CRM supports SSO but requires separate setup by the customer's admin.