Migrate from Savvy HRMS to BambooHR

Savvy HRMS Employee records (name, date of birth, contact details, PAN, blood group, emergency contact, marital status) map directly to BambooHR Employee fields via BambooHR REST API. We extract personal info, profile photo if stored, and emergency contact details. BambooHR standard fields cover the core employee schema; any Savvy HRMS custom employee properties require explicit custom field provisioning in BambooHR before import. We resolve duplicate employees by email address as the dedupe key.

Savvy HRMS stores employees within a company context but does not have a standalone Company/Account object equivalent. BambooHR has a Company field on the employee record and a Departments feature for hierarchical org structure. We extract the top-level organization name from Savvy HRMS, provision it as the BambooHR Company, and map Savvy HRMS departments into BambooHR Department records as the organizational hierarchy. Employees without a department assignment receive the root company as their default.

Savvy HRVS stores job history as separate entries (joining date, promotion, transfer, role change, location change) tied to the employee. BambooHR maintains a single Employment Info section with a Job History tab for historical entries. The most recent Savvy HRMS job entry becomes the active record in BambooHR Employment Info; prior entries load as historical Job History records with job title, department, employment type, and effective date. Employment type (full-time, part-time, contract) maps to BambooHR's employmentStatus where available and to a custom field where the mapping requires it.

Savvy HRMS salary components (basic, HRA, conveyance, medical, bonus, variable pay) map to BambooHR Compensation entries with pay rate, frequency, and effective date. Each Savvy HRMS salary component becomes a separate Compensation entry in BambooHR because BambooHR Compensation stores one component per record. Tax withholding codes from Savvy HRMS cannot map to BambooHR tax fields without manual configuration; we flag this for the customer's admin during cut-over. BambooHR Compensation Management (an add-on) provides benchmarking and planning on top of migrated compensation history.

Each Savvy HRMS leave type (earned leave, casual leave, sick leave, maternity, paternity, loss of pay) maps to a separate BambooHR Time-Off Policy. BambooHR supports annual, monthly, and custom accrual methods; we match Savvy HRMS accrual logic to the closest BambooHR equivalent and configure carry-forward rules where supported. Current leave balances at the agreed migration cut-off date load as adjustment entries in BambooHR. We flag any Savvy HRMS leave types that do not map to BambooHR Time-Off categories for the customer's review. Leave encashment and comp-off tracking require custom field provisioning.

Savvy HRMS attendance data includes clock-in/clock-out timestamps, overtime hours, grace period adjustments, and device-based capture. BambooHR does not natively store raw attendance rows but provides time tracking and reporting. We export Savvy HRMS attendance records as time entries in BambooHR, mapping regular attendance to standard time entries and flagging overtime as a separate entry type. We preserve raw timestamp data in BambooHR time entry notes or custom fields if provisioned. Attendance rule logic (grace period, late arrival policy) does not migrate; we document the current Savvy HRMS rules for manual rebuild in BambooHR Time Tracking settings.

Savvy HRMS payroll run records (earnings, deductions, net pay, pay period) are exported as a structured reference archive because BambooHR does not natively support Indian statutory payroll (PF, ESI, professional tax). We preserve payroll run data in a CSV archive with payslip metadata for audit continuity. We do not replicate the actual filing or statutory calculation logic, which is Savvy HRMS-specific. Customers requiring Indian statutory filing post-migration should plan a parallel payroll provider (RazorpayX, Keka, or equivalent); we can recommend integration paths during scoping.

Savvy HRMS review cycles, competency ratings, KRA scores, and 360-degree feedback entries migrate as BambooHR Performance Review records. Each Savvy HRMS appraisal cycle becomes a BambooHR review cycle; individual ratings, competency scores, and KRA fields that have no direct BambooHR equivalent require custom field provisioning. Self-review, manager review, and peer review stages from Savvy HRMS map to the corresponding review section in BambooHR. Goals and OKRs from Savvy HRMS are enumerated separately for the customer's admin to recreate in BambooHR Goals.

Savvy HRMS Recruitment module stores candidate profiles, application stages, interview scores, and offer details. BambooHR ATS manages candidates within its applicant tracking pipeline. We export candidate profiles and stage history from Savvy HRMS and map to BambooHR ATS pipeline stages, preserving the stage progression as notes on the candidate record. Active job postings do not migrate; we provide a structured form template for the customer's admin to recreate postings in BambooHR ATS. This mapping applies only to organizations with the Recruitment module active; we confirm during scoping.

Organizations frequently add custom properties to standard Savvy HRMS objects (Employee, Leave, Attendance, Payroll). We enumerate all custom fields during scoping by reviewing admin exports and schema exports, then provision matching custom fields in BambooHR before any data import. Any Savvy HRMS custom fields without a BambooHR equivalent are listed in a separate exceptions document for the customer's admin to decide on handling. Custom object types (Contract Labor, L&D records) map to BambooHR Employee Custom Fields or to a separate reference table depending on data type and cardinality.

Savvy HRMS Contract Labor entries (contract worker name, contract dates, billing rate, allocation details) exist as a separate object in Savvy HRMS. BambooHR does not have a native contract labor object. We map active contract workers to BambooHR Employee records with employmentStatus set to Contractor, storing billing rate and contract end date in provisioned custom fields. Expired contract workers are exported as a reference archive. We confirm during scoping whether the customer needs active contractor records migrated or archived only.