HRMS migration

Migrate from Revolut People to Zoho Recruit

Field-level mapping, validation, and rollback between Revolut People and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.

Revolut People logo

Revolut People

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

85%

11 of 13

objects map 1:1 between Revolut People and Zoho Recruit.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Revolut People to Zoho Recruit is a module-specific migration: the source platform bundles performance, HR, and recruiting in one stack, while Zoho Recruit is a dedicated ATS without native performance review or HR core modules. We extract recruitment data from Revolut People through admin-level CSV exports and screen-scraping workflows where no API exists, then restructure it to match Zoho Recruit's Candidate, Job Opening, Interview, and Client module schemas. Skills and competency frameworks defined in Revolut People require normalisation mapping because Zoho Recruit stores skills differently as part of the candidate profile rather than as a standalone framework object. We sequence Users first to satisfy Zoho Recruit's email-based user matching, then migrate Candidates and Job Openings before scheduling data, preserving application stage history as a custom field where Zoho Recruit's pipeline does not natively track the same stage values. Automations, recruitment advertising workflows, and offer-letter templates do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Zoho Recruit.

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

Revolut People logo

Revolut People

What's pushing teams away

  • Revolut People is not available for new US customers as of 2024 due to reported regulatory or compliance issues, forcing US-based teams to find alternative platforms.
  • The platform lacks depth in payroll processing and benefits administration compared to dedicated HR suites, with G2 reviewers noting these as areas where Revolut People lags behind competitors.
  • Advanced compensation analytics and equity management features are limited, with some reviewers noting that total compensation tracking feels bolted on rather than native to 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 Revolut People objects map to Zoho Recruit

Each row shows how a Revolut People 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.

Revolut People

Candidates / Applicants

maps to

Zoho Recruit

Candidates

1:1
Fully supported

Revolut People's applicant records migrate to Zoho Recruit Candidates. The source First Name, Last Name, Email, Phone, and Current Status map directly. Zoho Recruit requires Last Name as a mandatory field; where applicants have no last name in Revolut People, we set the value to 'not provided' per Zoho Recruit's import specification. Application stage from Revolut People's pipeline maps to a custom picklist field in Zoho Recruit because Zoho Recruit's standard stage values may not match Revolut People's custom stage names.

Revolut People

Job Openings / Job Postings

maps to

Zoho Recruit

Job Openings

1:1
Fully supported

Active job postings in Revolut People's Recruitment module map to Zoho Recruit Job Openings. Job title, department, location, employment type, and job description transfer as text fields. Post date and closing date map to Opening Date and Target Date. Status mapping resolves active, on-hold, and filled values from Revolut People to Zoho Recruit's Open, On Hold, and Closed status values.

Revolut People

Interview Schedules

maps to

Zoho Recruit

Interviews

1:1
Fully supported

Interview records in Revolut People (interview type, scheduled date and time, interviewer, location or video link, and outcome) map to Zoho Recruit Interviews. We resolve interviewer email addresses to Zoho Recruit User records via the User provisioning step before inserting interview records. Interview round information from Revolut People stores as a custom Number field in Zoho Recruit.

Revolut People

Application Status History

maps to

Zoho Recruit

Candidates (custom field)

lossy
Fully supported

Revolut People's application status change log tracks when a candidate moved between pipeline stages. Zoho Recruit stores the current stage but not the full status change history by default. We preserve the complete stage transition log as a structured text area field on the Candidate record, formatted as a timeline with dates and stage names, so that hiring managers retain audit visibility into how each candidate progressed.

Revolut People

Users / Team Members

maps to

Zoho Recruit

Users

1:1
Mapping required

Revolut People user accounts (name, email, role assignment) migrate to Zoho Recruit Users. Zoho Recruit requires each importing user to not already have a separate Zoho Recruit account; we flag any duplicate accounts for the customer admin to close before migration. We recommend importing at least two users before starting bulk candidate import per Zoho Recruit's technical requirement.

Revolut People

Clients

maps to

Zoho Recruit

Clients

1:1
Fully supported

If Revolut People stores client or vendor company records associated with job requisitions, these map to Zoho Recruit Clients. Client name, primary contact email, and phone transfer directly. Zoho Recruit's Client object also supports billing contact and address fields that we populate where available in the source export.

Revolut People

Skills and Competency Frameworks

maps to

Zoho Recruit

Candidate Skills (custom field)

1:1
Mapping required

Revolut People's standalone skills library defines competencies per role with proficiency levels. Zoho Recruit does not have a standalone skill framework object; instead skills attach to the candidate profile. We extract each candidate's assigned skills and proficiency levels from Revolut People, normalise the skill names against the full skill library discovered during scoping, and write them to a custom multi-select picklist or lookup field on the Zoho Recruit Candidate record. Custom competency matrices require flattening before import.

Revolut People

Employee Records (for internal candidates)

maps to

Zoho Recruit

Candidates

1:1
Fully supported

Revolut People employees who apply for internal roles are stored as employee records with an associated applicant record. We link the Zoho Recruit Candidate to a Zoho People Employee record via email matching if the customer also runs Zoho People. Internal candidate flag and original employee ID migrate as custom fields on the Candidate record.

Revolut People

Attachments / Resumes

maps to

Zoho Recruit

Attachments

1:1
Mapping required

Candidate resumes and attachments exported from Revolut People are uploaded to Zoho Recruit as file attachments linked to the corresponding Candidate record. We use Zoho Recruit's attachment import alongside the candidate record insert, with the file name preserved as the original. Maximum file size follows Zoho Recruit's attachment limits.

Revolut People

Surveys / Candidate Feedback

maps to

Zoho Recruit

Assessments

1:1
Mapping required

Revolut People stores candidate satisfaction or assessment survey responses linked to interview records. Zoho Recruit's Assessments module holds structured evaluation data. We map survey question responses and overall scores to the Assessment object, linking each assessment to the relevant Candidate and Interview record in Zoho Recruit. Open-ended survey comments migrate as notes attached to the assessment.

Revolut People

Goals and Roadmaps (recruitment targets)

maps to

Zoho Recruit

Custom Module or Notes

lossy
Fully supported

Revolut People allows teams to set goal roadmaps for recruitment targets such as time-to-hire or offer acceptance rate. Zoho Recruit does not have a native goal tracking module for hiring metrics. We migrate goal definitions and latest progress as a custom Zoho Recruit module or as structured notes on the Job Opening, depending on the customer's reporting requirements identified during scoping.

Revolut People

Performance Reviews (not applicable to ATS scope)

maps to

Zoho Recruit

N/A

1:1
Fully supported

Revolut People's performance review and appraisal records are part of the HRMS core module and do not map to Zoho Recruit's ATS object model. These records are flagged as out-of-scope for this migration. If the customer also uses Zoho People, performance review data can be migrated separately through the Zoho People migration scope.

Revolut People

PTO and Leave Balances

maps to

Zoho Recruit

N/A

1:1
Fully supported

Time, attendance, PTO, and leave balance data from Revolut People's HR module do not map to Zoho Recruit. Zoho Recruit is an ATS and does not track employee time off. Leave data is out of scope for this migration and should be handled separately if the customer implements Zoho People as their HR core.

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.

Revolut People logo

Revolut People gotchas

High

No public HRMS API means no automated export pipeline

High

US customer suspension limits platform availability

Medium

Compensation equity data stored separately from payroll

Medium

Custom skills and scorecards vary per tenant

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

  • Revolut People has no public HRMS API for automated extraction

    Revolut People's developer portal documents only the Business banking API, not the People HRMS module. There is no documented endpoint for employees, applicants, job postings, or interview records. We work around this by using admin-level CSV exports where available and structured screen-scraping workflows for data that does not export cleanly. Where exports are incomplete or unavailable, we flag the object as requiring manual extraction before migration begins. This adds time to the discovery and extraction phases and may limit the fidelity of historical application status logs that are not included in standard CSV exports.

  • Zoho Recruit requires Last Name as a mandatory field on all Candidates

    Zoho Recruit enforces Last Name as a mandatory field on Candidate records during import. If Revolut People stores candidates with no last name (for example, single-name candidates from certain cultural naming conventions), the import will silently ignore those records. We handle this by setting absent last names to 'not provided' in the transform step before import, preserving the original full name in a custom field so the customer can correct it post-migration. The customer's admin should review these records immediately after migration for accuracy.

  • Custom skill frameworks require flattening before ATS import

    Revolut People's competency frameworks allow multi-level skill definitions with custom proficiency scales, values scorecards, and role-to-skill mappings per tenant. Zoho Recruit stores skills as flat entries on the candidate profile without a standalone framework object. We audit the full Revolut People skill library during scoping to build a normalisation map, then flatten each candidate's assigned skills and proficiency levels into comma-separated or multi-select values for Zoho Recruit. This discovery work adds two to three days to the scoping phase and may require the customer's HR team to validate the normalised skill taxonomy.

  • Zoho Recruit API credit limits apply to bulk migration writes

    Zoho Recruit uses a credit-based API limit system: the Professional edition includes 10,000 base credits plus 500 per user license, with a 500,000 maximum, and Bulk Write operations cost 500 credits per initialisation. For large candidate migrations (over 10,000 records), we manage batch sizing and credit replenishment across a 24-hour rolling window to avoid hitting limits mid-migration. The Enterprise edition (15,000 base plus 1,000 per user, 1,000,000 max) provides more headroom. We monitor credit consumption and apply exponential backoff if credit replenishment lags during the migration run.

  • Zoho Recruit Free edition does not support custom fields

    Custom fields are not available in the Free edition of Zoho Recruit. If the customer's migration scope includes custom fields for application stage history, internal candidate flags, or competency normalisation, the destination account must be on the Standard tier ($25/user/month) or above. We confirm the target edition during scoping and flag any custom field requirements against the current edition. Customers on the Free plan must upgrade before migration begins if any custom field is in scope.

Migration approach

Six steps for a successful Revolut People to Zoho Recruit data migration

  1. Discovery and extraction scoping

    We audit the Revolut People recruitment module with the customer's admin to identify the full scope: candidate records, job postings, interview schedules, application status logs, skill assignments, and attachment volume. Because Revolut People has no public API, we map every available export path, identify objects that require screen-scraping or manual extraction, and document any data that cannot be extracted at this stage. We also confirm the target Zoho Recruit edition (Standard minimum if custom fields are in scope) and identify any existing Zoho Recruit accounts that would conflict with user imports.

  2. Skill library audit and normalisation map

    We extract the full skill library from Revolut People including all custom skills, proficiency levels, values scorecards, and competency matrices. We build a normalisation map that flattens each framework into a set of skill names and proficiency values suitable for Zoho Recruit's flat candidate skill fields. The customer HR team reviews and approves the normalisation map before any candidate data is transformed. This step typically adds two to three days and must be completed before candidate migration begins.

  3. Zoho Recruit environment preparation

    We configure the destination Zoho Recruit account: creating custom fields (Application Stage History, Internal Candidate Flag, Original Candidate ID, Competency Normalisation), setting up pipeline stage values to match Revolut People's stage names where possible, provisioning at least two recruiter users per Zoho Recruit's technical import requirement, and confirming that the edition supports the required custom field types. Schema is validated in a Zoho Recruit sandbox or staging environment before production migration begins.

  4. Data extraction and transformation

    We extract data from Revolut People in dependency order: Users first (to satisfy email-based matching), then Job Openings, then Candidates with their application status history and skill assignments, then Interviews and Assessments, then Attachments. Each export is validated for row count, required field presence (particularly Last Name), and duplicate records. The transformation layer applies the skill normalisation map, converts absent last names to 'not provided', maps pipeline stage values to Zoho Recruit equivalents, and formats dates and contact information to match Zoho Recruit's import schema.

  5. Production migration and reconciliation

    We run production migration into Zoho Recruit in record-dependency order: Users first (validated against existing Zoho Recruit User table for duplicates), then Job Openings, then Candidates with skill and status history, then Interviews, then Assessments, then Attachments. Each phase emits a row-count reconciliation report comparing source count to destination count. We monitor Zoho Recruit API credit consumption throughout and apply batch sizing adjustments if credit limits approach. The customer admin spot-checks 25-50 candidate records against the Revolut People source for field-level accuracy before sign-off.

  6. Cutover, validation, and automation rebuild handoff

    We freeze Revolut People recruitment writes during cutover, run a final delta migration of any records created or modified during the migration window, then confirm Zoho Recruit as the active ATS. We deliver a written inventory of Revolut People automations, recruitment advertising workflows, and offer-letter templates that do not migrate, with a Zoho Recruit configuration recommendation for each. We support a five-day hypercare window for reconciliation issues raised by the recruiting team. We do not rebuild automations inside the migration scope; that work is handled by the customer's admin or a Zoho implementation partner.

Platform deep dives

Context on both ends of the pair

Revolut People logo

Revolut People

Source

Strengths

  • Skills-based competency frameworks with pre-built and customisable proficiency scales for role-level skill definitions.
  • AI-assisted 1:1 meeting tools that generate agendas and track action items between manager and employee.
  • Modular pricing allows teams to start with Performance at £8/employee and add Recruitment or HR at £3–4 more per month.
  • Zero implementation fees stated upfront, reducing initial cost of adoption for new customers.
  • Organisational structure editor integrates permissions, reporting lines, and department hierarchy in one view.

Weaknesses

  • No public HRMS API documented; migration relies on screen scraping or partner export tools which may miss historical review data.
  • US market suspension since 2024 limits the platform's relevance for international teams with US entities.
  • Limited payroll depth compared to dedicated HR suites; compensation tracking lacks integration with payroll execution.
  • Benefits administration is view-only for employees rather than a full benefits-enrollment engine with carrier integrations.
  • Documentation for GDPR data portability requests is sparse, making right-to-erasure and data export compliance harder to automate.
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. 2 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 Revolut People and Zoho Recruit.

  • Object compatibility

    B

    2 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

    Revolut People: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

Estimate your Revolut People 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 Revolut People to Zoho Recruit data migrations

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

Can't find your answer?

Walk through your Revolut People 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 two and four weeks for accounts under 5,000 candidates and 200 active job openings with no complex skill framework normalisation required. Migrations with large custom skill libraries, multiple non-standard pipeline stages, attachment-heavy application histories (over 20,000 files), or concurrent Zoho People onboarding move to five to eight weeks because of the skill audit and normalisation map, the screen-scraping extraction work, and the API credit management across large batch writes.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Revolut People.
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