HRMS migration
Field-level mapping, validation, and rollback between Worknice and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.
Worknice
Source
BambooHR
Destination
Compatibility
10 of 11
objects map 1:1 between Worknice and BambooHR.
Complexity
BStandard
Timeline
4-8 weeks
Overview
Moving from Worknice to BambooHR is a cross-platform migration with a key structural constraint: Worknice has no publicly documented REST API, so all source data extraction relies on Worknice's built-in CSV export tools within the UI. We work with the customer's Worknice admin to batch exports of People, Leave, Reviews, and Documents during scoping, then write to BambooHR using their REST API with the BambooHR-issued API key. Worknice's Australian-specific fields (TFN, superannuation details) require explicit mapping decisions because BambooHR is US-centric and these fields map to custom employee fields or supplemental documents rather than native attributes. Bundle automation, position bundles, and integration connections (Worknice's Connections feature linking people to external ATS and payroll systems) do not migrate; we document these for the customer's HR team to configure in BambooHR post-migration. BambooHR's three-tier pricing (Core from $10, Pro from $17, Elite from $25 per employee per month) gives customers flexibility to select the feature tier matching their post-migration scope.
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 Worknice 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.
Worknice
People
BambooHR
Employee
1:1Worknice People records map to BambooHR Employee records. Each Worknice People record carries first name, last name, email, role (Employee, Contractor, Manager), position assignment, pay details, and integration connections. We map the core name and contact fields directly to BambooHR's standard employee fields. Worknice role assignments map to BambooHR employmentStatus (Full-Time, Part-Time, Contractor) and a custom field for the original Worknice role. The BambooHR API key must belong to an Administrator account to read and write all employee fields.
Worknice
Positions
BambooHR
Job Information (custom fields)
1:1Worknice Positions define job titles and reporting hierarchies. We export position names, department assignments, and reporting manager links as structured metadata. In BambooHR, these map to the Job Info tab (title, department, division, location) plus custom fields for the original Worknice position ID and any manager relationship not captured through BambooHR's native supervisor field. Position bundle assignments are exported as a flat metadata field and flagged for the customer to configure as a BambooHR custom field or group structure post-migration.
Worknice
Leave balances
BambooHR
Time Off
1:1Worknice stores leave entitlements and accrual balances per leave type (Annual Leave, Sick Leave, Personal Leave) tied to position start dates. We export leave type, current balance, and accrual method as separate fields. BambooHR's Time Off module uses Policies created in-app; we import the current balance as a static starting balance and flag that the customer's HR team must configure equivalent accrual policies in BambooHR before go-live. Leave carried forward, approval history, and pending requests require separate handling during cutover.
Worknice
Documents / Paperwork
BambooHR
Employee Files
1:1Worknice stores compliance documents, contracts, and onboarding paperwork per person. We export documents as binary blobs and recreate the attachment relationship in BambooHR using the Files API. File naming conventions from Worknice may not map directly to BambooHR's document organization, so we attach files to the corresponding Employee record and note the original Worknice document type in a BambooHR custom field for each file. Documents larger than 10 MB require chunking per BambooHR's upload limits.
Worknice
Performance Reviews
BambooHR
Performance Management
1:1Worknice supports 360 reviews, customizable review forms, and review status tracking (draft, in-progress, complete). We export reviewer relationships, form question responses, overall rating, and completion status. BambooHR's performance module (Pro and Elite tiers) uses review cycles and configurable forms; we map Worknice review responses to BambooHR's review form structure, flagging any Worknice custom form fields that have no direct BambooHR equivalent as requiring manual entry or a separate review cycle configuration post-migration.
Worknice
Goals and OKRs
BambooHR
Goals
1:1Worknice stores company-level OKRs and employee goals with parent-child alignment hierarchies. We export goal titles, descriptions, progress percentages, due dates, and parent goal relationships. BambooHR Goals (Pro and Elite) supports goal setting and tracking; we map Worknice goal progress to BambooHR goal percent complete, and preserve the parent-child relationship as a custom field pointing to the parent goal ID because BambooHR Goals does not have a native parent-goal linking field. Goal status mapping from Worknice to BambooHR is documented during scoping.
Worknice
Roles
BambooHR
Employee employmentStatus
1:1Worknice assigns roles at the person level: Employee, Manager, Account owner, Contractor. We preserve these as direct fields in the BambooHR Employee record. The Worknice role maps to BambooHR's employmentStatus field (Contractor, Full-Time, Part-Time, Inactive) and a custom multi-select picklist if the organization used multiple simultaneous roles. Manager role assignment is preserved as the supervisor field in BambooHR Job Info.
Worknice
Bundles and templates
BambooHR
Custom fields (configuration)
lossyWorknice Bundles group templates (documents, onboarding tasks, review forms) assigned to positions or people during onboarding. The bundle-to-template relationship has no direct equivalent in BambooHR. We export bundle names and associated template types as structured metadata attached to the relevant Position record, then flag during the design call that bundle automation must be rebuilt as BambooHR onboarding checklists or workflow rules in the destination. This is a configuration handoff, not a data migration.
Worknice
Integration connections
BambooHR
Not migrated
1:1Worknice's Connections feature maps individual People records to external systems (ATS, payroll providers, timesheet tools). These integration IDs are specific to Worknice's integration broker and have no counterpart in BambooHR. We exclude these records from the migration set entirely and flag that the customer must re-establish integration connections in BambooHR after go-live using BambooHR's Integration Marketplace or API-based integrations.
Worknice
Time tracking entries
BambooHR
Time Tracking
1:1Worknice Essential plan includes time tracking per employee with hours, dates, and time category. We export time entry records where this data exists. BambooHR Time Tracking is available on applicable plans; we map Worknice time entries to BambooHR time entries, preserving date, hours worked, and category. Historical time entry volumes and any timesheet approval workflows require review during scoping because high-volume historical data may exceed practical migration scope.
Worknice
Surveys and feedback
BambooHR
Employee Satisfaction (eNPS)
1:1Worknice supports continuous feedback collection and engagement surveys. We export survey responses and feedback records per person where they exist, including survey name, response date, and response text. BambooHR's Employee Satisfaction module (Pro and Elite) uses eNPS surveys with AI-categorized themes; we map Worknice survey response data to BambooHR survey records and flag that survey design and question structures require reconstruction as BambooHR survey templates post-migration.
| Worknice | BambooHR | Compatibility | |
|---|---|---|---|
| People | Employee1:1 | Fully supported | |
| Positions | Job Information (custom fields)1:1 | Fully supported | |
| Leave balances | Time Off1:1 | Mapping required | |
| Documents / Paperwork | Employee Files1:1 | Mapping required | |
| Performance Reviews | Performance Management1:1 | Mapping required | |
| Goals and OKRs | Goals1:1 | Mapping required | |
| Roles | Employee employmentStatus1:1 | Fully supported | |
| Bundles and templates | Custom fields (configuration)lossy | Mapping required | |
| Integration connections | Not migrated1:1 | Not supported | |
| Time tracking entries | Time Tracking1:1 | Mapping required | |
| Surveys and feedback | Employee Satisfaction (eNPS)1:1 | Mapping required |
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.
Worknice gotchas
Minimum annual spend creates migration lock-in
No publicly documented REST API for bulk export
Position bundles do not migrate as structured bundles
Leave accrual methods require manual reconciliation
Integration connections are person-level and non-transferable
BambooHR gotchas
Undocumented API rate limits can trigger 503 errors
Per-employee pricing model requires active record count verification
API credentials must be sent on every request to avoid extra round trips
Custom field schema varies per account and requires manual inventory
Document and attachment exports are not covered by standard report exports
Pair-specific challenges
Migration approach
Scoping and CSV export coordination
We audit the Worknice account with the customer's admin to identify all in-scope entities: People records, Positions, Leave balances, Performance Reviews, Goals, Documents, and any active Bundles or survey data. Because Worknice has no API, we coordinate with the admin to extract CSV exports from Worknice's UI, batching by entity type and date range where export size limits apply. We simultaneously review the BambooHR destination account for existing employees, custom fields, and time-off policies to identify any pre-existing data that needs reconciliation before migration begins.
BambooHR custom field and policy provisioning
We design and provision the BambooHR destination schema before any data import. This includes creating custom fields for Australian-specific data (TFN, superannuation fund, superannuation member number), custom fields for Worknice source identifiers (original Worknice People ID, original position name, bundle assignments), and configuring time-off policies that match the Worknice accrual methods documented during scoping. BambooHR requires the API key to belong to an Administrator account for custom field creation. Schema provisioning happens in a staging environment or the production account with a test employee to validate field visibility and access restrictions.
Employee import with source ID preservation
We import Worknice People records as BambooHR Employee records in dependency order: base employee fields first (name, email, employment status, hire date), then job information (title, department, division, location, supervisor), then compensation and sensitive fields. We preserve the original Worknice People ID in a custom field (worknice_id__c) on each BambooHR employee to support reconciliation and future delta syncs. Any Worknice employee without a valid email is flagged in the reconciliation report for the admin to resolve before proceeding.
Leave balance import and time-off policy mapping
We import Worknice leave balances as BambooHR time-off entries using the static starting balance approach. Each leave type in Worknice maps to a corresponding BambooHR time-off type, and the current balance is entered as an accrued balance in BambooHR. We set the balance effective date to the import date and document the original accrual method from Worknice in the migration notes so the customer's HR team can configure the matching BambooHR policy for future accruals. Pending leave requests are not migrated; the admin processes them in Worknice before cutover.
Document and file migration
We export binary documents from Worknice as individual files, preserving the original filename and Worknice document type. We upload each file to the corresponding BambooHR Employee record using the BambooHR Files API, mapping the Worknice document type to a BambooHR category (Onboarding Documents, Personal Documents, Tax Documents). Files larger than 10 MB are chunked; sensitive files (contracts, tax forms) are uploaded with restricted access. We deliver a file inventory spreadsheet mapping each BambooHR file URL to the original Worknice document reference.
Performance review and goal data migration
We import Worknice Performance Review data as BambooHR review records attached to the corresponding Employee. Each Worknice review cycle maps to a BambooHR review cycle, and individual review questions and responses are mapped to BambooHR's review form structure where field types are compatible. Custom form fields that have no BambooHR equivalent are documented in the review mapping notes for manual entry or alternative tracking. Worknice Goals and OKRs are imported as BambooHR Goals with progress percentages preserved; parent-child goal relationships are stored as a custom field reference.
Cutover, delta sync, and integration rebuild handoff
We freeze Worknice writes during the cutover window, run a final delta migration of any records created or modified since the initial export, then switch the customer's HR stack to BambooHR as the system of record. We deliver a written inventory of Worknice Bundle configurations, Integration Connections, and active survey designs for the customer's HR team to rebuild in BambooHR. We provide a one-week hypercare window for reconciliation issues. We do not rebuild Worknice bundles as BambooHR workflows or re-establish external integrations as part of the standard migration scope.
Platform deep dives
Worknice
Source
Strengths
Weaknesses
BambooHR
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. All 7 core objects map 1:1 between Worknice and BambooHR.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Worknice and BambooHR.
Object compatibility
All 7 core objects map 1:1 between Worknice and BambooHR.
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
Worknice: Not publicly documented.
Data volume sensitivity
Worknice 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 Worknice to BambooHR migration scoping. Not seeing yours? Book a call.
Walk through your Worknice to BambooHR migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Worknice
Other ways to arrive at BambooHR
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.