HRMS migration

Migrate from Mercu to BambooHR

Field-level mapping, validation, and rollback between Mercu and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.

Mercu logo

Mercu

Source

BambooHR

Destination

BambooHR logo

Compatibility

40%

4 of 10

objects map 1:1 between Mercu and BambooHR.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Mercu to BambooHR is a transition from a university-specific academic HRMS serving Mercu Buana University in Jakarta to a general-purpose cloud HRIS designed for small-to-mid businesses worldwide. The structural challenge is mapping Mercu's multi-field Indonesian naming convention (title, given name, middle name, surname) into BambooHR's standard first-name/last-name split, while preserving the full original display name for staff directory accuracy. We also resolve supervisor relationships from Mercu's academic hierarchy into BambooHR's manager lookup, map historical leave balances into BambooHR's Time Off module, and flag any Mercu leave types that have no direct BambooHR equivalent for manual reconciliation. Employment status transitions, department histories, and contract end dates carry over as custom fields where BambooHR's standard schema does not capture the academic context. BambooHR's native ATS (Job Openings and Applications), onboarding checklists, and performance review cycles are not migrated as templates; we deliver a written scope of these objects for the customer's admin to configure post-migration.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Mercu logo

Mercu

What's pushing teams away

  • Channel and integration scope is concentrated on frontline volume-hiring use cases — knowledge-worker or executive search teams will not find specialized features for their workflows.
  • WhatsApp Business API costs and compliance (Meta-imposed conversation fees, consent requirements) sit on top of the Mercu subscription, complicating total-cost-of-ownership calculations.
  • Smaller third-party connector marketplace than legacy ATSes — teams running on niche or in-house systems may need custom integration work.
  • Pricing is sales-led at the enterprise tier (1,000+ employees), reducing transparency for procurement teams comparing options.
  • Reliance on candidate WhatsApp availability — although SMS fallback exists, candidates without consistent mobile messaging access still drop out of automated funnels.

Choosing

BambooHR logo

BambooHR

What's pulling them in

  • Lowest friction entry point for SMBs moving off spreadsheets — intuitive interface means most teams are functional within days, not weeks.
  • Consolidation value: BambooHR merges ATS, onboarding, HR records, time-off, and payroll into a single pane of glass that employees never need to leave.
  • Volume discounts applied automatically by headcount, so pricing scales predictably as the company grows without renewal negotiations.
  • BambooHR reports most customers go live in four to six weeks, making it a realistic commitment for under-resourced HR teams.
  • Award-winning Support Heroes cited frequently in reviews — responsive human support after implementation is a differentiator.

Object mapping

How Mercu objects map to BambooHR

Each row shows how a Mercu 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.

Mercu

Employee

maps to

BambooHR

Employee

1:1
Fully supported

Mercu Employee records map to BambooHR Employee. The primary challenge is Mercu's multi-field Indonesian name format (gelar/title, nama depan/given name, nama tengah/middle name, nama belakang/surname) which we split into BambooHR's First Name and Last Name fields, with the full original concatenated name preserved in a custom employee field (e.g., Full Name Original) for staff directory accuracy. Employee ID from Mercu maps to BambooHR's Employee Number field as the dedupe key. National ID (NIK) and NIDN (lecturer identification number) map to custom fields if the customer requires them post-migration.

Mercu

Employment Details

maps to

BambooHR

Employment Details

lossy
Fully supported

Mercu's employment_type (dosen/lecturer, staff, kontrak), academic_rank (asisten ahli, lektor, lektor kepala, profesor), and functional position map to BambooHR's Employment History section as separate employment records. Each employment record in BambooHR captures job title, department, employment status, start date, and end date. We configure the employment history sequence in BambooHR so the most recent academic rank is the primary displayed title, with prior ranks preserved in the employment timeline.

Mercu

Department / Faculty

maps to

BambooHR

Department

1:1
Fully supported

Mercu's faculty and department structure (Fakultas Teknik, Fakultas Ekonomi, etc.) maps to BambooHR's Departments. We create the department hierarchy in BambooHR during the configuration phase, mapping Mercu's parent faculty relationship to BambooHR's department structure. Employees are assigned to their primary department via BambooHR's Department field, with secondary faculty affiliations recorded in a custom multi-select field.

Mercu

Employment Status

maps to

BambooHR

Employment Status

lossy
Fully supported

Mercu's employment status values (aktif/active, cuti/leave of absence, kontrak/contract, selesai/terminated) map to BambooHR's Employment Status values. We configure BambooHR's status options during setup to match the source values, with Cuti (academic leave) mapped to a custom status category that BambooHR's standard statuses do not cover natively. Terminated employees from Mercu with an exit date migrate with their termination_date field populated and status set toInactive.

Mercu

Leave Balance

maps to

BambooHR

Time Off

lossy
Fully supported

Mercu's historical leave balance records (annual leave, sick leave, cuti akademik, cuti melahirkan, cuti bersama) map to BambooHR's Time Off module. Each leave type in Mercu is matched to the closest BambooHR equivalent (Annual for cuti tahunan, Sick for cuti sakit, Personal for cuti pribadi, Bereavement for cuti duka). Any Mercu-specific leave types without a BambooHR equivalent are recorded in a custom leave type created during the configuration phase, with accrued balances entered as starting balances.

Mercu

Supervisor / Manager

maps to

BambooHR

Supervisor

1:1
Fully supported

Mercu's supervisor relationship (dosen pembimbing/lecturer supervisor, kepala bagian/head of department) maps to BambooHR's supervisor field on the Employee record. We resolve the supervisor lookup by matching the supervisor's employee number or email from Mercu to the newly created BambooHR Employee record, in dependency order: supervisors are created first so that their BambooHR IDs are available when assigning to subordinates.

Mercu

Compensation / Payroll Summary

maps to

BambooHR

Pay Runs

lossy
Fully supported

Mercu's compensation and payroll summary records (base salary, allowances, deductions by pay period) do not map directly to BambooHR Pay Runs because BambooHR Payroll is a separate paid add-on that many customers do not activate. We map the most recent compensation data to BambooHR's Compensation fields (pay rate, pay type, effective date) as a one-time snapshot, and flag the payroll data migration scope for the customer to decide whether to activate BambooHR Payroll or use an external Indonesian payroll provider.

Mercu

Contract / Agreement

maps to

BambooHR

Employee Documents

1:1
Fully supported

Mercu's employment contracts and academic agreements migrate as file attachments to BambooHR's Employee Documents module. We extract contract documents from Mercu's document storage, associate each with the correct employee record in BambooHR, and organize by type (Kontrak Kerja, SK Pengangkatan, MoA Dosen). Document content is not parsed or indexed within BambooHR; the file itself is attached and visible in the employee's document tab.

Mercu

Attendance / Presence

maps to

BambooHR

Time Tracking

lossy
Fully supported

If Mercu's attendance records are in scope, they map to BambooHR's Time Tracking add-on module. BambooHR's Time Tracking is a separate paid feature; if the customer does not activate it, attendance data is not migrated and is flagged for the customer's IT team to configure BambooHR Time Tracking or select an alternative attendance integration.

Mercu

Academic Credentials

maps to

BambooHR

Custom Employee Fields

lossy
Mapping required

Mercu's academic credential records (S1, S2, S3 degrees, professional certifications, NIDN) are mapped to BambooHR custom employee fields created during the configuration phase. We create custom fields for highest degree, institution of highest degree, NIDN (for lecturers), professional certifications, and certification expiry date. The academic credential documents themselves are attached to the employee record under Employee Documents.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Mercu logo

Mercu gotchas

High

Catalog website (mercubuana.ac.id) is Mercu Buana University, NOT the Mercu AI hiring platform

High

Mercu is a recruitment overlay, not the system of record for employees

Medium

WhatsApp Business API costs and consent rules sit outside the Mercu subscription

Medium

AI match scores and conversation history do not include the AI prompt logic

BambooHR logo

BambooHR gotchas

High

Undocumented API rate limits can trigger 503 errors

High

Per-employee pricing model requires active record count verification

Medium

API credentials must be sent on every request to avoid extra round trips

Medium

Custom field schema varies per account and requires manual inventory

Low

Document and attachment exports are not covered by standard report exports

Pair-specific challenges

  • Indonesian multi-part name formats require manual normalization

    Mercu's employee records use Indonesian naming conventions with multiple parts (title, given name, middle name, surname, possibly with panggilan/nickname). BambooHR's First Name and Last Name fields are mandatory and two-field only. We split the name by parsing the rightmost component as Last Name and all preceding components as First Name, but names without a clear surname boundary in Indonesian culture may result in awkward display in BambooHR's staff directory. We preserve the original full name in a custom field and flag records where normalization may affect the employee's official display for manual review before final import.

  • BambooHR's leave types do not cover Indonesian academic leave categories natively

    Mercu tracks leave types specific to Indonesian academic employment: cuti akademik (academic study leave), cuti melahirkan (maternity leave, distinct from standard sick leave), and cuti bersama (joint leave days declared nationally). BambooHR's standard Time Off categories (Annual, Sick, Personal, Bereavement) do not cover these without custom leave type configuration. We create custom leave types in BambooHR during the configuration phase and migrate historical accrued balances, but any active leave request workflows (approval chains, carryover rules, encashment policies) are university-specific and require manual rebuild in BambooHR.

  • BambooHR Payroll is a separate paid add-on; Indonesian payroll does not migrate without it

    Mercu's payroll records (base salary, allowances, deductions, tax calculations under Indonesian PPh 21) are tightly coupled to Indonesian tax and social security regulations. BambooHR Payroll is a separate paid module not included in the core HRIS subscription. If the customer does not activate BambooHR Payroll, historical payroll data cannot be represented in BambooHR's data model. We migrate compensation snapshots to BambooHR's pay rate fields but do not migrate payroll run history, tax deductions, or BPJS contributions.

  • Academic rank and faculty hierarchy require custom field configuration

    BambooHR has no native field for academic rank (asisten ahli, lektor, lektor kepala, profesor) or faculty affiliation beyond a generic Department field. These are core data points for Mercu Buana University's HR administration. We create custom employee fields during configuration to capture rank and faculty, but these are free-text or picklist fields with no automation triggers, approval workflows, or reporting drill-down native to BambooHR. Any rules tied to academic rank (e.g., leave entitlement by rank) require manual rebuild as BambooHR workflows.

Migration approach

Six steps for a successful Mercu to BambooHR data migration

  1. Discovery and source data audit

    We audit Mercu's data export across all modules: Employee records (with name components, NIK, NIDN, academic rank), Employment history (contract type, start date, end date, faculty, department), Leave balance history (accrued, used, remaining by type), Supervisor relationships, Compensation snapshots, and document inventory (contracts, credentials, certifications). We also assess which modules are actively used versus historically populated, identify records with missing required fields, and determine whether BambooHR Payroll will be activated at the destination, which governs payroll data scope.

  2. BambooHR account setup and custom field configuration

    We create the BambooHR account structure: departments matching Mercu's faculty hierarchy, employment status values including any custom academic statuses (e.g., Cuti Akademik), and custom employee fields for NIDN, academic rank, faculty affiliation, highest degree, and the full original name. We configure leave types including any custom Indonesian leave categories. This schema is validated in a BambooHR test environment before production data moves.

  3. Name normalization and pre-migration data cleaning

    We parse Mercu's multi-part Indonesian names, determine the surname boundary for each record, and write the normalized First Name and Last Name to a staging table. Records where the surname boundary is ambiguous or where normalization would materially change the employee's displayed name are flagged for manual review in a reconciliation sheet before migration. We also clean records with missing required fields by filling from source data where possible or flagging for HR admin to complete.

  4. Supervisor lookup resolution

    We extract all supervisor references from Mercu's Employee records and match them against the target BambooHR employee list by employee number and email. Supervisors are migrated first so their BambooHR IDs are available to satisfy the lookup constraint on subordinate records. Any supervisor with no match in the destination org is held in a reconciliation queue for the customer's HR admin to provision.

  5. Production migration in dependency order

    We run the production migration in record-dependency sequence: Departments first (no dependencies), then Employees (with SupervisorID resolved), then Employment History records, then Time Off balances (with leave type mapping applied), then Compensation snapshots, then Employee Documents (contract and credential files attached to the correct employee). Each phase emits a row-count reconciliation report comparing source count to destination count, with any discrepancies investigated before the next phase begins.

  6. Cutover, validation, and admin handoff

    We freeze Mercu write access during cutover, run a final delta migration of any records modified during the migration window, then mark BambooHR as the system of record. We deliver a migration summary report with record counts per object, any unresolved lookups, and a list of unmapped leave types or custom fields requiring post-migration configuration. We do not rebuild academic rank-based workflows, leave approval chains, or payroll run logic inside the migration scope; these are documented separately for the customer's HR admin.

Platform deep dives

Context on both ends of the pair

Mercu logo

Mercu

Source

Strengths

  • Built specifically for frontline volume hiring — concentrated on retail, hospitality, logistics, and QSR/F&B verticals.
  • Native multi-channel candidate communication: WhatsApp, SMS, LINE, Kakao, Zalo, with WhatsApp-to-SMS automatic fallback.
  • Pre-built integrations with most major ATS and HRIS platforms (Workable, Dayforce, TalentLyft, and more) plus no-code connectors.
  • AI candidate Q&A and match scoring reduce recruiter time per candidate at high application volumes.
  • Enterprise customer references include Lufthansa, Guzman y Gomez, JD Sports, and Decathlon, indicating production-scale capability.

Weaknesses

  • Concentrated on volume frontline hiring — not designed for knowledge-worker or executive search.
  • Total cost of ownership includes external WhatsApp Business API fees and Meta-imposed conversation pricing on top of the Mercu subscription.
  • Smaller integration marketplace than legacy ATSes — niche or in-house systems may require custom work.
  • Enterprise pricing is sales-led; lower-tier pricing transparency is partial.
  • AI scoring and chat logic do not export when migrating away from the platform.
BambooHR logo

BambooHR

Destination

Strengths

  • Single platform consolidating ATS, onboarding, HR records, payroll, and time-off reduces system sprawl for SMBs.
  • Fast implementation — BambooHR reports four to six weeks from kickoff to go-live for most customers.
  • Per-employee pricing with automatic volume discounts makes cost predictable as headcount grows.
  • Strong customer support reputation (Support Heroes) cited consistently across G2, Capterra, and direct testimonials.
  • Well-documented API with UTF-8 encoding, clear field types, and HTTPS-only access.

Weaknesses

  • Mobile application is significantly limited compared to the desktop experience, frustrating remote and field workers.
  • Companies above 150–200 employees frequently outgrow the platform's feature depth and customization surface.
  • Limited advanced reporting and analytics compared to enterprise HR platforms — custom report building is the ceiling.
  • PTO and profile customization are pain points — non-standard accrual policies and complex org structures require workarounds.
  • Document management and attachment handling lack the granularity of dedicated document-centric HR systems.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Mercu and BambooHR.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Mercu: Not publicly documented.

  • Data volume sensitivity

    B

    Mercu doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Mercu to BambooHR migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Mercu to BambooHR data migrations

Answers to the questions buyers ask most during Mercu to BambooHR migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Mercu to BambooHR migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Migrations under 500 employees with straightforward employment records and no historical leave carryover land between three and five weeks. Migrations above 500 employees, with multiple faculty departments, supervisor hierarchies, historical leave balance carryover, or contract document attachments, move to eight to twelve weeks. The timeline depends on the data audit findings, the number of records requiring name normalization, and whether BambooHR Payroll is activated at the destination.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Mercu.
Land in BambooHR, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day