Migrate from ZenHR to BambooHR

ZenHR Employees map to BambooHR Employees with the full Personal, Professional, and Financial sections mapped to BambooHR's employee record fields. ZenHR's bank account details, GOSI number, and salary components transfer to BambooHR's bank info section and custom fields. MENA-specific fields that have no BambooHR native equivalent (end-of-service benefit rate, notice period in days, visa status) are created as custom fields in BambooHR during the pre-migration schema phase. Every ZenHR tenant has unique custom fields on the Employee object; we audit these during discovery so that null values do not land on BambooHR mandatory fields during import.

ZenHR Timeoff records carry balance, request status, and a transaction history of accruals and deductions. BambooHR's Time Off tracks current balance per policy but does not expose a per-employee transaction audit trail by default. We sequence all ZenHR Timeoff Transactions in chronological date order, calculate the opening balance at the migration effective date, and set the BambooHR opening balance accordingly. Pending leave requests are flagged for the customer to re-submit post-migration because BambooHR requires an active employee and a valid workflow to create requests.

ZenHR Documents (contracts, IDs, certificates, offer letters) with e-signature metadata migrate to BambooHR Employee Files attached to the corresponding Employee record. We transfer document type, expiry date, and upload timestamp as metadata fields. Binary file transfers are handled separately via BambooHR's file upload API. Any document that has expired is flagged in the migration report for the customer's admin to handle per BambooHR's expiry alert configuration.

ZenHR Branches (physical office locations across the MENA region) map to BambooHR Locations. Each Branch's address, country, and timezone transfer as Location fields. Branch-level settings that govern overtime rules or leave policy applicability are noted in the migration report and can be mapped to BambooHR Time Off policies per Location if the customer's configuration requires it.

ZenHR separates Branches, Levels, and Positions as distinct structural objects with cross-references. BambooHR collapses organizational hierarchy into a single Departments list with a Name field. We map ZenHR Departments and Levels into BambooHR Departments, preserving Level information as a custom field on the Employee record (e.g., custom_employee_level__c) if the customer's reporting requires it. Positions that function as job titles map to the Employee job title field.

ZenHR Terminations are separate records with EOSB/gratuity amounts and effective dates. We migrate each Termination as a historical Employee record with an Employment History entry in BambooHR, setting the termination date and preserving the EOSB amount, final settlement currency, and notice period served in custom fields. The original effective_date is preserved as the canonical termination date rather than the migration import timestamp. This is critical for MENA labor law compliance audits and for any future gratuity recalculation.

ZenHR Employee Loans with principal, remaining balance, and repayment schedule map to a custom loan object or custom fields on the BambooHR Employee record. BambooHR does not have a native Loans module. We create custom fields for loan_principal__c, loan_remaining_balance__c, loan_monthly_deduction__c, and loan_start_date__c, and flag active loans in the migration report for the customer's admin to verify and continue or close the repayment schedule in the destination system.

ZenHR Overtime records with type classification (regular, holiday, weekend), hours, and rate map to custom fields on the BambooHR Employee record. BambooHR's Time Off does not natively support overtime types. We aggregate overtime by type and employee for the migration period and store the total hours and average rate as custom fields. Customers who need ongoing overtime tracking use BambooHR's Time Tracking add-on or a third-party time-clock integration post-migration.

ZenHR Branch Employee Shifts assign employees to shift schedules by branch and date range. BambooHR does not have a native clock-in/clock-out module (Time Tracking is available as a separate add-on). We migrate shift assignments as custom fields on the Employee record and aggregate attendance summaries (total regular hours, total overtime hours per month) as summary custom fields. Individual clock-in/clock-out events are voluminous and not migrated unless the customer requires them specifically and has BambooHR Time Tracking enabled.

ZenHR distinguishes Users (system login) from Employees (person records). A person can exist as an Employee without a User login. We map ZenHR User accounts to BambooHR user accounts by email match. Roles and permissions in ZenHR map to BambooHR's permission set model, where the admin assigns system access and module visibility per user. Any ZenHR User without an email match in BambooHR goes to a reconciliation queue for the customer's admin to provision.

ZenHR payroll runs with line-item salary components, deductions, and net pay can be mapped to BambooHR Payroll if the customer is on BambooHR Payroll and operates in a US or Western payroll context. For MENA-based payroll, BambooHR Payroll does not support GCC tax withholding, GOSI deductions, or EOSB accrual calculations. We migrate payroll summary data (most recent salary, last pay date, last deduction amounts) as custom fields on the Employee record and recommend a parallel payroll system or manual reconciliation for historical payroll auditing. Off-cycle payments are noted in the migration report.

ZenATS Candidates, Vacancies, and pipeline stage history migrate to BambooHR Job Applications and Job Openings. BambooHR Hiring does not have the same pipeline depth as ZenATS — there are no multiple rounds, interview scorecards, or custom stage templates by default. We migrate candidate name, email, phone, application date, vacancy name, and current stage. Candidate SMS and email communication bodies are not accessible via ZenHR API and are flagged as a data gap; we recommend a manual export from ZenATS for any candidate communication history the customer wishes to preserve.