Migrate from OnBlick HR Compliance to Bullhorn ATS & CRM

OnBlick Employee records split across Bullhorn Candidate (for active job seekers and placed employees) and ClientContact (for employed contacts within client organizations). Personal identifiable information, department assignments, employment status, and contact details transfer as standard fields on both objects. We use employee email as the dedupe key and flag the record type distinction in a custom field employment_type__c.

Work authorization histories (visa type, start date, expiry date, I-94 numbers) transfer to a Bullhorn Custom Object attached to the Candidate record. We preserve the original OnBlick expiration date exactly as stored, not today's date, so that any 6-month alert logic the customer rebuilds in Bullhorn continues from the correct baseline. Visa type maps to a picklist custom field; CPT/OPT dates map to date fields with STEM OPT or CPT designation flags.

H-1B petition cases transfer as Bullhorn Custom Object records linked to the Candidate. Case status, petition start and end dates, LCA wage level, prevailing wage, and employer attorney contact information map to custom fields. Supporting document checklists transfer as structured data in a text area field formatted as line-delimited references to Bullhorn Document records attached to the case.

LCA records transfer with certified LCA number, prevailing wage, job title, SOC code (as certified at filing time, not the current equivalent), work location, and validity dates. Bullhorn's /meta endpoint exposes the custom object schema; we pre-create fields before migration and use batch inserts via Bullhorn REST API with rate-limit handling. SOC code historical context is preserved exactly as OnBlick stored it to maintain audit consistency for DOL reviews.

OnBlick PAF auto-assembled PDFs transfer as Bullhorn Document records attached to the LCA Custom Object. The underlying component data (LCA details, SOC code, wage data, benefits disclosure) transfers as structured fields in the customObject4 record. We export both the assembled PDF and the component data so the customer retains both the regulatory artifact and the structured source fields.

I-9 records transfer as Bullhorn Custom Object records with Section 1 and Section 2 completion data, authorized representative assignment, and reverification flags. The complete I-9 PDF transfers as a Document record attached to the custom object. Federal retention obligations (3 years after hire or 1 year after termination) are documented in a custom field i9_retention_date__c so the customer can enforce retention compliance in Bullhorn. We explicitly flag that Bullhorn does not provide E-Verify Web Services integration natively.

Form I-983 data (training plan, site supervisor details, curriculum objectives, program start and end dates) transfers as a Bullhorn Custom Object linked to the STEM OPT Candidate. The completed I-983 PDF migrates as a Document record. Training site address and supervisor contact information map to custom fields; the bona fide employer-employee relationship documentation from OnBlick transfers as structured text fields and attachments.

Timesheet records transfer as Bullhorn Custom Objects linked to the Candidate (for contractor timesheets) or Placement (for placed employee timesheets). Work hours, project associations, supervisor assignments, and approval status transfer to custom fields. Timesheet line-item detail migrates to a related list on the custom object. If the customer requires timesheet functionality post-migration, Bullhorn's custom object provides the schema foundation but the approval workflow requires rebuild as a Bullhorn Workflow or third-party add-on.

Leave records (PTO, holidays, vacation balances) transfer to a Bullhorn Custom Object linked to the Candidate or ClientContact. Leave policy rules and accrual methods vary across systems; we map leave types to the nearest-equivalent custom picklist values and flag any non-standard accrual rates in a notes field for the customer's HR admin to validate against their Bullhorn leave policy configuration.

SOC occupation codes sourced from O*NET transfer as custom fields on the LCA Custom Object. Historical SOC codes (as certified at LCA filing time) preserve the original O*NET version and FLC wage source data. We do not update SOC codes to current equivalents post-migration because the certified code at filing time is what DOL expects during an audit. Bullhorn's SOC data requires manual maintenance or integration with O*NET data sources; OnBlick's SOC predictor engine does not replicate in Bullhorn.

Immigration documents, PAFs, I-9 attachments, and petition PDFs transfer as Bullhorn ContentDocument records linked via ContentDocumentLink to their parent Candidate and Custom Object records. File names preserve OnBlick's original naming convention for traceability. Large attachment sets require Bullhorn's Bulk API or chunked REST uploads with content-type validation to preserve PDF integrity.

OnBlick eSignature metadata (signeasy integration) transfers as custom fields on the parent object (I-9, Immigration Case, or LCA). Signature audit trail (signer identity, timestamp, IP address) populates the custom fields; the signed document itself transfers as a Bullhorn Document record. Bullhorn does not natively replicate the signeasy eSignature API; if electronic signing continues, the customer must configure a new signeasy Bullhorn integration post-migration.