HRMS migration

Migrate from Mercu to Crelate

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

Mercu logo

Mercu

Source

Crelate

Destination

Crelate logo

Compatibility

67%

8 of 12

objects map 1:1 between Mercu and Crelate.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Mercu Buana University's HRMS to Crelate is an atypical migration pairing because Mercu manages university staff records (employment contracts, department assignments, leave balances, academic titles) while Crelate is a talent acquisition and recruiting CRM built for agencies and staffing firms. The migration is not a like-for-like schema copy. We treat Mercu employee profiles as Crelate Contacts, Mercu departments as Crelate Companies, and Mercu's employment contract and leave balance records as Crelate Custom Objects or linked documents. The key complexity is that Crelate's native data model assumes a recruiting pipeline with job orders, candidates, and placements; university staff do not follow that pattern. We resolve this by designing a Crelate schema that uses Contacts and Companies for the organizational hierarchy, custom fields for employment metadata (contract type, tenure, academic rank), and a separate Custom Object for leave balances that links back to the Contact record. Workflows, approval chains, and payroll configurations from Mercu do not migrate; we deliver a written inventory of Mercu's administrative workflows for the university's HR team to configure in Crelate or document in a separate HRMS implementation plan.

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

Crelate logo

Crelate

What's pulling them in

  • Affordable per-seat pricing with transparent tiers makes Crelate accessible for small-to-mid staffing firms evaluating ATS platforms for the first time.
  • Fast implementation reported by customers—some describe getting live in a matter of minutes with support team assistance.
  • Unified ATS + CRM in a single product eliminates the need to buy and synchronize separate recruiting and sales tools.
  • Flexible custom fields across Contacts, Companies, and Opportunities allow recruiting teams to capture firm-specific data without developer involvement.
  • Positive reviews highlight the product's intuitive interface and functional breadth for teams that need recruiting workflows without enterprise overhead.

Object mapping

How Mercu objects map to Crelate

Each row shows how a Mercu object lands in Crelate, 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

Crelate

Contact

1:1
Fully supported

Mercu employee profiles map to Crelate Contact records. The Mercu employee ID becomes a custom Crelate field mercu_employee_id__c for audit and cross-reference. Academic title, employment status, national ID (NIK for Indonesian employees), and tax number map to Crelate custom text fields created during schema setup. Name, email, phone, and address fields migrate directly using Crelate's standard Contact field API names.

Mercu

Department

maps to

Crelate

Company

1:1
Fully supported

Mercu departments map to Crelate Company records representing organizational units (faculties, divisions, administrative offices). Department name becomes Company name, department code becomes a custom field mercu_dept_code__c, and headcount metadata migrates to custom fields. This mapping supports activity logging against departments as Company records rather than flat lookup tables.

Mercu

Employment Contract

maps to

Crelate

Custom Object + Document

1:1
Fully supported

Mercu employment contracts (contract type, start date, end date, salary grade, renewal status) map to a Crelate Custom Object named Employment_Contract__c linked to the Contact record via a lookup field. The contract PDF or scanned document migrates as a ContentDocument attached to the Employment_Contract__c record via ContentDocumentLink. Contract type (permanent, temporary, honorary) becomes a picklist field on the Custom Object.

Mercu

Leave Balance

maps to

Crelate

Custom Object

1:1
Fully supported

Mercu leave balance records (annual leave, sick leave, academic leave) map to a Crelate Custom Object named Leave_Balance__c linked to the Contact. Fields include leave_type (picklist), year (integer), balance_days (decimal), used_days (decimal), and carried_forward (decimal). We migrate the most recent three years of leave history to avoid inflating the Crelate data volume while preserving sufficient audit trail.

Mercu

Position / Job Title

maps to

Crelate

Custom Field on Contact

lossy
Fully supported

Mercu position titles (Dosen Tetap, Dosen Tamu, Staff Administrasi, etc.) map to a Crelate custom picklist field mercu_position_type__c on Contact. The position description field migrates to a custom long-text field mercu_position_desc__c. This approach avoids creating a separate Custom Object and keeps position data directly on the Contact record for reporting.

Mercu

Salary Grade

maps to

Crelate

Custom Field on Contact

lossy
Fully supported

Mercu salary grade and step information migrates to a Crelate custom field mercu_salary_grade__c (text). Annual salary may optionally map to mercu_annual_salary__c (currency) if disclosed and if the university's data governance policy permits storing compensation data in Crelate. We flag this field for the university's data steward to confirm before import.

Mercu

Academic Credentials

maps to

Crelate

Custom Field on Contact

lossy
Fully supported

Mercu academic credential fields (highest degree, institution, field of study) migrate to Crelate custom text fields mercu_highest_degree__c and mercu_degree_institution__c on Contact. This is a configuration mapping rather than a separate object because credentials are an attribute of the employee Contact rather than a standalone entity.

Mercu

Emergency Contact

maps to

Crelate

Custom Object

1:1
Fully supported

Mercu emergency contact records map to a Crelate Custom Object named Emergency_Contact__c linked to the primary Contact. Fields include emergency_contact_name, emergency_contact_phone, emergency_contact_relationship (picklist). We store the emergency contact as a separate object rather than flattening it into Contact fields because Crelate's standard Contact model does not have a native emergency contact section.

Mercu

Bank Account

maps to

Crelate

Custom Field (flagged)

lossy
Fully supported

Mercu bank account information (bank name, account number) migrates to Crelate custom fields mercu_bank_name__c and mercu_bank_account__c on Contact with encrypted field type where Crelate supports it. This field is flagged as sensitive PII requiring the university's confirmation of data handling policy before import, and we recommend the university's IT team review Crelate's data encryption posture for banking data.

Mercu

Document Attachment

maps to

Crelate

ContentDocument + ContentDocumentLink

1:1
Fully supported

Mercu document attachments (contract PDFs, ID scans, academic certificates) migrate to Salesforce-style ContentDocument records with ContentDocumentLink associations to the parent Contact record. We batch document uploads separately from record data to avoid timeout errors, using Crelate's API attachment endpoint with file chunking for documents over 10 MB.

Mercu

Employee Dependent

maps to

Crelate

Custom Object

1:1
Fully supported

Mercu dependent records (spouse, children) map to a Crelate Custom Object named Dependent__c linked to the primary Contact. Fields include dependent_name, dependent_relationship (picklist), dependent_dob (date), and dependent_id_number (text). This supports HR reporting requirements for benefits administration that do not map to Crelate's standard Contact model.

Mercu

Training Record

maps to

Crelate

Custom Object

1:1
Fully supported

Mercu training and certification records map to a Crelate Custom Object named Training_Record__c linked to Contact. Fields include training_name, training_provider, training_date, expiry_date, and certification_status. This supports academic staff development tracking that Crelate's native recruiting model does not cover and would otherwise be lost in migration.

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

Crelate logo

Crelate gotchas

High

120 req/min API rate limit throttles bulk migrations

High

20 custom field per-entity cap forces data model decisions

Medium

15,000-record export ceiling on single operations

Medium

Sequences and automation workflows do not migrate

Low

API key is a querystring parameter, not a header

Pair-specific challenges

  • Crelate is a recruiting ATS, not a full HRMS

    Mercu manages a complete university staff lifecycle (employment, contracts, leave, payroll, academic rank progression) that Crelate's native object model does not support. Crelate's standard schema covers Contacts, Companies, Candidates, Jobs, and Placements for recruiting workflows. We map Mercu's employee, contract, and leave data to Crelate Custom Objects with Contact lookups, but Crelate does not have native payroll, benefits enrollment, or HR approval chain features. The university must determine whether Crelate is the destination for long-term HR administration or solely for recruiting operations, and we design the schema accordingly. Workflows, payroll configurations, and HR approval chains from Mercu do not migrate to Crelate.

  • Crelate's per-user pricing requires minimum 5 seats

    Crelate Business plan is $119/user/month billed annually with a 5-seat minimum, setting the floor at $595/month or $7,140/year before add-ons. Crelate's pricing page confirms no free trial and annual billing only with auto-renewal. The university should confirm the number of HR and recruiting staff who will actively use Crelate before committing, as smaller teams may find the per-user floor expensive relative to the number of active recruiters. Data enrichment ($600+/year), premium parsing, and advanced training are additional costs not included in the base plan.

  • Custom Objects require Business Plus or Enterprise tier

    Crelate's Business plan includes CRM, ATS, Analytics, and custom fields on Core Records, but advanced customization including Custom Objects may be gated to Business Plus or Enterprise. We confirm the required tier during discovery by counting the number of Custom Objects needed (Employment_Contract__c, Leave_Balance__c, Dependent__c, Training_Record__c, Emergency_Contact__c) and recommend the appropriate Crelate plan. If the university selects the Business plan, we reduce scope to custom fields only and store complex multi-record data as JSON blobs in long-text fields, which we do not recommend for audit-critical records.

  • Document attachments require separate batch processing

    Mercu's document attachments (contract PDFs, ID scans, academic certificates) do not migrate through Crelate's standard CSV field mapping. We handle document migration as a separate batch using Crelate's API attachment endpoints with file chunking for documents over 10 MB and ContentDocumentLink creation to associate each file with the parent Contact record. This step runs after the primary Contact import to ensure the Contact IDs exist before linking. Without this separate step, document attachments are dropped or require manual re-upload post-migration.

  • Crelate does not support hierarchical Company nesting out of the box

    Mercu's department structure includes multi-level hierarchies (university > faculty > department > program). Crelate's Company object does not natively support hierarchical parent-child nesting the way a financial or HR system would. We handle this by storing the top-level faculty as the Company name and using a custom field mercu_parent_dept__c to track the parent department reference. This flattens the hierarchy into a lookup field rather than a native tree structure. If the university requires strict hierarchical reporting by organizational unit, Crelate may require a custom app or a separate organizational chart tool.

Migration approach

Six steps for a successful Mercu to Crelate data migration

  1. Discovery and data inventory

    We audit the Mercu Buana University HRMS database to inventory all employee records, department entities, contract documents, leave balance records, dependent information, and training history. We extract a complete record count per object type, identify any fields with null or incomplete data, and document the Mercu field names and data types for mapping. We simultaneously confirm the Crelate subscription tier (Business, Business Plus, or Enterprise) and verify which features (Custom Objects, custom fields, advanced automation) are available at the chosen tier.

  2. Schema design and Crelate configuration

    We design the destination Crelate schema based on the discovery output. This includes creating all required custom fields on Contact (position type, academic rank, salary grade, bank details, etc.), provisioning Custom Objects (Employment_Contract__c, Leave_Balance__c, Dependent__c, Training_Record__c, Emergency_Contact__c) with lookup relationships to Contact, and configuring picklist values for contract type, leave type, relationship type, and academic degree. We deploy schema changes to Crelate via the API before any data import begins.

  3. Department-to-Company mapping and Company creation

    We extract Mercu department records and import them as Crelate Company records in a first pass, before any Contact import. Department name maps to Company name, department code maps to mercu_dept_code__c, and a parent department reference maps to mercu_parent_dept__c. Company IDs are captured and stored in a lookup table for use during the Contact import phase. This ordering is required because Crelate's Contact.CompanyId field must be satisfied at the time of Contact insert.

  4. Contact import with employee metadata

    We import Mercu employee profiles as Crelate Contact records in a second pass. We map name, email, phone, and address fields to Crelate standard fields and all employment metadata (position type, academic rank, salary grade, tenure start date, employee ID) to custom fields on Contact. We resolve the department lookup by matching the Mercu department code to the Crelate Company record created in the previous step and populate Contact.CompanyId. Records with missing required fields (no email, no name) are flagged in a reconciliation report for the university's HR team to resolve before proceeding.

  5. Custom Object and document batch import

    We import Employment_Contract__c, Leave_Balance__c, Dependent__c, Training_Record__c, and Emergency_Contact__c records in dependency order, resolving the Contact lookup by matching mercu_employee_id__c to the Crelate Contact ID. Document attachments (contract PDFs, ID scans) are uploaded separately as ContentDocument records and linked to the parent Contact via ContentDocumentLink. Each batch emits a row-count reconciliation report. We flag any orphaned records (e.g., a dependent record pointing to a Contact that failed import) for manual resolution.

  6. Validation, cutover, and workflow inventory delivery

    We run a reconciliation check comparing Mercu source record counts against Crelate destination record counts for each object. The university's HR team spot-checks 25-50 random Contact and Custom Object records against the Mercu source data and signs off the validation report. We freeze Mercu writes during the cutover window, run a final delta import of any records modified during migration, and enable Crelate as the system of record. We deliver a written inventory of Mercu administrative workflows and approval chains that require manual rebuild in Crelate or a separate HRMS implementation.

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.
Crelate logo

Crelate

Destination

Strengths

  • Unified ATS and CRM in a single platform reduces data synchronization overhead for recruiting teams.
  • Fast setup with guided implementation reported as a significant time saver for small teams.
  • Transparent per-seat pricing without surprise fees at the base tier.
  • Flexible custom field configuration across core objects without developer dependency.
  • Export capability supports up to 15,000 records per operation for Contacts, Companies, and Opportunities.

Weaknesses

  • API rate limit of 120 requests per minute restricts bulk migration throughput.
  • Custom field cap of 20 per entity requires field consolidation for complex recruiting schemas.
  • All advanced features (Activities, Activity Forms, Core Record Field customization) are tier-gated add-ons.
  • Customer service responsiveness receives consistent negative feedback in reviews.
  • Resume parsing quality trails competitors and generates support requests.

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 Crelate.

  • 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 Crelate 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 Crelate data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Migrations under 1,000 employee records with straightforward field mapping and no document attachments complete in two to four weeks. Migrations with employment contract documents, multi-tier department hierarchies, leave balance Custom Objects with three-year history, dependent records, or training history migrate into five to eight weeks because of document extraction time, Custom Object schema design, and the validation cycles required before cutover. The Crelate 1-3 week migration timeline cited on crelate.com applies to ATS-to-ATS migrations with standard field mapping and does not account for the custom schema design required when migrating from a university HRMS to a recruiting ATS.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Mercu.
Land in Crelate, 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