HRMS migration
Field-level mapping, validation, and rollback between OnBlick HR Compliance and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
OnBlick HR Compliance
Source
Crelate
Destination
Compatibility
11 of 14
objects map 1:1 between OnBlick HR Compliance and Crelate.
Complexity
BStandard
Timeline
4-6 weeks
Overview
OnBlick HR Compliance and Crelate serve fundamentally different functions: OnBlick is a specialized immigration and I-9 compliance platform for US employers with H-1B and STEM OPT workforces, while Crelate is an applicant tracking and recruitment CRM. Migrating from one to the other requires separating the HR core data (employee profiles, work authorization timelines, contact data) that transfers into Crelate's candidate and organization objects from the immigration layer (H-1B cases, LCAs, Public Access Files, Form I-9 records, Form I-983 STEM OPT records) that has no native home in an ATS. We extract the transferable data through structured OnBlick exports negotiated with their support team (OnBlick has no public migration API), map employee records to Crelate candidates, preserve work authorization expiration dates so that alerting can continue in the destination, and flag all immigration-specific records that require a separate compliance tool. We do not migrate workflows, automations, LCA assembly rules, or SOC predictor logic as these are platform-native features with no Crelate equivalent.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a OnBlick HR Compliance object lands in Crelate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
OnBlick HR Compliance
Employee
Crelate
Candidate
1:1OnBlick Employee records map to Crelate Candidate records. We extract employee first name, last name, email, phone, address, department, job title, hire date, employment status, and manager assignment. OnBlick's employee photo and HR Drive document references migrate as attachments to the candidate record. Any employee status transition history (active to inactive, role changes) migrates as a Note or as entries in a custom status history field in Crelate.
OnBlick HR Compliance
Organization
Crelate
Organization
1:1OnBlick organizations (employer entities) map to Crelate Organizations. If the employer has multiple legal entities or subsidiaries tracked in OnBlick, each becomes a separate Crelate Organization. We preserve the organization address, EIN (if stored in a custom field), and industry classification. Organizations are imported before Candidates so that the organization lookup reference is satisfied at candidate insert time.
OnBlick HR Compliance
Work Authorization Record
Crelate
Candidate (custom fields)
lossyWork authorization timelines (visa type, start date, expiration date, authorization status) have no native Crelate field. We create a set of custom fields on the Candidate object: visa_type__c (picklist), work_authorization_start__c (date), work_authorization_expiry__c (date), and authorization_status__c (picklist: authorized, pending, expired). We preserve the full authorization history as a formatted Note attached to the candidate so that reverification history is not lost. The 6-month expiration alert lead time from OnBlick must be re-established manually in Crelate or through a separate alerting tool.
OnBlick HR Compliance
Immigration Case
Crelate
Candidate (linked record)
1:1OnBlick H-1B petition cases have no native equivalent in Crelate's ATS schema. We create a Candidate-level linked record or note structure that captures case number, petition type, filing date, current status, and assigned attorney or reviewer. Case document attachments (Form I-797 receipts, LCA copies, RFE responses) migrate as candidate attachments. The customer should establish a dedicated immigration case management tool (OnBlick, Fragomen, or another immigration attorney platform) to replace OnBlick for active case tracking post-migration.
OnBlick HR Compliance
Labor Condition Application (LCA)
Crelate
Candidate (custom fields) + Attachment
lossyLCA records from OnBlick's iCert Registry integration (wage level, job title, prevailing wage, employment location, LCA determination date) migrate as a set of custom fields on the Candidate record plus the LCA PDF as an attachment. We preserve the SOC code and wage level that was certified at filing time, not the current equivalent code, to maintain audit consistency for DOL reviews. SOC codes and prevailing wages that change over time are historical at the LCA level and must not be overwritten with current values.
OnBlick HR Compliance
Public Access File (PAF)
Crelate
Candidate (attachment)
1:1OnBlick PAFs are auto-assembled composite documents sourced from certified LCAs, SOC codes, and FLC wage data. We export the assembled PAF PDFs and the underlying component data as structured fields plus attachment. Crelate has no PAF object. The customer receives the full PAF archive as attachments on the relevant candidate records, and a separate written inventory of all PAFs with their component LCA references is delivered for use by immigration counsel or for DOL audit responses.
OnBlick HR Compliance
Form I-9
Crelate
Candidate (attachment) + Retention Notice
1:1Form I-9 records (Section 1 and Section 2 completion, authorized representative assignments, reverification flags) migrate as candidate attachments. Federal law requires I-9 retention for 3 years after hire or 1 year after termination, whichever is later. We flag every I-9 record in the migration manifest with its retention deadline and include a compliance handoff notice documenting the retention obligation. I-9 data must be accessible in a system that supports audit-ready retrieval for ICE or DOL reviews.
OnBlick HR Compliance
Form I-983 STEM OPT
Crelate
Candidate (attachment) + Note
1:1Form I-983 STEM OPT training plan data (training employer, site supervisor, curriculum objectives, evaluation dates) has no Crelate native object. We extract I-983 data as structured fields in a migration field sheet and attach the completed I-983 PDF to the candidate record. STEM OPT students and their designated training plans should be tracked in a separate immigration compliance system post-migration because Crelate does not support the government-mandated form structure or the 6-month evaluation cycle.
OnBlick HR Compliance
Document Attachments
Crelate
Candidate (attachments)
1:1Documents stored in OnBlick's HR Drive associated with employee records, immigration cases, PAFs, I-9s, and I-983s migrate as attachments to the corresponding Crelate candidate record. We preserve the original filename, file type, and upload timestamp. Documents without a clear candidate parent (organization-level compliance documents, audit reports) are delivered as a separate file archive with a manifest identifying the associated employee and document type.
OnBlick HR Compliance
Electronic Signatures
Crelate
Candidate (note)
1:1E-signature audit trails from OnBlick's Signeasy integration (signer identity, timestamp, IP address, document reference) migrate as a formatted Note on the relevant candidate record. The actual signed document migrates as an attachment; the signature audit trail metadata migrates as structured text fields within the Note so that legal proof of execution is preserved for immigration and I-9 audit purposes.
OnBlick HR Compliance
Timesheet
Crelate
N/A (out of scope)
1:1Timesheet records (work hours, project associations, supervisor assignments, approval status) are an OnBlick HR feature with no equivalent in Crelate's ATS data model. Timesheets do not migrate. If the customer uses Crelate for temp staffing or direct-hire placement with client-billed timesheets, those timesheet records remain in OnBlick until the customer implements a dedicated timesheet tool. We document the timesheet record count and date range in the migration manifest for the customer's records.
OnBlick HR Compliance
Leave Record
Crelate
N/A (out of scope)
1:1Leave management records (PTO balances, accrual history, leave policy associations) do not migrate. Crelate is an ATS and recruitment CRM; it does not have a leave management or PTO tracking module. If the customer requires leave tracking post-migration, a separate HRIS with leave management capabilities should be selected and implemented. We export a leave balance snapshot as a CSV attachment to the employee record for reference.
OnBlick HR Compliance
SOC Classification
Crelate
Candidate (custom field) + Note
lossySOC occupation codes, titles, and wage level mappings sourced from O*NET and FLC Data Center in OnBlick migrate as a custom field (soc_code__c) on the candidate record plus a formatted Note explaining the wage level determination. We preserve the SOC code and wage level that was certified at LCA filing time as historical values, not current equivalents, to maintain audit consistency.
OnBlick HR Compliance
User and Role Assignment
Crelate
Candidate (source system reference)
1:1OnBlick user accounts and role-based access control assignments do not map to Crelate's user model. Crelate user seats are allocated for recruiters and hiring managers; OnBlick admin and compliance officer roles have no Crelate equivalent in the ATS context. We extract a user-role matrix from OnBlick as a reference document and deliver it to the customer's IT or HR admin for provisioning Crelate access based on recruiting and HR responsibilities.
| OnBlick HR Compliance | Crelate | Compatibility | |
|---|---|---|---|
| Employee | Candidate1:1 | Fully supported | |
| Organization | Organization1:1 | Fully supported | |
| Work Authorization Record | Candidate (custom fields)lossy | Fully supported | |
| Immigration Case | Candidate (linked record)1:1 | Fully supported | |
| Labor Condition Application (LCA) | Candidate (custom fields) + Attachmentlossy | Fully supported | |
| Public Access File (PAF) | Candidate (attachment)1:1 | Fully supported | |
| Form I-9 | Candidate (attachment) + Retention Notice1:1 | Fully supported | |
| Form I-983 STEM OPT | Candidate (attachment) + Note1:1 | Fully supported | |
| Document Attachments | Candidate (attachments)1:1 | Fully supported | |
| Electronic Signatures | Candidate (note)1:1 | Mapping required | |
| Timesheet | N/A (out of scope)1:1 | Fully supported | |
| Leave Record | N/A (out of scope)1:1 | Fully supported | |
| SOC Classification | Candidate (custom field) + Notelossy | Fully supported | |
| User and Role Assignment | Candidate (source system reference)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
OnBlick HR Compliance gotchas
No public migration API forces manual export negotiation
I-9 retention obligations survive data migration
Work authorization expiration dates must transfer with precise timelines
Custom object schemas are not programmatically accessible
SOC and LCA data versioning requires historical context
Crelate gotchas
120 req/min API rate limit throttles bulk migrations
20 custom field per-entity cap forces data model decisions
15,000-record export ceiling on single operations
Sequences and automation workflows do not migrate
API key is a querystring parameter, not a header
Pair-specific challenges
Migration approach
Data export request and schema discovery
We open a formal data export engagement with OnBlick support on behalf of the customer, requesting a full structured export of all record types including Employee, Work Authorization, Immigration Case, LCA, PAF, I-9, I-983, Document Attachments, and Electronic Signature audit trails. While awaiting OnBlick's response, we conduct a UI-based schema review with the customer's OnBlick administrator account to enumerate all active custom objects, custom fields, and organizational structures. We generate a record-count estimate per object and identify any records flagged as inactive, archived, or outside the immigration scope.
Immigration compliance scoping and handoff design
We conduct a compliance-focused scoping session with the customer to identify every active H-1B petition, STEM OPT I-983 training plan, and I-9 record with an unresolved retention obligation. We determine whether the customer will use a separate immigration case management tool post-migration (fragomen, corporate immigration counsel, a new vendor) or handle immigration compliance manually with Crelate attachments. We design the custom field schema in Crelate for work authorization tracking and confirm the immigration handoff package structure with the customer's compliance officer or immigration attorney before any data is extracted from OnBlick.
Crelate custom field configuration and sandbox validation
We create the custom candidate fields required for work authorization tracking (visa_type__c, work_authorization_start__c, work_authorization_expiry__c, authorization_status__c), SOC code capture (soc_code__c), and signature metadata. We configure Crelate Organizations and validate the candidate-organization lookup relationship. All custom fields and organizational structures are validated in a Crelate sandbox or test environment before production data is loaded. We run a trial migration of 10-20 employee records and spot-check field mappings, attachment integrity, and expiration date precision before proceeding to full production migration.
Immigration documentation archive and compliance handoff package
We assemble a structured immigration documentation archive containing all PAF PDFs and component data, LCA records with certified SOC and wage data, I-983 training plans, and I-9 records as searchable PDF attachments linked to the relevant candidate. The archive is delivered alongside the Crelate candidate migration and includes a retention deadline manifest for each I-9 record, an active H-1B case status summary, and a written handoff letter suitable for delivery to immigration counsel. This package satisfies the compliance continuity requirement for employers transitioning from a dedicated immigration platform.
Production migration in dependency order with delta reconciliation
We execute the production migration in the following order: Crelate Organizations (employer entities), Candidates with custom authorization fields, candidate attachments (I-9s, PAFs, LCA PDFs, I-983s), immigration case notes, signature audit trail notes, and SOC classification notes. Each phase emits a row-count reconciliation report. We capture a migration timestamp at cutover and perform a delta pass for any records modified in OnBlick during the migration window. I-9 and work authorization expiration dates are validated for full date precision (year-month-day) before each batch is committed.
Cutover, validation, and post-migration inventory delivery
We freeze OnBlick write access at cutover, execute a final delta migration pass, and confirm Crelate as the system of record. We deliver the immigration compliance handoff package, the timesheet and leave balance CSV snapshot, the user-role matrix for Crelate provisioning, and a written inventory of every active H-1B case, LCA, and I-9 record with its retention deadline. We support a one-week hypercare window for data reconciliation issues. We do not rebuild OnBlick workflows, SOC predictor logic, PAF assembly rules, or I-9 authorized representative processes in Crelate; these are documented separately for the customer's compliance team.
Platform deep dives
OnBlick HR Compliance
Source
Strengths
Weaknesses
Crelate
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across OnBlick HR Compliance and Crelate.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
OnBlick HR Compliance: Not publicly documented.
Data volume sensitivity
OnBlick HR Compliance doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during OnBlick HR Compliance to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your OnBlick HR Compliance to Crelate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave OnBlick HR Compliance
Other ways to arrive at Crelate
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.