Migrate your mploy data
Niche ATS serving small businesses with a flat-rate pricing model. Minimal public footprint, sparse reviews, and limited documentation make this an opaque migration target.
In its favor
Why people choose mploy
The signal that keeps mploy on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Affordable flat-rate pricing at $89/month attracts small businesses with straightforward hiring volumes who want ATS basics without per-seat billing complexity.
Candidate-facing job board posting and application portal provide a self-contained recruiting funnel for small teams without dedicated recruiting coordinators.
Simple, narrow feature set reduces onboarding friction for small HR teams that need to move fast without learning a complex system.
Positioned as an ATS alongside competitors like CEIPAL and Workable, appealing to buyers comparing options at the $25–$89/month range on review platforms.
Flat-rate model without per-user tiers makes budget forecasting predictable for small businesses with variable headcount.
Zero third-party reviews on G2 and Capterra make it impossible to validate product reliability, support quality, or long-term viability before committing data.
Small-market product raises concerns about vendor longevity and the risk of a forced migration if the platform sunsets without warning.
Limited public documentation means internal teams struggle to configure workflows, integrations, or custom fields without vendor support.
Absence of a visible API or developer documentation blocks automation use cases, integrations with HRIS systems, and programmatic data extraction.
Small vendor footprint limits access to skilled implementation partners, forcing customers to rely solely on vendor support for complex setups.
Reasons to switch
Why people leave mploy
The recurring reasons buyers give for replacing mploy. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where mploy 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
mploy pricing overview
mploy uses a single flat-rate pricing model at $89 per month, with no published per-user tiers or feature-differentiated plans. This simplicity contrasts with per-seat ATS pricing from competitors and may reduce cost predictability concerns, but also means no built-in upgrade path to advanced features as the team grows.
Standard
Tier 1 of 1
$89 flat rate per month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on mploy's schedule — see our quote-based pricing →
What gets migrated
mploy object support
Object-by-object support for mploy migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCandidates is the core ATS object in mploy representing job applicants. Standard fields include name, email, phone, resume, and application status. We migrate Candidates via admin-panel CSV export, mapping to the destination's equivalent object and preserving application history as we replay status changes.
Jobs
Fully supportedJobs represent open positions being recruited for. Each job contains title, department, location, description, and open/closed status. We export active and archived jobs to preserve closed requisitions for compliance auditing and reporting continuity.
Applications
Mapping requiredApplications are the join records linking Candidates to Jobs, capturing submission date, stage in pipeline, and source. Source attribution and stage names often vary between ATS systems, requiring explicit mapping during migration scoping.
Users
Mapping requiredUser accounts represent employees with access to the ATS. Role assignments (admin, recruiter, hiring manager) must be mapped to the destination's role model. Inactive users may be excluded or preserved as historical records depending on scope.
Pipelines
Mapping requiredPipelines define the hiring stages a Candidate moves through (e.g., Applied, Phone Screen, Interview, Offer). Stage names and count vary by customer configuration. We preserve the ordered stage sequence and replay timestamps for each stage transition.
Interviews
Not in this platformInterview records, including interviewer assignments, scores, and feedback, are not confirmed as a separately exportable object in mploy. Where interview data exists, we attempt to capture it as notes on the Application record, but we do not guarantee structured interview data migration.
Offers
Mapping requiredOffer records contain compensation details, start dates, and acceptance status. These are often tied to Applications. We migrate Offer fields where present and map them to the destination's equivalent offer or extended-offer object.
Custom Fields
Mapping requiredCustom fields on any object require explicit enumeration during scoping. mploy allows custom fields on Candidates and Jobs in some configurations. We export field definitions and values, then map them to destination custom fields, preserving data types and picklist values.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Candidates is the core ATS object in mploy representing job applicants. Standard fields include name, email, phone, resume, and application status. We migrate Candidates via admin-panel CSV export, mapping to the destination's equivalent object and preserving application history as we replay status changes. |
| Jobs | Fully supported | Jobs represent open positions being recruited for. Each job contains title, department, location, description, and open/closed status. We export active and archived jobs to preserve closed requisitions for compliance auditing and reporting continuity. |
| Applications | Mapping required | Applications are the join records linking Candidates to Jobs, capturing submission date, stage in pipeline, and source. Source attribution and stage names often vary between ATS systems, requiring explicit mapping during migration scoping. |
| Users | Mapping required | User accounts represent employees with access to the ATS. Role assignments (admin, recruiter, hiring manager) must be mapped to the destination's role model. Inactive users may be excluded or preserved as historical records depending on scope. |
| Pipelines | Mapping required | Pipelines define the hiring stages a Candidate moves through (e.g., Applied, Phone Screen, Interview, Offer). Stage names and count vary by customer configuration. We preserve the ordered stage sequence and replay timestamps for each stage transition. |
| Interviews | Not in this platform | Interview records, including interviewer assignments, scores, and feedback, are not confirmed as a separately exportable object in mploy. Where interview data exists, we attempt to capture it as notes on the Application record, but we do not guarantee structured interview data migration. |
| Offers | Mapping required | Offer records contain compensation details, start dates, and acceptance status. These are often tied to Applications. We migrate Offer fields where present and map them to the destination's equivalent offer or extended-offer object. |
| Custom Fields | Mapping required | Custom fields on any object require explicit enumeration during scoping. mploy allows custom fields on Candidates and Jobs in some configurations. We export field definitions and values, then map them to destination custom fields, preserving data types and picklist values. |
Gotchas
What to watch for in mploy migrations
Issues we've hit on past mploy migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API confirmed for programmatic data extraction
Zero third-party reviews create a reliability blind spot
Custom field schema is customer-specific and must be enumerated manually
Candidate document attachments require separate export handling
| Severity | Issue |
|---|---|
| High | No public API confirmed for programmatic data extraction |
| High | Zero third-party reviews create a reliability blind spot |
| Medium | Custom field schema is customer-specific and must be enumerated manually |
| Medium | Candidate document attachments require separate export handling |
Leaving mploy?
Where mploy customers move next
5 destinations mploy can migrate to.
How a mploy migration works
Four steps, mploy-specific
Connect
Not publicly documented into mploy. Scopes limited to read-only on the data we move.
Map
We translate mploy-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate mploy quirks before production.
Migrate
Full migration with mploy rate-limit handling. Rollback available throughout.
FAQ
mploy migration FAQ
Answers to the questions buyers ask most during mploy migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your mploy 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 mploy.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your mploy setup and destination — written quote back within a business day.