Migrate from Zimyo to BambooHR

Zimyo employee records map directly to BambooHR employee profiles. We map standard fields including name, date of birth, hire date, employment status, job title, department, location, compensation, bank details, and emergency contacts. Custom employee properties on the Zimyo side map to BambooHR custom fields, with type conversion (text to text, date to date, picklist to dropdown). Zimyo's employment type distinctions (full-time, part-time, contract) map to BambooHR's employee type field.

Zimyo leave types, entitlement balances, accrual rules, and carry-forward policies map to BambooHR Time Off policies. We validate each employee's leave balance independently against Zimyo reports before committing. Carry-forward rules require manual review in BambooHR post-migration because BambooHR handles carry-forward configuration per policy rather than per employee. Leave approvals and comments migrate as note attachments on the Time Off request record.

Zimyo clock-in/clock-out timestamps with geo-location and overtime calculations do not map directly to BambooHR because BambooHR's Time Tracking add-on handles timesheets and billable hours rather than raw clock events. We map the most recent attendance summary (last 90 days) as a Time Off balance adjustment for employees transitioning to BambooHR's accrual-based time-off model. Historical attendance logs beyond 90 days are exported as a CSV file inventory for the customer's admin to reference. Overtime calculations from Zimyo do not migrate; overtime eligibility rules require rebuild in BambooHR's Time Tracking configuration.

Zimyo payroll data (earnings, deductions, tax withholdings, net pay) maps to BambooHR Payroll if the customer activates that add-on. If BambooHR Payroll is not in scope, we export payroll history as a structured CSV inventory for the customer's finance team and payroll admin. INR-denominated payroll components require currency conversion with timestamped exchange rates before import into BambooHR's USD-only payroll module. Historical payroll runs cannot be retroactively loaded into BambooHR Payroll; only current and future payroll runs process natively.

Zimyo performance cycles, goals, competency ratings, self-assessments, and manager feedback map to BambooHR Performance when the customer licenses the Pro plan or above. Review templates and competency frameworks vary by organization and require schema alignment during scoping. Rating scales differ between platforms; we map Zimyo's rating values to BambooHR's 5-point scale with a custom field preserving the original Zimyo rating for audit. Goals and OKRs from Zimyo do not map to a native BambooHR object; we export them as a goals inventory CSV for manual re-entry or third-party goal-tracking tool integration.

Zimyo job postings, candidate profiles, application stages, interview schedules, scorecards, and offer letters map to BambooHR's applicant tracking system. Hiring pipeline stages are configurable per organization; we map Zimyo stages to BambooHR pipeline stages during scoping. Candidate application history and status migrate with timestamps. We do not migrate Zimyo's job board posting configurations; the customer re-posts openings in BambooHR ATS post-migration.

Zimyo departments, cost centers, and locations map to BambooHR Departments and Locations. Reporting hierarchies migrate as supervisor relationships on employee records. Organization-level workforce management settings from Zimyo do not have a direct BambooHR equivalent; we export them as a configuration inventory for the customer's admin to reapply manually.

Employee documents (contracts, ID proofs, certifications, offer letters) migrate as BambooHR employee files with original filenames and upload timestamps preserved. File integrity checksums are generated post-upload to verify no corruption. Document categories from Zimyo map to BambooHR's document folder structure. Documents exceeding BambooHR's file size limits are flagged and exported to a shared cloud location with links in the employee record.

Organization-specific custom fields from Zimyo migrate to BambooHR custom fields. We conduct type mapping during scoping: Zimyo text fields map to BambooHR Text fields, date fields to Date fields, and picklist fields to Dropdown fields. Multi-select picklists map to BambooHR's multi-select if the customer's plan supports them. Custom fields with no equivalent BambooHR field type are exported to a custom fields inventory CSV for manual placement or third-party tool integration.

Benefit plans, enrollment elections, dependents, and coverage periods from Zimyo map to BambooHR Benefits if the customer licenses that add-on. Benefit types and plan names vary by organization and require value mapping. Historical enrollment records are effective-dated and migrate with the employee's start date as the coverage start. We do not migrate benefits administration rules or deduction calculations; those are configured fresh in BambooHR Benefits.

Zimyo expense submissions, line items, category mappings, approval workflows, and reimbursement statuses do not map to a native BambooHR object. We export expense claim history as a structured CSV inventory for the customer's finance team. If BambooHR's Expenses functionality is activated via an add-on or third-party integration, the customer re-enters open claims post-migration. Approved and reimbursed claim history is preserved in CSV for audit purposes.

Timesheets, billable hours, and project-time allocations from Zimyo map to BambooHR Time Tracking when that add-on is licensed. Custom timesheet fields and approval statuses require configuration review. We validate total hours against payroll runs where applicable and flag discrepancies before import. Project-time allocations do not have a native BambooHR equivalent; we export them as a time allocation inventory CSV.