HRMS migration
Field-level mapping, validation, and rollback between HR Manager Pro and Recruit CRM & ATS. We move data and schema; workflows are rebuilt natively in Recruit CRM & ATS.
HR Manager Pro
Source
Recruit CRM & ATS
Destination
Compatibility
8 of 10
objects map 1:1 between HR Manager Pro and Recruit CRM & ATS.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Migrating from HR Manager Pro to Recruit CRM is a cross-domain move: the source is a WordPress-based internal HR plugin for managing employees, leave, and documents, while the destination is a cloud ATS and CRM built for recruitment agencies and executive search firms. The primary challenge is that HR Manager Pro's data model (Employees, Departments, Leave Balances, Documents) has no direct equivalent in Recruit CRM (Candidates, Clients, Jobs, Pipeline). We handle the extraction via CSV export from HR Manager Pro, transform each record to match Recruit CRM's Candidate schema, and load through the Recruit CRM bulk import API. We flag Leave Balances and accrual logic as non-migratable because Recruit CRM does not maintain internal HR leave tracking. Documents stored in the WordPress media library require a separate download-and-re-associate step. We do not migrate workflows, automations, or custom HR plugin configurations as code; these require manual rebuild in Recruit CRM or are not applicable to its ATS workflow model.
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 HR Manager Pro 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.
HR Manager Pro
Employee
Recruit CRM & ATS
Candidate
1:1HR Manager Pro Employee records map to Recruit CRM Candidate records. We extract the employee profile (name, email, phone, address, hire date, department, job title) from the CSV export and map each field to the corresponding Candidate property. We flag fields with no direct Candidate equivalent (emergency contact, salary band, employment type) as custom field candidates for the customer's admin to define in Recruit CRM after migration. The primary matching key is email address.
HR Manager Pro
Department
Recruit CRM & ATS
Tags or Candidate Group
1:1HR Manager Pro Department taxonomy maps to Recruit CRM Tags or Candidate Groups. Recruit CRM does not have a native Department object on Candidate records; department affiliation is expressed via tagging. We extract the department list, create corresponding tags in Recruit CRM during the load phase, and assign each Candidate the relevant tag based on the source Employee's department column. Customers with complex multi-level department hierarchies flatten to a single tag level in Recruit CRM.
HR Manager Pro
Leave Policy
Recruit CRM & ATS
Not Migratable
lossyLeave entitlement and accrual rule configuration in HR Manager Pro has no equivalent object in Recruit CRM. Recruit CRM is an ATS and recruitment CRM; it does not maintain employee leave balances, accrual schedules, carryover rules, or vesting timelines. We document the leave policy structure (policy name, accrual frequency, balance) as a written reference for the customer's admin to maintain externally or re-enter in a dedicated HR leave tool if required.
HR Manager Pro
Leave Balance
Recruit CRM & ATS
Not Migratable
1:1Current leave balance snapshots stored in HR Manager Pro's custom plugin tables do not map to any Recruit CRM object. We extract the most recent balance per employee as a static value during scoping and recommend the customer use this as a reference document for HR verification rather than attempting a live transfer. Recruit CRM has no leave tracking module where this data would land.
HR Manager Pro
Document
Recruit CRM & ATS
Candidate Attachment
1:1Employee documents (contracts, certifications, IDs) stored in the WordPress media library require a parallel download step. The CSV export contains the file path or media ID; we fetch each file from the WordPress media library, map it to the corresponding Candidate record in Recruit CRM, and upload it as an attachment. This step runs independently of the main CSV load and adds 15-30 minutes per 100 documents depending on file size. We flag any documents without a valid email-matched Candidate target in a resolution queue.
HR Manager Pro
Custom Fields
Recruit CRM & ATS
Custom Candidate Fields
lossyHR Manager Pro allows admin-defined custom fields on employee profiles that we only discover at pre-migration scan time. We include these as additional columns in the CSV export. Mapping requires reviewing the Recruit CRM field type system (text, number, date, picklist, checkbox) and creating matching custom fields on the Candidate object before the main load. If the customer adds custom fields after scoping but before migration day, we re-run the scan and update the field map.
HR Manager Pro
User or Owner
Recruit CRM & ATS
Recruit CRM User
1:1HR Manager Pro does not have a separate User object separate from Employee; the WordPress admin user who manages the plugin is a WordPress user, not an HRMS owner. We map the WordPress admin account and any additional HR Manager Pro user accounts to Recruit CRM User records by email. The customer provisions Recruit CRM users before migration and we match by email during the Candidate import so that Owner assignment is populated on each record.
HR Manager Pro
Job Posting
Recruit CRM & ATS
Job
1:1HR Manager Pro does not include job posting or requisition management in its feature set. If the customer has used the plugin to track internal job openings as employee records or notes, these do not export as a structured Job object. We do not create Jobs in Recruit CRM from unstructured HR Manager Pro data; the customer's recruitment team builds Job records directly in Recruit CRM post-migration.
HR Manager Pro
Benefits and Deductions
Recruit CRM & ATS
Not Migratable
1:1Benefits plan assignments and deduction rates exported as part of the HR Manager Pro employee CSV have no equivalent location in Recruit CRM. Recruit CRM Candidate records support custom fields but not a structured benefits enrollment object. We include benefits data as custom text fields on the Candidate record if the customer requests it, but note that Recruit CRM is not designed for benefits administration.
HR Manager Pro
Time Entries
Recruit CRM & ATS
Not Migratable
1:1The HR Manager Pro base plugin does not include time-tracking. If the customer has a third-party time-tracking addon, historical time entry data lives in a separate database table not accessible via CSV export and is outside migration scope. Recruit CRM does not provide a time-tracking module; customers needing time tracking integrate via Zapier with a dedicated time-tracking tool.
| HR Manager Pro | Recruit CRM & ATS | Compatibility | |
|---|---|---|---|
| Employee | Candidate1:1 | Fully supported | |
| Department | Tags or Candidate Group1:1 | Fully supported | |
| Leave Policy | Not Migratablelossy | Fully supported | |
| Leave Balance | Not Migratable1:1 | Fully supported | |
| Document | Candidate Attachment1:1 | Fully supported | |
| Custom Fields | Custom Candidate Fieldslossy | Mapping required | |
| User or Owner | Recruit CRM User1:1 | Fully supported | |
| Job Posting | Job1:1 | Fully supported | |
| Benefits and Deductions | Not Migratable1:1 | Mapping required | |
| Time Entries | Not Migratable1:1 | Not 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.
HR Manager Pro gotchas
No API forces reliance on CSV export scoping
Leave balance accrual logic does not export
File attachments require separate download workflow
Custom fields discovered only at scan time
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
Discovery and scoping
We audit the source HR Manager Pro instance: employee record count, department list, document volume, custom field inventory, and any leave balance or benefits data present in the plugin's database. We pair this with a Recruit CRM target definition: which plan tier (Pro, Business, Enterprise), which Candidate fields are required, and which custom fields the customer wants created. We deliver a written migration scope document listing all migratable objects, non-migratable objects with alternatives, and a field-level map for each migratable object.
Source CSV export and validation
We export the full employee dataset from HR Manager Pro via the plugin's built-in CSV export tool. We validate the export against the scoped field map: checking for missing required columns, malformed date formats, empty department rows, and non-UTF-8 encoding issues. Any validation failures are resolved in collaboration with the customer's WordPress admin before the export is accepted as migration-ready. Documents are listed in a separate export manifest with WordPress media library paths for the parallel download step.
Pre-migration Recruit CRM setup
Before loading data, we work with the customer to configure Recruit CRM: creating the custom Candidate fields matched to the source custom field inventory, defining Tags for department mapping, provisioning Recruit CRM User accounts matched by email to the source Employee records, and setting the Candidate record status values. Schema configuration happens in the Recruit CRM sandbox or trial environment first for validation before production migration.
Document download and re-association preparation
We run the parallel document download step against the WordPress media library. Each file is fetched by its media ID or path, validated for readability and size, and associated with the corresponding employee by email address lookup. Files that cannot be matched to an employee are flagged in a resolution queue. We then prepare each file for upload to Recruit CRM as a Candidate attachment.
Production migration and bulk import
We run the Candidate bulk import into Recruit CRM using the validated CSV and a Recruit CRM-compatible column mapping. We apply the department-to-tag transformation during import, set Owner assignment via email-matched User records, and preserve hire date as a custom Candidate field. Document attachments are uploaded in parallel after the Candidate base record is confirmed created. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and handoff
We freeze HR Manager Pro as the write system during cutover and run a final delta check for any records modified during the migration window. We deliver a validation report comparing source record counts to destination Candidate counts, a document migration report listing successfully attached files and any unresolved queue items, and a written inventory of non-migratable objects (leave policies, balances, benefits) with recommendations. We do not rebuild HR Manager Pro workflows or configurations in Recruit CRM; those do not map to Recruit CRM's ATS workflow model.
Platform deep dives
HR Manager Pro
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 HR Manager Pro 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
HR Manager Pro: Not applicable.
Data volume sensitivity
HR Manager Pro 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 HR Manager Pro to Recruit CRM & ATS migration scoping. Not seeing yours? Book a call.
Walk through your HR Manager Pro 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 HR Manager Pro
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.