Migrate your Mercu data
Academic HRMS platform used by Mercu Buana University in Indonesia to manage university staff records and administrative workflows.
In its favor
Why people choose Mercu
The signal that keeps Mercu on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
WhatsApp-first candidate communication — Mercu reaches frontline applicants on the channel they already use, with automatic fallback to SMS when WhatsApp is unavailable, dramatically improving response rates over email.
Built specifically for high-volume frontline hiring (retail, hospitality, logistics) — customers include Lufthansa, Guzman y Gomez, JD Sports, and Decathlon.
AI-powered interview scheduling, automated reminders, and candidate Q&A reduce no-shows and free recruiter time without requiring candidates to download an app.
Multi-channel beyond WhatsApp/SMS — also supports LINE, Kakao, and Zalo, important for hiring across Southeast Asia and Korean/Japanese markets.
Native integrations with major ATS and HRIS platforms (Workable, Dayforce, TalentLyft, and others) plus no-code connector options reduce IT effort for procurement-approved stacks.
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.
Reasons to switch
Why people leave Mercu
The recurring reasons buyers give for replacing Mercu. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Mercu fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Mercu pricing overview
Mercu offers tiered pricing scaled by hiring volume. Public materials reference tiers for 251–999 hires per year and an Enterprise tier with enhanced security, integrations, and support for 1,000+ hires per year. Exact monthly pricing is not published on third-party listings — quote required. WhatsApp Business API conversation fees from Meta are billed separately and are not bundled in Mercu's subscription.
Mid-volume
Tier 1 of 2
Custom quote
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Mercu's schedule — see our quote-based pricing →
What gets migrated
Mercu object support
Object-by-object support for Mercu migrations. Per-pair details surface during scoping.
Employees (Hired Candidates)
Mapping requiredMercu is recruitment-focused; once a candidate is hired, the employee record typically lives in the connected ATS/HRIS, not Mercu. Hired candidate exports include the application data and conversation history that supported the hire.
Candidates (Applicants)
Fully supportedCandidate records are the primary object — name, contact details, application source, AI match score, conversation history, and status export from Mercu via API or CSV. We preserve channel-of-origin (WhatsApp vs SMS vs LINE) as a custom field.
Conversations
Fully supportedTwo-way conversation history with each candidate exports with timestamps, channel, message body, and AI-generated responses flagged separately from human ones.
Interviews / Bookings
Mapping requiredScheduled interviews carry candidate, interviewer, time slot, and channel-specific reminder history. We map to destination interview objects, preserving rescheduling timestamps and no-show flags.
Job Postings
Mapping requiredJob postings are typically created in the upstream ATS and synced into Mercu via integration; the source of truth for jobs is the ATS, not Mercu. Migration scoping confirms which system holds the canonical record.
Match Scores (AI)
Mapping requiredAI-generated match scores per application are exported as numeric custom properties on the candidate record. Scoring logic is Mercu-proprietary and does not transfer; only the resulting score migrates.
Custom Fields
Mapping requiredCustom application fields (shift preferences, language, location radius) export with their field name and type and are mapped to destination custom fields during scoping.
Documents / Attachments
Mapping requiredResume files, ID documents, and other candidate-submitted attachments export as binary objects. We re-attach in the destination using the migrated candidate ID as the key.
| Object | Support | Notes |
|---|---|---|
| Employees (Hired Candidates) | Mapping required | Mercu is recruitment-focused; once a candidate is hired, the employee record typically lives in the connected ATS/HRIS, not Mercu. Hired candidate exports include the application data and conversation history that supported the hire. |
| Candidates (Applicants) | Fully supported | Candidate records are the primary object — name, contact details, application source, AI match score, conversation history, and status export from Mercu via API or CSV. We preserve channel-of-origin (WhatsApp vs SMS vs LINE) as a custom field. |
| Conversations | Fully supported | Two-way conversation history with each candidate exports with timestamps, channel, message body, and AI-generated responses flagged separately from human ones. |
| Interviews / Bookings | Mapping required | Scheduled interviews carry candidate, interviewer, time slot, and channel-specific reminder history. We map to destination interview objects, preserving rescheduling timestamps and no-show flags. |
| Job Postings | Mapping required | Job postings are typically created in the upstream ATS and synced into Mercu via integration; the source of truth for jobs is the ATS, not Mercu. Migration scoping confirms which system holds the canonical record. |
| Match Scores (AI) | Mapping required | AI-generated match scores per application are exported as numeric custom properties on the candidate record. Scoring logic is Mercu-proprietary and does not transfer; only the resulting score migrates. |
| Custom Fields | Mapping required | Custom application fields (shift preferences, language, location radius) export with their field name and type and are mapped to destination custom fields during scoping. |
| Documents / Attachments | Mapping required | Resume files, ID documents, and other candidate-submitted attachments export as binary objects. We re-attach in the destination using the migrated candidate ID as the key. |
Gotchas
What to watch for in Mercu migrations
Issues we've hit on past Mercu migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Mercu?
Where Mercu customers move next
5 destinations Mercu can migrate to.
How a Mercu migration works
Four steps, Mercu-specific
Connect
API key / OAuth (not extensively documented in public materials) into Mercu. Scopes limited to read-only on the data we move.
Map
We translate Mercu-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Mercu quirks before production.
Migrate
Full migration with Mercu rate-limit handling. Rollback available throughout.
FAQ
Mercu migration FAQ
Answers to the questions buyers ask most during Mercu migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Mercu migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Mercu.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Mercu setup and destination — written quote back within a business day.