HRMS migration
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
Source
Recruit CRM & ATS
Destination
Compatibility
8 of 11
objects map 1:1 between Mercu and Recruit CRM & ATS.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Recruit CRM & ATS
Candidate
1:1Mercu 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
Recruit CRM & ATS
Company or Custom Department Object
1:1Mercu 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
Recruit CRM & ATS
Placement
1:1Mercu 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
Recruit CRM & ATS
Custom Fields on Candidate
lossyMercu 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
Recruit CRM & ATS
Job Title or Custom Field
1:1Mercu 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
Recruit CRM & ATS
Company Hierarchy or Division
1:1Mercu'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
Recruit CRM & ATS
Candidate Status
lossyMercu 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
Recruit CRM & ATS
Contact
1:1Mercu 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
Recruit CRM & ATS
Documents on Candidate or Placement
1:1Mercu 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
Recruit CRM & ATS
Placement History Custom Field
lossyMercu 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
Recruit CRM & ATS
User
1:1Mercu 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.
| Mercu | Recruit CRM & ATS | Compatibility | |
|---|---|---|---|
| Employee Profile | Candidate1:1 | Fully supported | |
| Department Assignment | Company or Custom Department Object1:1 | Fully supported | |
| Employment Contract | Placement1:1 | Fully supported | |
| Leave Balance | Custom Fields on Candidatelossy | Fully supported | |
| Position or Job Title | Job Title or Custom Field1:1 | Fully supported | |
| Organizational Hierarchy | Company Hierarchy or Division1:1 | Fully supported | |
| Employment Status | Candidate Statuslossy | Fully supported | |
| Contact Information | Contact1:1 | Fully supported | |
| Document Attachments | Documents on Candidate or Placement1:1 | Fully supported | |
| Historical Employment Record | Placement History Custom Fieldlossy | Fully supported | |
| User or Owner | User1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Catalog website (mercubuana.ac.id) is Mercu Buana University, NOT the Mercu AI hiring platform
Mercu is a recruitment overlay, not the system of record for employees
WhatsApp Business API costs and consent rules sit outside the Mercu subscription
AI match scores and conversation history do not include the AI prompt logic
Recruit CRM & ATS gotchas
API rate limits are license-scaled and can throttle bulk migration
Custom field schemas vary per organization and require field-level mapping
Files and email attachments require separate extraction and re-upload
Email sequences and automation logic do not transfer between platforms
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Mercu
Source
Strengths
Weaknesses
Recruit CRM & ATS
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Mercu and Recruit CRM & ATS.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Mercu: Not publicly documented.
Data volume sensitivity
Mercu doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Mercu to Recruit CRM & ATS migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Mercu
Other ways to arrive at Recruit CRM & ATS
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.