HRMS migration

Migrate from OnBlick HR Compliance to BambooHR

Field-level mapping, validation, and rollback between OnBlick HR Compliance and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.

OnBlick HR Compliance logo

OnBlick HR Compliance

Source

BambooHR

Destination

BambooHR logo

Compatibility

100%

12 of 12

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

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

OnBlick HR Compliance and BambooHR serve different primary use cases. OnBlick is built for US employers managing I-9, E-Verify, H-1B petitions, LCAs, and Public Access Files for nonimmigrant workforces. BambooHR is a general-purpose HRIS designed for small-to-mid-market teams that need employee records, onboarding, time-off management, and compliance tooling without immigration case management. The migration gap is structural: H-1B case records, LCA filings, PAF assemblies, and Form I-983 STEM OPT data have no native BambooHR equivalents. We extract those records from OnBlick, package them as structured exports with file attachments, and deliver them alongside the BambooHR migration so your admin can archive the immigration layer independently. Employee profiles, work authorization expiration timelines, timesheets, and leave records migrate into BambooHR's standard employee data model. We do not migrate OnBlick workflows, SOC predictor rules, or custom compliance calculation objects; these require a written handoff inventory for your team to evaluate against BambooHR's compliance module.

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

BambooHR logo

BambooHR

What's pulling them in

  • Lowest friction entry point for SMBs moving off spreadsheets — intuitive interface means most teams are functional within days, not weeks.
  • Consolidation value: BambooHR merges ATS, onboarding, HR records, time-off, and payroll into a single pane of glass that employees never need to leave.
  • Volume discounts applied automatically by headcount, so pricing scales predictably as the company grows without renewal negotiations.
  • BambooHR reports most customers go live in four to six weeks, making it a realistic commitment for under-resourced HR teams.
  • Award-winning Support Heroes cited frequently in reviews — responsive human support after implementation is a differentiator.

Object mapping

How OnBlick HR Compliance objects map to BambooHR

Each row shows how a OnBlick HR Compliance object lands in BambooHR, 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

BambooHR

Employee

1:1
Fully supported

OnBlick employee profiles (name, contact, department, employment status, job title, hire date, termination date) map directly to BambooHR employee records. BambooHR's standard employee fields cover all profile data. OnBlick's employee_number maps to BambooHR's employeeNumber field. We extract the full employment status transition history and note the effective dates in BambooHR's job history fields where supported.

OnBlick HR Compliance

Work Authorization Records

maps to

BambooHR

Employee (Visa fields)

1:1
Fully supported

OnBlick work authorization records (visa type, start date, expiration date) map to BambooHR's employee visa tracking fields: expires (visa expiration date), expiryDate (passport expiry), and the visa type field. We preserve the full authorization timeline so the destination retains the original expiration baseline. BambooHR's visa field does not support automated 6-month expiration alerts; we flag this gap and recommend the customer configure manual reminders or use BambooHR's VirgilHR compliance intelligence for general HR compliance alerts.

OnBlick HR Compliance

Immigration Cases

maps to

BambooHR

No equivalent

1:1
Fully supported

OnBlick immigration case records (H-1B petition checklists, status history, reviewer assignments, supporting documents) have no native BambooHR equivalent. BambooHR does not include an immigration case management module. We extract these records as structured CSV exports with associated file attachments and deliver them alongside the BambooHR migration. The customer's immigration team or outside counsel archives the case file independently. We document the complete case record schema in the migration handoff inventory.

OnBlick HR Compliance

Labor Condition Applications (LCAs)

maps to

BambooHR

No equivalent

1:1
Fully supported

LCA records from OnBlick contain wage levels, job titles, prevailing wages, employment locations, and iCert Registry filing references. BambooHR has no LCA tracking module. We export LCA records as structured data and PDF file attachments, preserving the certified SOC code and wage level that was active at filing time (not the current equivalent). This ensures DOL audit consistency if the employer is ever audited post-migration.

OnBlick HR Compliance

Public Access Files (PAF)

maps to

BambooHR

No equivalent

1:1
Fully supported

PAFs are auto-assembled composite documents in OnBlick combining certified LCAs, O*NET SOC codes, and FLC wage data. BambooHR does not generate or store PAFs. We export the assembled PAF PDFs and underlying component data so the employer retains the full PAF package. We note which LCA records feed each PAF so the customer can reassemble if needed.

OnBlick HR Compliance

Form I-9 Records

maps to

BambooHR

Document attachment (employee record)

1:1
Mapping required

OnBlick Form I-9 records (Section 1 and Section 2 completion data, authorized representative assignments, reverification flags) are legally sensitive documents with retention obligations. We export the full I-9 record set including reverification history. In BambooHR, we attach the I-9 PDF as an employee document. BambooHR's Mitratech I-9 integration handles new hires going forward; the migrated historical I-9 records are attached to the employee profile as reference documents. The retention obligation (3 years after hire or 1 year after termination) transfers with the record.

OnBlick HR Compliance

Form I-983 STEM OPT Records

maps to

BambooHR

No equivalent

1:1
Mapping required

OnBlick I-983 STEM OPT records contain training plans, site supervisor details, and curriculum objectives. BambooHR has no I-983 form structure. We export I-983 data as structured fields mapped to a flat CSV, with the completed form PDF as an attachment. The customer's STEM OPT administrator retains these records per USCIS guidance; the records are archived off-platform with a reference link in the migration handoff inventory.

OnBlick HR Compliance

Timesheets

maps to

BambooHR

Timesheets

1:1
Fully supported

OnBlick timesheet records (work hours, project associations, supervisor assignments, approval status) map to BambooHR time tracking. We transfer line-item detail with hours, dates, and supervisor assignments. If OnBlick timesheets include custom project or cost-center fields, we map them to BambooHR custom fields where available or document them as supplementary data for the customer's admin to reconcile post-migration.

OnBlick HR Compliance

Leave Records

maps to

BambooHR

Time Off

1:1
Mapping required

OnBlick leave records (PTO, vacation, holiday balances, accrual methods) map to BambooHR time-off management. Leave policy rules and accrual methods vary between systems; we map leave types to nearest-equivalent BambooHR categories. We extract current balances and accrual rates and transfer them as-is, with a note that accrual method differences (front-loaded vs accrual-per-pay-period) may require BambooHR policy reconfiguration.

OnBlick HR Compliance

SOC Classifications

maps to

BambooHR

No equivalent

1:1
Fully supported

OnBlick SOC classification records store occupation codes, titles, and wage level mappings sourced from O*NET. These feed into LCA preparation and H-1B prevailing wage determinations. BambooHR has no SOC classification module. We export SOC code history with the certified wage level and date, preserving historical context for DOL compliance. SOC codes used in active LCA filings are flagged in the handoff inventory.

OnBlick HR Compliance

Custom Objects

maps to

BambooHR

No equivalent

1:1
Fully supported

OnBlick supports administrator-level custom objects, fields, rules, calculations, and views, but the platform does not expose a schema export endpoint. We identify custom objects by reviewing OnBlick's UI with the customer's administrator account during discovery. If custom objects contain compliance or immigration data, we enumerate their fields and export the data as structured CSV. We document every custom object and field in the migration handoff inventory for the customer's admin to evaluate against BambooHR custom fields.

OnBlick HR Compliance

Document Attachments

maps to

BambooHR

Employee Files

1:1
Fully supported

Documents associated with immigration cases, PAFs, and I-9 records stored in OnBlick's HR Drive are exported with their parent object association. We attach immigration and compliance documents to the corresponding employee record in BambooHR as file uploads. The folder structure from OnBlick is preserved as a zip archive delivered alongside the employee data import.

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

BambooHR logo

BambooHR gotchas

High

Undocumented API rate limits can trigger 503 errors

High

Per-employee pricing model requires active record count verification

Medium

API credentials must be sent on every request to avoid extra round trips

Medium

Custom field schema varies per account and requires manual inventory

Low

Document and attachment exports are not covered by standard report exports

Pair-specific challenges

  • Immigration objects have no BambooHR home

    H-1B case records, LCA filings, PAF assemblies, and I-983 STEM OPT records do not have native equivalents in BambooHR. BambooHR's compliance module covers general HR compliance (harassment training, ACA, I-9 via Mitratech) but not immigration case management. We export these records as structured data and PDF files and deliver them alongside the BambooHR migration. The customer's immigration team or outside counsel must archive the immigration layer off-platform. Failing to explicitly handle these records results in data loss at cutover.

  • OnBlick has no public migration API

    OnBlick does not publish a REST or GraphQL API for bulk data extraction. Migration scoping requires filing a data export request with OnBlick support and negotiating a structured data extract, which can add three to seven days to the project timeline. We begin every OnBlick migration by engaging OnBlick support for the export. If OnBlick support is slow to respond, the migration timeline extends. We cannot begin field-level mapping until the schema export arrives.

  • I-9 retention obligation survives data migration

    Federal law requires employers to retain Form I-9 records for three years after hire or one year after termination, whichever is later. When migrating away from OnBlick, we ensure the full I-9 record set including reverification history is exported and the retention obligation is explicitly transferred. The I-9 PDFs are attached to the corresponding employee record in BambooHR as reference documents. BambooHR's Mitratech I-9 integration handles new hires going forward; historical records remain as attached files. The retention obligation does not disappear when the migration completes.

  • Work authorization expiration dates must transfer with correct baselines

    OnBlick tracks work authorization expiration and triggers alerts six months before expiry. When migrating to BambooHR, we extract the full work authorization timeline including visa type, start date, and expiration date so the customer can set correct baselines in BambooHR or a separate compliance tracking tool. Resetting expiration dates to the current date destroys months of lead time and exposes the employer to missed reverification deadlines. We explicitly flag the original expiration date in the employee record migration.

  • Custom object schemas are not programmatically accessible

    OnBlick allows administrators to create custom objects, fields, rules, calculations, and views, but the platform does not expose a schema export endpoint. We can only identify and map custom objects by reviewing OnBlick's UI with the customer's administrator account. If custom objects contain critical immigration or compliance data, we schedule additional discovery sessions specifically to enumerate those fields before migration. Any custom rules or calculation logic must be documented manually and rebuilt in BambooHR or another tool.

Migration approach

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

  1. Engage OnBlick support and enumerate the source schema

    We file a data export request with OnBlick support and schedule a discovery session with the customer's OnBlick administrator to enumerate all active objects, custom fields, immigration case records, LCA history, and PAF archives. We review the UI with the administrator to capture custom object schemas that cannot be programmatically exported. The discovery output is a written source schema inventory covering every OnBlick object the customer wants to preserve.

  2. BambooHR destination setup and employee field mapping

    We configure the BambooHR destination: employee fields mapped from OnBlick profiles, visa expiration dates set from OnBlick work authorization timelines, time-off policies translated from OnBlick leave structures, and timesheet configurations matched to the source. We enable the Mitratech I-9 integration for new hires going forward and attach migrated I-9 PDFs to employee records. We flag any OnBlick immigration objects (H-1B cases, LCAs, PAFs, I-983 records) as archive-only with no BambooHR destination.

  3. Immigration archive packaging

    We extract H-1B case records, LCA filings, PAF PDFs, I-983 data, and SOC classification history as structured data packages and file archives. Each immigration record is tagged with the associated employee identifier for cross-reference. We deliver the archive as a structured zip file with a manifest linking each record to the source OnBlick object and the migrated BambooHR employee.

  4. Sandbox migration and reconciliation

    We run a full migration into BambooHR using a test employee set, reconciling record counts and spot-checking fields (name, hire date, department, visa expiration, timesheet totals) against the OnBlick source. I-9 PDFs are attached and verified as openable. The customer reviews the sandbox output and signs off before production migration begins. Any mapping corrections happen here.

  5. Production migration in dependency order

    We run production migration in record order: employee profiles first (with work authorization expiration dates preserved), then timesheet histories, then leave records, then I-9 document attachments. Immigration case records, LCA filings, and PAF files are packaged as the archive deliverable and handed off separately. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and compliance handoff

    We freeze OnBlick writes during cutover, run a final delta migration of any records modified during the migration window, then set BambooHR as the system of record. We deliver the immigration archive package with full manifest, the custom object field inventory, and the SOC/LCA historical record handoff. We support a one-week hypercare window for reconciliation issues. We do not rebuild OnBlick workflows, SOC predictor rules, or I-9 alert configurations in BambooHR; these are documented in the handoff inventory for the customer's admin to evaluate.

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.
BambooHR logo

BambooHR

Destination

Strengths

  • Single platform consolidating ATS, onboarding, HR records, payroll, and time-off reduces system sprawl for SMBs.
  • Fast implementation — BambooHR reports four to six weeks from kickoff to go-live for most customers.
  • Per-employee pricing with automatic volume discounts makes cost predictable as headcount grows.
  • Strong customer support reputation (Support Heroes) cited consistently across G2, Capterra, and direct testimonials.
  • Well-documented API with UTF-8 encoding, clear field types, and HTTPS-only access.

Weaknesses

  • Mobile application is significantly limited compared to the desktop experience, frustrating remote and field workers.
  • Companies above 150–200 employees frequently outgrow the platform's feature depth and customization surface.
  • Limited advanced reporting and analytics compared to enterprise HR platforms — custom report building is the ceiling.
  • PTO and profile customization are pain points — non-standard accrual policies and complex org structures require workarounds.
  • Document management and attachment handling lack the granularity of dedicated document-centric HR systems.

Complexity grading

How hard is this migration?

Standard HRMS migration. All 7 core objects map 1:1 between OnBlick HR Compliance and BambooHR.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 7 core objects map 1:1 between OnBlick HR Compliance and BambooHR.

  • 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 BambooHR 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 BambooHR data migrations

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

Can't find your answer?

Walk through your OnBlick HR Compliance to BambooHR migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Straightforward migrations under 200 employees with no active H-1B case history land between three and five weeks and complete in four to six weeks. Migrations with active immigration case records, LCA and PAF archives, I-983 STEM OPT data, custom OnBlick objects, or timesheet histories exceeding 12 months extend to eight to twelve weeks. The primary variable is how quickly OnBlick support delivers the data export, which is outside our control and can add three to seven days to the discovery phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from OnBlick HR Compliance.
Land in BambooHR, 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