Migrate from isolved to BambooHR

isolved Employee records map directly to BambooHR Employee. Core fields (first name, last name, SSN, date of birth, hire date, adjusted service date, employment status, marital status, address, and contact information) transfer via batch CSV. SSN is extracted under encryption and re-masked before import into BambooHR. Employee number in isolved maps to BambooHR's employeeId field. Employment category, citizenship, and ethnicity fields map to BambooHR custom fields or standard fields with appropriate picklist selection.

isolved Pay Groups (weekly, biweekly, semi-monthly, monthly) control pay frequency and overtime calculation rules. We extract the Pay Group table and map each group to BambooHR's Pay Frequency setting (stored as a period type: weekly, bi-weekly, semi-monthly, monthly). If BambooHR's Payroll add-on is active, Pay Frequency also drives the payroll run calendar. Pay Groups with custom overtime rules do not migrate as configuration; we document the overtime threshold for the customer's admin to configure in BambooHR Payroll settings.

isolved Job Codes are an employer-defined picklist used for compliance reporting, compensation rules, and headcount analysis. BambooHR does not have a native Job Code object; we map Job Code values to a BambooHR custom picklist field (e.g., jobCode) and export the full isolved Job Code table during scoping to produce a mapping matrix. The customer reviews the matrix and assigns each isolved code to a BambooHR Job Title or creates a new Department entry as appropriate.

isolved Work Locations drive tax withholding, workers comp codes, and benefit eligibility rules. BambooHR uses a Location field on the Employee record to capture work site. We export the full isolved Work Location list and map each location to a BambooHR Location entry (State and Country fields), preserving any workers comp code association in a custom field for the customer's admin to configure in BambooHR's workers comp settings post-migration.

isolved Pay Types (salary, hourly, commission, bonus, and deduction codes) are defined lists that vary by employer. BambooHR stores compensation as a Pay Rate field on the Employee record with separate fields for pay type. We extract the isolved Pay Type table and map each code to a BambooHR payType value (salary, hourly, nonexempt). Custom deduction codes and employer benefit contribution codes that do not have direct BambooHR equivalents are documented in a compensation schema handoff for the customer's admin to set up in BambooHR Payroll.

Historical payroll registers (earnings, taxes, deductions, garnishments) migrate as a structured data export. We extract full payroll history from isolved's batch file format by Pay Group and pay period, preserving pay-period dates, earnings amounts, tax withholdings, deduction codes, and garnishment order details. SSAE-18 audit continuity requires that W-2 reportable amounts and garnishment order identifiers remain auditable after cutover; we re-code deduction schemas to align with the destination format and deliver a payroll register CSV for the customer's records. Note that BambooHR Payroll does not store historical payroll registers as a native object; the data migrates as an exported dataset for record-keeping rather than for display inside BambooHR.

Active benefit elections (medical, dental, vision, HSA, FSA, life insurance) link to Employee records in isolved. We extract enrolled plan names, carrier names, coverage tiers (employee, spouse, family), and monthly premiums. BambooHR tracks benefit elections as a structured module with plan enrollment records linked to Employees. We map enrolled plans to BambooHR Benefit Plan entries and flag any plan types (such as Section 125 cafeteria plan elections) that require manual reconfiguration in BambooHR's benefit settings because plan-level admin rules do not migrate.

Accrued and taken time off by type (PTO, sick, personal, and custom accrual types) migrate as current balances and carry-forward amounts. isolved calculates accruals per Work Location and Pay Group rules; we export the balance snapshot as of the migration date and import it into BambooHR Time Off as the opening balance. Note that accrual rate rules (such as years-of-service step increases) do not migrate as configuration; we document the current accrual rates for each Time Off type and leave the rule configuration to the customer's BambooHR admin.

Employee banking information for payroll disbursement migrates under encryption. We extract routing number, account number, deposit type (full or partial), and deposit amount or percentage fields from isolved's Direct Deposit transactions. Bank account data is masked in transit and only decrypted at the point of import into BambooHR. Note that BambooHR recommends that employees re-enter banking details during onboarding as a security best practice; we flag this to the customer during scoping so they can decide whether to import with re-authentication required or to proceed with the import and notify employees.

Electronically stored employee file attachments (offer letters, performance reviews, I-9s, signed agreements) migrate as document blobs with metadata. We export documents from isolved's file storage and import them into BambooHR's Files section linked to the corresponding Employee record. Document filenames, upload dates, and file types (PDF, DOCX, image) are preserved in BambooHR's metadata. Note that we cannot guarantee format fidelity for files created in legacy formats or with embedded macros; we recommend spot-checking a sample of 20 documents post-migration.

Pending or in-flight change requests in isolved (salary changes, direct deposit updates, name or address changes, HSA elections) are stateful records that do not auto-resolve on import. We extract pending transaction records with their current status, transaction type, and effective date, and deliver them as a transaction queue CSV. The customer's BambooHR admin reviews and completes each transaction manually post-migration since BambooHR's workflow model does not accept imported pending states.