HRMS migration
Field-level mapping, validation, and rollback between Vacancy Filler and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Vacancy Filler
Source
Zoho Recruit
Destination
Compatibility
10 of 12
objects map 1:1 between Vacancy Filler and Zoho Recruit.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Vacancy Filler to Zoho Recruit addresses two structural pain points: opaque, sales-quote-only pricing and limited platform independence following the 2021 Acendre acquisition. Zoho Recruit publishes tiered pricing ($0 Free, $25/user/month Standard, $45/user/month Enterprise) with a 15-day free trial, making budget forecasting straightforward. The migration is technically constrained by Vacancy Filler's absence of a documented public API, which requires us to negotiate a database export directly with Acendre or proceed via structured screen-scraped extracts. We map Vacancies to Job Openings as the parent record, custom application questions to Zoho Recruit custom fields on the Candidates module, and incomplete onboarding records with a completion-percentage flag. We do not migrate workflows, agency preferred-supplier-list configurations, or report definitions; we deliver a written inventory of these for the customer's admin to rebuild in Zoho Recruit's visual pipeline builder.
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 Vacancy Filler object lands in Zoho Recruit, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Vacancy Filler
Vacancy
Zoho Recruit
Job Opening
1:1Vacancy records are the primary parent object in Vacancy Filler. We map Vacancy title, department, location, salary range, employment type, and status to Zoho Recruit Job Opening fields. Posting dates migrate as Opening Date and Target Date. The Vacancy status (Active, Closed, Draft) maps to the Job Opening status picklist. Vacancies with a status of Archived in Vacancy Filler are loaded as Closed Job Openings in Zoho Recruit with an isInative flag. Job Opening is the parent record for all subsequent Candidate and Interview imports.
Vacancy Filler
Candidate
Zoho Recruit
Candidate
1:1Candidate profiles from Vacancy Filler map to Zoho Recruit Candidates with all standard contact fields (First Name, Last Name, Email, Phone, Mobile, Current Company, Current Job Title). Zoho Recruit requires Last Name as a mandatory field; any Candidate record without a Last Name value in Vacancy Filler is flagged with Last Name set to 'Not Provided' per Zoho Recruit's import requirement. CV and resume attachments migrate as file attachments linked to the Candidate record. Candidates who appear in multiple Applications carry a single consolidated Candidate record in Zoho Recruit.
Vacancy Filler
Application
Zoho Recruit
Candidate (Job Applied section)
1:manyVacancy Filler Applications are the join record between a Candidate and a Vacancy, carrying pipeline stage, screening scores, and notes. In Zoho Recruit, the application relationship is represented by the Candidate's association to a Job Opening with a stage value. We extract the Vacancy-Candidate pair, the stage label, any screening score, and notes, then load them as a Candidate-Job Opening association with the stage set to the matching Zoho Recruit pipeline stage. Vacancy Filler stage labels are mapped to Zoho Recruit stage names during the pre-migration schema review.
Vacancy Filler
Hiring Manager / User
Zoho Recruit
User
1:1Vacancy Filler user accounts (Hiring Managers, Recruiters, Admins) export with name, email, role, and team assignment. We resolve each Vacancy Filler user by email against the Zoho Recruit User table. Permissions are not portable between systems and require manual reconstruction in Zoho Recruit's Setup > Users & Control. We deliver a User mapping table listing each Vacancy Filler role and the recommended Zoho Recruit role (Standard Recruiter, Hiring Manager, Admin). Users with existing separate Zoho Recruit accounts must close those accounts before import per Zoho Recruit's migration documentation.
Vacancy Filler
Talent Pool
Zoho Recruit
Candidate (Tagged List)
1:1Longlisted candidates stored in Vacancy Filler Talent Pools carry a distinct status from active applicants. We export pool name, associated candidates, and any pool notes. Zoho Recruit does not have a native Talent Pool object, so we replicate the grouping by creating Zoho Recruit Candidate Tags for each pool name and attaching all pool members. This preserves the talent pool segmentation while using Zoho Recruit's native tagging feature.
Vacancy Filler
Interview Schedule
Zoho Recruit
Interview
1:1Vacancy Filler interview records carry date, time, interviewer(s), format (in-person or video), and outcome notes. We map these to Zoho Recruit Interview records linked to the Candidate and the Job Opening. Where Vacancy Filler stores the interviewer's email, we resolve it to a Zoho Recruit User for assignment. Video interview links migrate as Interview details. In-person interviews carry the Location field.
Vacancy Filler
Agency PSL
Zoho Recruit
Client
1:1The Vacancy Filler Agency Module stores preferred recruitment agencies with name, contact, specialism, and tier (Preferred, Approved, etc.). We export these as a separate agency list and load them into Zoho Recruit as Client records, with the agency tier stored in a custom field Agency_Tier__c. Agency specialism (e.g., STEM, Finance, Education) maps to the Client Industry or a custom picklist.
Vacancy Filler
Custom Application Question
Zoho Recruit
Custom Field (Candidates module)
lossyVacancy Filler supports bespoke screening questions per vacancy. These are stored at vacancy level with answers stored at application level. We extract the question schema for each vacancy during the pre-migration audit, group vacancies by common question sets, and create matching custom fields on the Zoho Recruit Candidates module. Answers migrate as values in those custom fields linked to the Candidate record. Vacancies with unique one-off question sets receive individual custom field creation with customer sign-off before migration. Zoho Recruit supports text, picklist, date, number, and checkbox field types for custom fields.
Vacancy Filler
Onboarding Record
Zoho Recruit
Candidate (Document Section)
1:1Onboarding data in Vacancy Filler tracks new-hire document completion, induction checklist progress, and start-date details. This is often incomplete for mid-year or active migrations. We flag each incomplete record with a completion_percentage__c custom field rather than silently dropping it, and load what exists into the Candidate record's document section or notes. The customer decides whether to backfill onboarding data manually post-migration or accept the partial state.
Vacancy Filler
Pre-Hire Test / Score
Zoho Recruit
Custom Field (Candidates module)
1:1Test results and screening scores attached to applications in Vacancy Filler migrate as custom fields on the Zoho Recruit Candidate record. We preserve the raw score, pass label, and test name as a composite custom field (e.g., Assessment_Score__c). Where Vacancy Filler uses a third-party assessment provider, we store the provider name, score, and date in separate custom fields for reference.
Vacancy Filler
Job Board Posting
Zoho Recruit
Custom Field or Integration Link
1:1Vacancy Filler tracks which job boards each vacancy was posted to as linked posting records (board name, posting URL, status). We extract the board name and posting URL and store them in a custom field on the Job Opening record (JobBoard_Posting_URL__c) or as notes on the record. Active postings are flagged for the customer's admin to re-activate in Zoho Recruit's job board integration after migration.
Vacancy Filler
Reporting / Management Information
Zoho Recruit
None
1:1Vacancy Filler dashboards, report definitions, and management information configurations are not independently exportable. We do not migrate reporting configurations. Historical application and vacancy data in Zoho Recruit is queryable through Zoho Recruit's standard and custom reports once migration is complete. We recommend the customer's admin reviews Zoho Recruit's standard reports (included in Standard tier) and builds custom reports from the migrated data post-go-live.
| Vacancy Filler | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Vacancy | Job Opening1:1 | Fully supported | |
| Candidate | Candidate1:1 | Fully supported | |
| Application | Candidate (Job Applied section)1:many | Fully supported | |
| Hiring Manager / User | User1:1 | Fully supported | |
| Talent Pool | Candidate (Tagged List)1:1 | Fully supported | |
| Interview Schedule | Interview1:1 | Fully supported | |
| Agency PSL | Client1:1 | Fully supported | |
| Custom Application Question | Custom Field (Candidates module)lossy | Fully supported | |
| Onboarding Record | Candidate (Document Section)1:1 | Fully supported | |
| Pre-Hire Test / Score | Custom Field (Candidates module)1:1 | Fully supported | |
| Job Board Posting | Custom Field or Integration Link1:1 | Fully supported | |
| Reporting / Management Information | None1: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.
Vacancy Filler gotchas
Acendre acquisition creates platform continuity uncertainty
No publicly documented API for bulk data export
Pricing is opaque with no public tiers
Onboarding records are often incomplete at migration time
Custom application questions vary per vacancy
Zoho Recruit gotchas
Daily API rate limits are tier-gated and per-user capped
User import hard cap of 2,000 records
Attachment folder hierarchy must be preserved exactly
Resume parsing quota varies by plan and resets daily
Custom fields unavailable in Free and Standard editions
Pair-specific challenges
Migration approach
Discovery and export feasibility assessment
We audit the source Vacancy Filler account for record counts (Vacancies, Candidates, Applications, Users, Talent Pools, Agency records, Interview records, Onboarding records), export feasibility, and Acendre contract review. We submit a data export request to Acendre if database export is not directly available to the customer. We simultaneously assess the Zoho Recruit destination account: edition selection (Free, Standard at $25/user/month, or Enterprise at $45/user/month), existing custom fields, pipeline stage configuration, and user provisioning. The discovery output is a written migration scope with the export constraint resolved, record-count estimates, and a Zoho Recruit edition recommendation.
Schema design and custom field provisioning in Zoho Recruit
We design the destination schema in Zoho Recruit before any data import. This includes creating custom fields on the Candidates module for bespoke Vacancy Filler application questions (identified during the vacancy schema audit), custom fields for agency tier (Agency_Tier__c), onboarding completion percentage (completion_percentage__c), and assessment scores. We configure the Job Opening pipeline stages to match Vacancy Filler vacancy statuses. All custom fields are created via Setup > Candidates > Customise Fields in a staging pass before the import begins. We also add a migration service account as the second user to satisfy Zoho Recruit's minimum-two-user requirement.
Data export and transformation
We extract data from Vacancy Filler using the agreed export path (direct database export, Acendre-provided extract, or structured screen-scraped export). Data is transformed into CSV format matching Zoho Recruit's import templates. The transformation includes: extracting per-vacancy custom question schemas and mapping answers to newly created custom fields; resolving Vacancy Filler user emails to Zoho Recruit User records for Hiring Manager assignment; splitting Talent Pool memberships into Candidate tags; and flagging incomplete onboarding records with the completion_percentage__c field and Onboarding_Incomplete__c flag. Candidates without a Last Name are populated with 'Not Provided' per Zoho Recruit's mandatory field requirement.
Sandbox validation and mapping sign-off
We import a sample of 50-100 records per module (Candidates, Job Openings, Users) into the Zoho Recruit account using the Data Migration wizard (Setup > Data Administration > Data Migration). The customer reconciles the imported sample against the Vacancy Filler source records, verifies that custom fields are correctly populated, confirms that pipeline stages match the original Vacancy Filler statuses, and signs off the field mapping. Corrections to custom field names, picklist values, and stage mappings are applied to the full dataset before the production import begins.
Production migration in dependency order
We run production migration in record-dependency order: Users first (via CSV import to satisfy Owner lookups), then Job Openings (as the parent vacancy record), then Candidates (with Last Name mandatory field satisfied and CV attachments migrated), then Interview records (linked to Candidate and Job Opening), then Agency records (as Clients with Agency_Tier__c), then Talent Pool tags (applied to Candidates), then Onboarding data (with completion_percentage__c flag). Each phase emits a row-count reconciliation report before the next phase begins. The Vacancy Filler account is placed in read-only mode during the final 48 hours of cutover to capture any delta created during the migration window.
Cutover, delta import, and automation rebuild handoff
We run a final delta migration for any records modified in Vacancy Filler during the migration window, then enable Zoho Recruit as the system of record. Job board posting integrations are re-activated in Zoho Recruit using the migrated posting URLs as reference. We deliver a written inventory of Vacancy Filler workflows, agency preferred-supplier-list configurations, and report definitions for the customer's admin to rebuild in Zoho Recruit's visual pipeline builder and reporting module. We do not rebuild Vacancy Filler workflows as Zoho Recruit Workflows inside the migration scope; that is a separate engagement. We support a one-week hypercare window post-cutover for data reconciliation issues.
Platform deep dives
Vacancy Filler
Source
Strengths
Weaknesses
Zoho Recruit
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 Vacancy Filler and Zoho Recruit.
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
Vacancy Filler: Not publicly documented — typical SaaS limits assumed and confirmed during scoping..
Data volume sensitivity
Vacancy Filler 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 Vacancy Filler to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Vacancy Filler to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Vacancy Filler
Other ways to arrive at Zoho Recruit
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.