HRMS migration

Migrate from Vacancy Filler to Zoho Recruit

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 logo

Vacancy Filler

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

83%

10 of 12

objects map 1:1 between Vacancy Filler and Zoho Recruit.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Vacancy Filler logo

Vacancy Filler

What's pushing teams away

  • Pricing is opaque and requires a sales conversation, making it difficult for smaller organisations or those with rapid headcount growth to budget predictably.
  • The platform's UI and feature set have not kept pace with modern ATS competitors, particularly around candidate relationship management and engagement tracking.
  • Acendre acquisition in 2021 raised questions about product roadmap direction, support continuity, and whether Vacancy Filler will be merged into a broader talent management suite.
  • Integration ecosystem is limited to Microsoft Outlook, Twitter, LinkedIn, and job boards, with no native HRIS or onboarding payroll integration available out of the box.
  • Limited API documentation and developer access means organisations with custom integration requirements struggle to build on top of the platform.

Choosing

Zoho Recruit logo

Zoho Recruit

What's pulling them in

  • Lowest cost entry point of any major ATS — a free tier with Candidates, Clients, Contacts, Interviews, and a career site lets small teams validate before committing to a paid plan.
  • Deep Zoho ecosystem integration — if the team already uses Zoho CRM, Sheets, or Analytics, candidate data flows between modules without re-keying or third-party middleware.
  • Customizable pipelines and stages — both agency and corporate editions let users define custom pipeline stages and assign candidates through drag-and-drop visual boards.
  • AI-assisted features via Zia — resume parsing, candidate summarization, and job-candidate matching are built in on paid tiers, reducing manual screening time.
  • Job board aggregation at no extra cost — paid tiers include postings to major job boards, extending reach without purchasing separate job ad bundles.

Object mapping

How Vacancy Filler objects map to Zoho Recruit

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

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Vacancy 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

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Candidate 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

maps to

Zoho Recruit

Candidate (Job Applied section)

1:many
Fully supported

Vacancy 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

maps to

Zoho Recruit

User

1:1
Fully supported

Vacancy 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

maps to

Zoho Recruit

Candidate (Tagged List)

1:1
Fully supported

Longlisted 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

maps to

Zoho Recruit

Interview

1:1
Fully supported

Vacancy 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

maps to

Zoho Recruit

Client

1:1
Fully supported

The 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

maps to

Zoho Recruit

Custom Field (Candidates module)

lossy
Fully supported

Vacancy 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

maps to

Zoho Recruit

Candidate (Document Section)

1:1
Fully supported

Onboarding 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

maps to

Zoho Recruit

Custom Field (Candidates module)

1:1
Fully supported

Test 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

maps to

Zoho Recruit

Custom Field or Integration Link

1:1
Fully supported

Vacancy 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

maps to

Zoho Recruit

None

1:1
Not supported

Vacancy 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.

Gotchas + challenges

What specifically takes care here

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 logo

Vacancy Filler gotchas

High

Acendre acquisition creates platform continuity uncertainty

High

No publicly documented API for bulk data export

Medium

Pricing is opaque with no public tiers

Medium

Onboarding records are often incomplete at migration time

Low

Custom application questions vary per vacancy

Zoho Recruit logo

Zoho Recruit gotchas

High

Daily API rate limits are tier-gated and per-user capped

High

User import hard cap of 2,000 records

Medium

Attachment folder hierarchy must be preserved exactly

Medium

Resume parsing quota varies by plan and resets daily

Low

Custom fields unavailable in Free and Standard editions

Pair-specific challenges

  • Vacancy Filler has no publicly documented API for bulk export

    Technical research confirmed no publicly accessible API endpoint, developer portal, or bulk export mechanism for Vacancy Filler. All migrations must proceed via database export (where the customer has direct database access and Acendre permits it) or structured screen-scraped exports where they do not. We scope the export constraint upfront during discovery. If Acendre cannot provide a supported export mechanism or the customer lacks database access, we negotiate a manual export format with an extended timeline. This constraint is the primary risk item in Vacancy Filler migrations and can add two to four weeks to the migration schedule if export tooling must be built.

  • Acendre acquisition introduces data export eligibility uncertainty

    Vacancy Filler was acquired by Acendre in October 2021. The acquisition means that account data, support tier, and SLA terms are now governed by Acendre's policies rather than Vacancy Filler's original terms. We verify the customer's current support contract, data export eligibility, and whether a database export is technically available with Acendre directly before confirming migration scope. Customers on legacy Vacancy Filler contracts without explicit data portability provisions may face additional negotiation with Acendre to obtain a full database export.

  • Zoho Recruit requires at least two users before migration begins

    Zoho Recruit's import tooling requires a minimum of two users in the destination account before the Data Migration wizard can process CSV imports. If the customer creates a fresh Zoho Recruit account with only the primary admin user, the import wizard will block until a second user is added. We add a migration service account as the second user during Zoho Recruit setup to satisfy this requirement. The migration service account is deactivated after cutover if it is not needed for ongoing operations.

  • Custom application questions require per-vacancy schema mapping

    Vacancy Filler stores bespoke screening questions at vacancy level, meaning each vacancy can have a unique question schema with no shared master template. Migrating these as static values requires extracting the question schema per vacancy, identifying common question groups across vacancies, and creating matching custom fields in Zoho Recruit before any Candidate import. Vacancies with unique one-off question sets that cannot be grouped receive individual custom field treatment, requiring customer sign-off before field creation. This step adds scope to the pre-migration data audit phase.

  • Onboarding records are frequently incomplete at migration time

    Onboarding data in Vacancy Filler is entered progressively as new hires complete induction steps. Organisations migrating mid-year or with active hiring in progress will have incomplete onboarding records for candidates currently in the onboarding phase. We flag each incomplete record in the pre-migration data audit, load them with a completion_percentage__c field populated from the Vacancy Filler induction checklist status, and tag the record with an Onboarding_Incomplete__c flag. The customer decides whether to backfill onboarding data manually post-migration or accept the partial state.

Migration approach

Six steps for a successful Vacancy Filler to Zoho Recruit data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Vacancy Filler logo

Vacancy Filler

Source

Strengths

  • Single system covering vacancy creation, candidate tracking, interview scheduling, and onboarding.
  • Multi-job-board posting from one vacancy entry across major UK job boards.
  • Designed for both high-volume and specialist recruitment with a fixed-price positioning.
  • Strong user reviews for ease of use among non-technical HR staff in education and public sector.

Weaknesses

  • No publicly documented API for programmatic access, limiting automation and integration options.
  • Pricing is opaque and requires direct sales engagement with no self-serve trial or tiered public pricing.
  • Acendre acquisition introduces uncertainty about long-term product independence and roadmap.
  • Limited third-party integrations beyond Outlook, LinkedIn, and major job boards.
Zoho Recruit logo

Zoho Recruit

Destination

Strengths

  • Free tier includes full candidate management with a hosted career site, making it viable for very small staffing operations.
  • Multi-edition architecture splits agency and corporate HR workflows, with tier-gated features that scale predictably with headcount.
  • Per-user API rate limits (500–1000/day) are generous for mid-size migrations compared to competitors that gate by total org quota.
  • Zoho's own data migration tool supports CSV import from Bullhorn, CATS, Jobdiva, and Workable, validating interoperability with common ATS formats.
  • 45-day money-back guarantee and 15-day full-feature trial reduce financial risk for teams evaluating the platform.

Weaknesses

  • Free edition excludes custom fields, lookup relationships, and formula fields, making data model extensibility unavailable until a paid tier is purchased.
  • Resume parsing quotas are capped: 250/day on Standard, 500/day on Professional, unlimited only on Enterprise — bulk imports of large candidate pools will hit these limits.
  • No bulk/batch API endpoint for inserts or updates — large migrations rely on looping single-record API calls within daily rate limit windows.
  • Custom modules cannot be imported from external ATS; only standard modules (Users, Candidates, Clients, etc.) are in the supported migration list.
  • Attachments require a rigid folder hierarchy to re-associate with records, and any deviation in folder structure during extraction causes silent disassociation.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Vacancy Filler and Zoho Recruit.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Vacancy Filler: Not publicly documented — typical SaaS limits assumed and confirmed during scoping..

  • Data volume sensitivity

    B

    Vacancy Filler doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Vacancy Filler to Zoho Recruit migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Vacancy Filler to Zoho Recruit data migrations

Answers to the questions buyers ask most during Vacancy Filler to Zoho Recruit migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between four and six weeks for accounts under 5,000 Candidates and 500 Vacancies with a confirmed database export path. Migrations with no documented API export path requiring negotiated Acendre data extracts, large per-vacancy custom question schema sets, incomplete onboarding record sets, or extended parallel-run windows move to eight to twelve weeks because of export tooling complexity and individual field mapping scope.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Vacancy Filler.
Land in Zoho Recruit, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day