Migrate from Checkwriters to BambooHR

Checkwriters Employees map to BambooHR Employee records. Core fields (first name, last name, date of birth, hire date, termination date, job title, department, location, employment status) map directly. Checkwriters re-hire flags and employee ID are preserved in custom fields on the BambooHR Employee record. HR Admin access is required during scoping to enumerate all active custom field definitions before field-level mapping begins.

Checkwriters payroll items use check-date ranges (start check date, end check date) to define when a rate or earning type is active. We translate each rate's effective check-date window to a calendar effective date in BambooHR's pay run configuration. Pay types (regular, overtime, bonus, commission) map to BambooHR earnings types; the rate stored in the check-date record becomes the pay rate on the BambooHR Employee record.

Checkwriters PTO, sick time, and Bereavement accrual balances map to BambooHR time-off policies. We identify the accrual policy type (annual reset vs. carry-forward) during scoping and configure BambooHR's accrual policy accordingly. Running balances are imported as initial balance values at cutover. Accrual rate and frequency information from Checkwriters translates to BambooHR's accrual rate configuration (hours per pay period, annual cap, rollover limits).

Historical time-off requests from Checkwriters (request date, request type, start date, end date, status, approver) migrate to BambooHR time-off records. Current pending requests are flagged during scoping for manual re-entry or coordinated approval timing around cutover. Request status transitions (approved, denied, cancelled) map directly to BambooHR time-off status values.

Checkwriters deductions (pre-tax 401k, health insurance, FSA; post-tax wage garnishments) map to BambooHR deduction records tied to the employee. Benefit plan enrollments are mapped to BambooHR benefit plans, with the carrier name, plan ID, and coverage tier preserved. Open enrollment period flags and qualifying life event dates require date translation to BambooHR's benefits tracking module, which is an add-on outside Core.

Checkwriters company-level custom fields (text, date, dropdown, numeric) map to BambooHR employee custom fields with equivalent types. Discovery requires HR Admin-level access to the Checkwriters tenant during scoping. We enumerate all active custom field definitions, map field types to BambooHR field types, and import values at the employee record level during the main migration phase.

Employee documents (offer letters, signed agreements, I-9s, performance records) are stored in Checkwriters' Document Center with visibility restrictions. We extract file references and import metadata (document type, upload date, associated employee) into BambooHR Documents, preserving the document name and category. Document visibility settings are translated to BambooHR's employee document access controls. File content itself migrates as attachments.

Historical pay stub data must be pulled from Checkwriters via Report Writer, not via API, because no public bulk export endpoint exists. We coordinate with the customer's HR Admin to define the correct report types (earnings, taxes, deductions) and date ranges before extraction. W-2 and 1099 historical references migrate as payroll history records in BambooHR, with the pay date as the index date. If BambooHR Payroll is not in scope, we migrate pay stub references as document links only.

Checkwriters Report Writer definitions cannot be migrated directly to BambooHR Reports because the reporting engines are structurally different. We extract the report definitions and column layouts during scoping and deliver a written mapping document showing which Checkwriters reports map to which BambooHR standard or custom reports. The customer's HR Admin rebuilds the reports in BambooHR's report builder post-migration.

Checkwriters onboarding (available on HR Premier and above) includes document e-signature collection and step tracking with a defined sequence of tasks per new hire. BambooHR Onboarding is a separate module with customizable task checklists, e-signature via electronic W-4, I-9, and direct deposit forms. Completed onboarding task histories do not migrate because the workflow engines are proprietary. We deliver a written inventory of active Checkwriters onboarding templates for the customer's admin to reconstruct in BambooHR Onboarding.

Performance review records and templates in Checkwriters (an add-on module) are stored in a proprietary format tied to the review workflow engine and cannot be exported via documented API. We do not attempt automated migration of review content because it produces incomplete or corrupted records. We flag this gap upfront and recommend a parallel manual review process in BambooHR Pro, with review templates rebuilt as BambooHR review cycle templates post-migration.

Checkwriters benefit plan enrollments, carrier connections, and deduction elections map to BambooHR's Benefits Tracking module (an add-on to Core and Pro). We map active enrollments to destination plan equivalents, including carrier name, plan type (medical, dental, vision), coverage tier (employee, employee+spouse, family), and annual deduction amount. Open enrollment period data and qualifying life event elections require coordination with the customer's benefits admin to ensure correct plan-year alignment in BambooHR.