HRMS migration

Migrate from Mercu to Recruit CRM & ATS

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

Mercu logo

Mercu

Source

Recruit CRM & ATS

Destination

Recruit CRM & ATS logo

Compatibility

73%

8 of 11

objects map 1:1 between Mercu and Recruit CRM & ATS.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Mercu to Recruit CRM is a platform-category transition from an academic HRMS serving a university in Jakarta to a recruitment agency CRM designed for staffing firms. The data models differ substantially: Mercu manages employee records, employment contracts, department affiliations, and leave balances; Recruit CRM operates a Candidate-to-Placement pipeline with Jobs, Pipelines, Clients, and activity tracking. We extract employee profiles and historical employment data from Mercu's database, transform the academic HR schema into recruitment CRM objects (candidates from employees, companies from departments, placements from employment records), and import through Recruit CRM's bulk import interface. Workflows, automations, and payroll configurations in Mercu do not migrate; we deliver a written inventory of these for your admin to rebuild in Recruit CRM. Historical timestamps and department affiliations are preserved for compliance reporting at the university.

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

Recruit CRM & ATS logo

Recruit CRM & ATS

What's pulling them in

  • Agencies choose Recruit CRM for its full customizability — pipelines, stages, and fields can be tailored to any recruitment workflow without developer involvement.
  • Small teams value the built-in CRM and ATS combined in one subscription, eliminating the need to purchase and sync separate systems.
  • The Chrome extension for one-click LinkedIn profile collection streamlines candidate sourcing and reduces manual data entry for recruiters.
  • Responsive customer support with fast issue resolution is consistently cited as a reason teams stick with the platform long-term.
  • Automation options including email sequences and workflow triggers allow recruitment agencies to reduce repetitive manual outreach tasks.

Object mapping

How Mercu objects map to Recruit CRM & ATS

Each row shows how a Mercu object lands in Recruit CRM & ATS, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Mercu

Employee Profile

maps to

Recruit CRM & ATS

Candidate

1:1
Fully supported

Mercu employee records map to Recruit CRM Candidate records. Full name, email, phone, address, and educational background fields transfer directly. Employment status (active, terminated, on leave) maps to Candidate status. Historical hire dates and employment tenure transfer as custom fields for compliance reporting.

Mercu

Department Assignment

maps to

Recruit CRM & ATS

Company or Custom Department Object

1:1
Fully supported

Mercu department affiliations map to Recruit CRM Company records representing the academic departments as organizational units. Department code, department name, and faculty or school affiliation transfer as Company custom fields. If the recruitment operation tracks clients by industry, department type maps to an industry classification on the Company record.

Mercu

Employment Contract

maps to

Recruit CRM & ATS

Placement

1:1
Fully supported

Mercu employment contracts with terms, start dates, end dates, and contract types map to Recruit CRM Placement records. Contract type (permanent, contract, part-time) maps to Placement type. Bill rate or salary fields transfer to the placement compensation section. Client company reference links the placement to the mapped Company record.

Mercu

Leave Balance

maps to

Recruit CRM & ATS

Custom Fields on Candidate

lossy
Fully supported

Mercu leave balance records (annual leave, sick leave, carry-over) transfer to custom fields on the Candidate record for audit and compliance purposes. Leave status (active entitlement, used, pending approval) is preserved in a custom leave status field. Leave balance data is read-only post-migration as leave tracking typically remains in the HR system.

Mercu

Position or Job Title

maps to

Recruit CRM & ATS

Job Title or Custom Field

1:1
Fully supported

Mercu position and job title assignments map to Candidate custom fields in Recruit CRM. Academic titles (lecturer, professor, assistant) and staff role classifications transfer as a picklist field for candidate qualification matching. Current position maps to a primary job title field on the Candidate record.

Mercu

Organizational Hierarchy

maps to

Recruit CRM & ATS

Company Hierarchy or Division

1:1
Fully supported

Mercu's organizational hierarchy with faculty, school, and department levels maps to a hierarchical Company structure in Recruit CRM. Parent department assignments establish the reporting relationship. The hierarchy is used for department-level reporting in Recruit CRM's dashboard if enabled.

Mercu

Employment Status

maps to

Recruit CRM & ATS

Candidate Status

lossy
Fully supported

Mercu employment status values (active, suspended, terminated, retired) map to Recruit CRM Candidate status options. Active employees map to Active candidates. Terminated or retired employees map to Archived or Inactive status based on the customer's retention policy for historical records.

Mercu

Contact Information

maps to

Recruit CRM & ATS

Contact

1:1
Fully supported

Mercu employee contact records (emergency contacts, secondary emails, phone numbers) map to Recruit CRM Contact records linked to the corresponding Candidate. Emergency contact name and relationship map as Contact custom fields. The primary candidate contact serves as the main candidate record.

Mercu

Document Attachments

maps to

Recruit CRM & ATS

Documents on Candidate or Placement

1:1
Fully supported

Mercu document attachments (CVs, contracts, certificates, ID copies) migrate to Recruit CRM Document records linked to the corresponding Candidate or Placement. File naming convention preserves the original document type identifier. Contract PDFs attach to the Placement record; CVs and certificates attach to the Candidate record.

Mercu

Historical Employment Record

maps to

Recruit CRM & ATS

Placement History Custom Field

lossy
Fully supported

Mercu historical employment records (previous positions, department transfers, tenure history) map to custom fields or a Placement history section on the Candidate record. Each historical position creates a separate entry with dates, department, and role. The most recent Mercu employment record serves as the current placement in Recruit CRM.

Mercu

User or Owner

maps to

Recruit CRM & ATS

User

1:1
Fully supported

Mercu user accounts who are record owners or administrators map to Recruit CRM User accounts. User email serves as the matching key. Inactive Mercu users map to Recruit CRM users with inactive status pending admin activation decisions.

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

Recruit CRM & ATS logo

Recruit CRM & ATS gotchas

High

API rate limits are license-scaled and can throttle bulk migration

Medium

Custom field schemas vary per organization and require field-level mapping

Medium

Files and email attachments require separate extraction and re-upload

Low

Email sequences and automation logic do not transfer between platforms

Pair-specific challenges

  • Academic HRMS to recruitment CRM schema has no direct object mapping

    Mercu's employee record schema (employment contracts, leave balances, department affiliations) does not map directly to Recruit CRM's candidate pipeline model. We design the transformation during scoping: employees become candidates, departments become companies, employment contracts become placements, and leave balances become custom fields. Skipping this design step results in flat record imports with no relationship structure in Recruit CRM. The customer must define how they want employment tenure, academic title, and leave entitlements to appear on candidate profiles.

  • Leave balance and payroll data does not belong in a recruitment CRM

    Mercu's leave balance tracking and payroll-related records are HRMS data that has no functional equivalent in Recruit CRM. We migrate leave balances as custom fields on the Candidate record for audit and compliance reference, but Recruit CRM does not support leave approval workflows or entitlement calculations. If the customer needs ongoing leave tracking, that remains in Mercu or a separate HR system post-migration. We flag these records explicitly during scoping so the customer decides what historical data to preserve versus archive.

  • Mercu's export format may require data cleansing before import

    Academic HRMS platforms often store employee data with inconsistent formatting (mixed date formats, incomplete address fields, duplicate emergency contact entries). We audit the Mercu export before import, standardize formats, remove duplicates, and flag records with missing required fields for the customer's admin to complete. Faye Digital's CRM migration research notes that dirty data multiplies during migration if not cleansed beforehand; we treat data quality assessment as a separate phase before bulk import.

  • Workflows, approval chains, and payroll automations do not migrate

    Mercu's HR workflows (leave approval chains, contract renewal notifications, onboarding checklists) are not transferable to Recruit CRM's workflow model. Recruit CRM workflows operate on candidate pipeline stages and placement milestones, not HR employment statuses. We deliver a written inventory of every active Mercu workflow with its trigger, conditions, and actions for the customer's admin to rebuild in Recruit CRM. Payroll configurations and salary-related automations do not migrate at all.

Migration approach

Six steps for a successful Mercu to Recruit CRM & ATS data migration

  1. Source data audit and export

    We extract employee profiles, department assignments, employment contracts, leave balances, position records, and document attachments from Mercu's database or export interface. We assess data completeness, identify inconsistent formats, flag duplicate records, and document the Mercu schema including any custom fields or non-standard data structures. The audit output is a data quality report and a written Mercu object inventory that forms the basis of the Recruit CRM schema design.

  2. Schema design and object mapping

    We design the destination schema in Recruit CRM based on the customer's operational goals. This includes creating custom fields on Candidate (academic title, employment tenure, leave status), configuring Company records for department mapping, designing the Placement record structure for employment contract data, and setting up any custom objects required for historical employment records. The mapping document specifies every Mercu field, its Recruit CRM destination, the transformation rule, and any validation requirements.

  3. Data cleansing and transformation

    We standardize Mercu data formats (date formats, phone numbers, address fields), deduplicate records, and resolve incomplete fields. We apply the object mapping rules in a staging environment, transforming employee records into candidate records, department affiliations into company relationships, and employment contracts into placement entries. The transformation output is a set of CSV files or Recruit CRM-compatible import packages ready for bulk upload.

  4. Sandbox import and reconciliation

    We run a full import into a Recruit CRM sandbox environment to validate the mapping, test record relationships, and confirm that custom fields render correctly. The customer's team spot-checks candidate profiles, placement records, and company entries against the Mercu source data. We reconcile record counts and field-level accuracy before committing to production import. Any mapping corrections happen in this phase.

  5. Production migration and delta sync

    We run the production migration in record dependency order: Companies (from departments) first, then Candidates (from employees), then Placements (from employment contracts), then custom fields and documents. We freeze Mercu writes during cutover and run a final delta sync of any records modified during the migration window. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and workflow inventory handoff

    We enable Recruit CRM as the system of record after confirming record counts match across all object types. We deliver the workflow and automation inventory document listing every Mercu workflow, approval chain, and payroll automation that requires rebuild in Recruit CRM. We support a one-week hypercare window for reconciliation issues. We do not rebuild Mercu workflows as Recruit CRM automations inside the migration scope.

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.
Recruit CRM & ATS logo

Recruit CRM & ATS

Destination

Strengths

  • Fully customizable pipelines, stages, and fields without requiring developer involvement
  • Combines recruitment CRM and ATS in one subscription for staffing agencies and small teams
  • Built-in email sequences and automation reduce manual outreach work
  • Chrome extension enables one-click LinkedIn profile collection directly into the CRM
  • Responsive customer support cited across multiple reviews with fast resolution times

Weaknesses

  • Several features are gated as paid add-ons rather than included in the base subscription
  • Email functionality has been reported as unreliable by multiple users
  • Interface occasionally lags during high-activity periods in large pipelines
  • Pricing is considered higher than comparable recruitment CRMs by some customers
  • Limited native reporting — users request pre-made report exports rather than manual data pulls

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 Recruit CRM & ATS.

  • 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 Recruit CRM & ATS 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 Recruit CRM & ATS data migrations

Answers to the questions buyers ask most during Mercu to Recruit CRM & ATS migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for organizations under 5,000 employee records with straightforward field mapping and no complex historical employment data. Migrations with employment contract history, leave balance carryover, department-to-company mapping complexity, or extensive document attachments move to seven to ten weeks because of data cleansing scope and reconciliation time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Mercu.
Land in Recruit CRM & ATS, 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