Migrate your Manatal data
AI-powered recruitment ATS built for small-to-mid staffing agencies and in-house HR teams, with tiered pricing that gates API access behind the top plan.
In its favor
Why people choose Manatal
The signal that keeps Manatal on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small teams and solo recruiters pick Manatal for its low entry price—$15/user/month on Professional with a 10,000-candidate database cap, sufficient for early-stage hiring operations.
Recruitment agencies choose Manatal for its built-in CRM features including client tracking, pipeline management, and placement revenue monitoring within a single platform.
In-house HR teams value the AI candidate scoring and recommendation engine, which surfaces passive candidates from the existing database based on job requirements.
The free 14-day trial with no credit card required lets small organizations validate the platform before committing to a paid subscription.
Multilingual support and a global 24/5 helpdesk attract international teams operating across multiple languages and time zones.
The API is locked behind the Enterprise Plus plan at $55/user/month, forcing teams with custom integrations or migration needs to pay for the highest tier just to access data programmatically.
Workflow automations are gated behind Enterprise tier—organizations relying heavily on automated candidate nurture sequences find Professional plan too limited without upgrading.
The built-in AI candidate matching fails to properly identify talent for complex or niche roles, pushing recruiters to manually source and filter candidates despite paying for AI features.
Navigation difficulty and a disorganized interface cause friction for daily users, especially when filtering large candidate databases with limited column customization.
Export limitations frustrate data portability—only one dataset can be exported at a time, exports are not enabled by default, and all timestamps appear in UTC with no timezone override.
Reasons to switch
Why people leave Manatal
The recurring reasons buyers give for replacing Manatal. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Manatal 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
Manatal pricing overview
Manatal charges per active user per month with annual billing discounts. Professional starts at $15/user/month with a 10,000-candidate cap, Enterprise at $35/user/month removes candidate limits and adds automations, and Enterprise Plus at $55/user/month unlocks the API and SSO. A free tier with limited features is available for evaluation. Pricing scales linearly with team size, not with data volume, making larger databases on Professional relatively economical compared to per-record competitors.
Free
Tier 1 of 4
Free
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Manatal's schedule — see our quote-based pricing →
What gets migrated
Manatal object support
Object-by-object support for Manatal migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCandidates are the primary object in Manatal. We migrate all profile fields, resume documents, tags, custom fields, stage history, and activity logs. Custom fields organized under custom categories are preserved with their category structure intact.
Jobs
Fully supportedJobs include configurable pipeline stages and assigned users. We migrate the job structure, all stage definitions, and current candidate-to-stage mappings. Note that job vacancy limits differ by plan tier.
Organizations (Clients/Departments)
Fully supportedOrganizations represent clients or internal departments. Bulk import via CSV or JSON is natively supported by Manatal. We handle deduplication logic—organizations with matching names are skipped during import.
Custom Fields (on Candidates)
Mapping requiredCustom fields are supported but require Admin access to create or modify. We preserve field names, data types, and values. Some legacy custom field structures may require remapping if field IDs have shifted between accounts.
Pipeline Stages
Fully supportedPipeline stages are defined per Job. We migrate the full stage sequence, including custom stage names and ordering. Stage-to-candidate assignments are preserved at migration time.
Activity Logs
Mapping requiredActivity logs capture user actions on candidates and jobs. We migrate the log entries with timestamps and actor attribution. Very high-volume activity logs may need chunking due to API pagination limits.
Attachments / Documents
Mapping requiredResume files and other attachments are referenced in candidate profiles. We migrate document metadata and file references. Binary file transfer depends on the source platform's export capabilities.
Users / Team Members
Mapping requiredUser accounts with roles and permissions are migrated as contact records in the destination. Manatal's internal user ID and role assignments are preserved as custom properties. SSO and User Groups are Enterprise Plus only features.
Workflow Automations
Mapping requiredWorkflow automations trigger on events such as stage transitions or candidate actions. We document automation rules for rebuild in the destination. Note: Automations are only available on Enterprise and Enterprise Plus plans.
Tags
Fully supportedTags are flat label objects applied to candidates and jobs. We migrate all tag assignments preserving the tag names across the dataset.
Recruitment CRM Data (Clients, Placements, Revenue)
Mapping requiredManatal includes CRM features for agencies tracking client relationships, placements, and commission revenue. These records are migrated as custom objects or standard CRM equivalents depending on the destination platform.
Organizations Import Deduplication
Not in this platformManatal's native organization import skips records where the organization name already exists in the database. We handle this by deduplicating source records before generating the import file to avoid silent data loss.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Candidates are the primary object in Manatal. We migrate all profile fields, resume documents, tags, custom fields, stage history, and activity logs. Custom fields organized under custom categories are preserved with their category structure intact. |
| Jobs | Fully supported | Jobs include configurable pipeline stages and assigned users. We migrate the job structure, all stage definitions, and current candidate-to-stage mappings. Note that job vacancy limits differ by plan tier. |
| Organizations (Clients/Departments) | Fully supported | Organizations represent clients or internal departments. Bulk import via CSV or JSON is natively supported by Manatal. We handle deduplication logic—organizations with matching names are skipped during import. |
| Custom Fields (on Candidates) | Mapping required | Custom fields are supported but require Admin access to create or modify. We preserve field names, data types, and values. Some legacy custom field structures may require remapping if field IDs have shifted between accounts. |
| Pipeline Stages | Fully supported | Pipeline stages are defined per Job. We migrate the full stage sequence, including custom stage names and ordering. Stage-to-candidate assignments are preserved at migration time. |
| Activity Logs | Mapping required | Activity logs capture user actions on candidates and jobs. We migrate the log entries with timestamps and actor attribution. Very high-volume activity logs may need chunking due to API pagination limits. |
| Attachments / Documents | Mapping required | Resume files and other attachments are referenced in candidate profiles. We migrate document metadata and file references. Binary file transfer depends on the source platform's export capabilities. |
| Users / Team Members | Mapping required | User accounts with roles and permissions are migrated as contact records in the destination. Manatal's internal user ID and role assignments are preserved as custom properties. SSO and User Groups are Enterprise Plus only features. |
| Workflow Automations | Mapping required | Workflow automations trigger on events such as stage transitions or candidate actions. We document automation rules for rebuild in the destination. Note: Automations are only available on Enterprise and Enterprise Plus plans. |
| Tags | Fully supported | Tags are flat label objects applied to candidates and jobs. We migrate all tag assignments preserving the tag names across the dataset. |
| Recruitment CRM Data (Clients, Placements, Revenue) | Mapping required | Manatal includes CRM features for agencies tracking client relationships, placements, and commission revenue. These records are migrated as custom objects or standard CRM equivalents depending on the destination platform. |
| Organizations Import Deduplication | Not in this platform | Manatal's native organization import skips records where the organization name already exists in the database. We handle this by deduplicating source records before generating the import file to avoid silent data loss. |
Gotchas
What to watch for in Manatal migrations
Issues we've hit on past Manatal migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API access is Enterprise Plus only
Data export not enabled by default
Organization import deduplication by name only
Workflow automations are tier-gated and use fair usage limits
Export timestamps are UTC only
| Severity | Issue |
|---|---|
| High | API access is Enterprise Plus only |
| High | Data export not enabled by default |
| Medium | Organization import deduplication by name only |
| Medium | Workflow automations are tier-gated and use fair usage limits |
| Low | Export timestamps are UTC only |
Leaving Manatal?
Where Manatal customers move next
5 destinations Manatal can migrate to.
How a Manatal migration works
Four steps, Manatal-specific
Connect
API key (Enterprise Plus only) into Manatal. Scopes limited to read-only on the data we move.
Map
We translate Manatal-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Manatal quirks before production.
Migrate
Full migration with Manatal rate-limit handling. Rollback available throughout.
FAQ
Manatal migration FAQ
Answers to the questions buyers ask most during Manatal migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Manatal 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 Manatal.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Manatal setup and destination — written quote back within a business day.