HRMS migration

Migrate from OnBlick HR Compliance to Crelate

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 logo

OnBlick HR Compliance

Source

Crelate

Destination

Crelate logo

Compatibility

79%

11 of 14

objects map 1:1 between OnBlick HR Compliance and Crelate.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

OnBlick HR Compliance logo

OnBlick HR Compliance

What's pushing teams away

  • Limited third-party integrations beyond QuickBooks Online and E-Verify Web Services restrict organizations with established HR tech stacks from using OnBlick as a system of record.
  • Pricing at $1,099/month starting is positioned for mid-to-enterprise employers; smaller teams with infrequent immigration needs find the cost difficult to justify.
  • Steep learning curve for immigration-naive HR staff who lack H-1B or LCA process knowledge, creating dependency on vendor support for day-to-day operations.
  • No publicly documented migration API or bulk export mechanism makes data portability a manual, support-dependent process that complicates switching platforms.
  • Customization options are restricted compared to general-purpose HRIS platforms, frustrating teams with non-standard onboarding or compliance workflows.

Choosing

Crelate logo

Crelate

What's pulling them in

  • Affordable per-seat pricing with transparent tiers makes Crelate accessible for small-to-mid staffing firms evaluating ATS platforms for the first time.
  • Fast implementation reported by customers—some describe getting live in a matter of minutes with support team assistance.
  • Unified ATS + CRM in a single product eliminates the need to buy and synchronize separate recruiting and sales tools.
  • Flexible custom fields across Contacts, Companies, and Opportunities allow recruiting teams to capture firm-specific data without developer involvement.
  • Positive reviews highlight the product's intuitive interface and functional breadth for teams that need recruiting workflows without enterprise overhead.

Object mapping

How OnBlick HR Compliance objects map to Crelate

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

maps to

Crelate

Candidate

1:1
Fully supported

OnBlick 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

maps to

Crelate

Organization

1:1
Fully supported

OnBlick 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

maps to

Crelate

Candidate (custom fields)

lossy
Fully supported

Work 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

maps to

Crelate

Candidate (linked record)

1:1
Fully supported

OnBlick 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)

maps to

Crelate

Candidate (custom fields) + Attachment

lossy
Fully supported

LCA 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)

maps to

Crelate

Candidate (attachment)

1:1
Fully supported

OnBlick 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

maps to

Crelate

Candidate (attachment) + Retention Notice

1:1
Fully supported

Form 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

maps to

Crelate

Candidate (attachment) + Note

1:1
Fully supported

Form 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

maps to

Crelate

Candidate (attachments)

1:1
Fully supported

Documents 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

maps to

Crelate

Candidate (note)

1:1
Mapping required

E-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

maps to

Crelate

N/A (out of scope)

1:1
Fully supported

Timesheet 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

maps to

Crelate

N/A (out of scope)

1:1
Fully supported

Leave 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

maps to

Crelate

Candidate (custom field) + Note

lossy
Fully supported

SOC 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

maps to

Crelate

Candidate (source system reference)

1:1
Fully supported

OnBlick 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.

Gotchas + challenges

What specifically takes care here

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 logo

OnBlick HR Compliance gotchas

High

No public migration API forces manual export negotiation

High

I-9 retention obligations survive data migration

High

Work authorization expiration dates must transfer with precise timelines

Medium

Custom object schemas are not programmatically accessible

Medium

SOC and LCA data versioning requires historical context

Crelate logo

Crelate gotchas

High

120 req/min API rate limit throttles bulk migrations

High

20 custom field per-entity cap forces data model decisions

Medium

15,000-record export ceiling on single operations

Medium

Sequences and automation workflows do not migrate

Low

API key is a querystring parameter, not a header

Pair-specific challenges

  • Immigration objects have no native home in Crelate's ATS schema

    Crelate is an applicant tracking and recruitment CRM. It has no native I-9, E-Verify, H-1B petition, LCA, PAF, or Form I-983 object. The immigration compliance data that OnBlick manages (H-1B case status, LCA records, PAF PDFs, I-983 training plans) must be handled as candidate attachments, custom fields, or a separate immigration case management tool. We flag every immigration-specific record in the migration manifest, attach the relevant documents to the candidate record in Crelate, and deliver a written compliance handoff package for the customer's immigration counsel or compliance officer. Organizations that rely on OnBlick for active H-1B case management need to establish a replacement immigration platform before the migration cuts over.

  • I-9 retention obligations follow the employer regardless of where records migrate

    Federal law (8 CFR 274a) requires employers to retain Form I-9 records for 3 years after the date of hire or 1 year after the date of termination, whichever is later. When migrating away from OnBlick, we export the complete I-9 record set including Section 1 and Section 2 completion data, authorized representative assignments, and reverification history as candidate attachments in Crelate. The retention obligation transfers to Crelate or to a designated compliance archive. We include a retention deadline manifest with every I-9 record. Employers who terminate OnBlick access without preserving I-9 records remain legally responsible for retention and audit readiness under ICE and DOL scrutiny.

  • No public API at OnBlick forces manual export negotiation

    OnBlick does not publish a public REST or GraphQL API for bulk data extraction. Every migration engagement begins with a formal data export request to OnBlick support. Depending on OnBlick's response time and data preparation capacity, this step can add three to ten business days to the project timeline. We request a full schema export and all available record types during the initial outreach. If OnBlick requires a support ticket, legal data processing agreement, or offboarding process to initiate the export, we coordinate with the customer's account administrator to file and track the request.

  • Work authorization expiration dates must transfer at full precision

    OnBlick tracks work authorization expiration at the employee level and triggers alerts 6 months before expiry. When migrating to Crelate, we extract the full authorization timeline including visa type, start date, and expiration date and load them into custom candidate fields. The expiration date must transfer at full precision; resetting it to a current or placeholder date destroys the lead time that OnBlick accumulated. After migration, the customer should configure a reminder workflow in Crelate or a separate HR tool to maintain the 6-month expiration alert cadence. We document the expiration date for every active work authorization in the migration manifest.

  • Timesheet and leave data have no Crelate equivalent and will not transfer

    OnBlick's timesheet and leave management features (work hours, project associations, PTO balances, accrual histories) have no corresponding object in Crelate's ATS data model. These records do not migrate. We export a timesheet and leave balance snapshot as a CSV attachment to each employee record before cutover, documenting the last recorded balance and period. If the customer needs ongoing timesheet or PTO tracking, those features require a separate HRIS implementation. Leaving timesheet and leave data stranded in OnBlick without an export creates a data gap if the OnBlick subscription is terminated before a replacement system is live.

Migration approach

Six steps for a successful OnBlick HR Compliance to Crelate data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

OnBlick HR Compliance logo

OnBlick HR Compliance

Source

Strengths

  • Specialized I-9 and E-Verify Web Services integration with authorized representative assignment for remote hires satisfies federal 3-day verification windows.
  • SOC predictor engine pulls wage and occupation data from O*NET and FLC Data Center to reduce H-1B petition RFEs tied to misclassification.
  • Automated Public Access File assembly from certified LCAs reduces hours of manual document collection to seconds of platform processing.
  • Proactive work authorization expiration alerts trigger 6 months in advance, giving HR teams sufficient lead time for reverification or extension filing.
  • Case studies report 50-60% reduction in onboarding time and HR workload when replacing paper-based I-9 and immigration workflows.

Weaknesses

  • No publicly documented migration API; bulk data extraction requires OnBlick support engagement and direct database access negotiation.
  • Pricing starts at $1,099/month, positioning the platform for mid-market to enterprise employers; smaller teams find the cost difficult to justify for infrequent immigration needs.
  • Limited third-party integrations restrict organizations with established HRIS and payroll stacks from using OnBlick as a single system of record.
  • Steep learning curve for HR staff without prior immigration experience; platform assumes compliance process knowledge.
  • Custom object and custom field creation is supported but schema export is not accessible via API, complicating migration scoping.
Crelate logo

Crelate

Destination

Strengths

  • Unified ATS and CRM in a single platform reduces data synchronization overhead for recruiting teams.
  • Fast setup with guided implementation reported as a significant time saver for small teams.
  • Transparent per-seat pricing without surprise fees at the base tier.
  • Flexible custom field configuration across core objects without developer dependency.
  • Export capability supports up to 15,000 records per operation for Contacts, Companies, and Opportunities.

Weaknesses

  • API rate limit of 120 requests per minute restricts bulk migration throughput.
  • Custom field cap of 20 per entity requires field consolidation for complex recruiting schemas.
  • All advanced features (Activities, Activity Forms, Core Record Field customization) are tier-gated add-ons.
  • Customer service responsiveness receives consistent negative feedback in reviews.
  • Resume parsing quality trails competitors and generates support requests.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across OnBlick HR Compliance and Crelate.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    OnBlick HR Compliance: Not publicly documented.

  • Data volume sensitivity

    B

    OnBlick HR Compliance doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your OnBlick HR Compliance to Crelate migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about OnBlick HR Compliance to Crelate data migrations

Answers to the questions buyers ask most during OnBlick HR Compliance to Crelate migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between four and six weeks for organizations with up to 500 employee records and no active immigration case volumes requiring structuring. Migrations involving H-1B case records, I-983 STEM OPT plans, LCA history, and PAF archives extend to eight to twelve weeks because of the additional custom field design, document attachment processing, and compliance handoff documentation. The OnBlick data export negotiation adds three to ten business days that runs in parallel with scoping and Crelate configuration.

Adjacent paths

Related migrations to explore

Ready when you are

Move from OnBlick HR Compliance.
Land in Crelate, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day