HRMS migration
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
Source
Zoho Recruit
Destination
Compatibility
11 of 13
objects map 1:1 between Revolut People and Zoho Recruit.
Complexity
BStandard
Timeline
2-4 weeks
Overview
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.
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 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
Zoho Recruit
Candidates
1:1Revolut 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
Zoho Recruit
Job Openings
1:1Active 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
Zoho Recruit
Interviews
1:1Interview 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
Zoho Recruit
Candidates (custom field)
lossyRevolut 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
Zoho Recruit
Users
1:1Revolut 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
Zoho Recruit
Clients
1:1If 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
Zoho Recruit
Candidate Skills (custom field)
1:1Revolut 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)
Zoho Recruit
Candidates
1:1Revolut 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
Zoho Recruit
Attachments
1:1Candidate 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
Zoho Recruit
Assessments
1:1Revolut 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)
Zoho Recruit
Custom Module or Notes
lossyRevolut 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)
Zoho Recruit
N/A
1:1Revolut 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
Zoho Recruit
N/A
1:1Time, 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.
| Revolut People | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidates / Applicants | Candidates1:1 | Fully supported | |
| Job Openings / Job Postings | Job Openings1:1 | Fully supported | |
| Interview Schedules | Interviews1:1 | Fully supported | |
| Application Status History | Candidates (custom field)lossy | Fully supported | |
| Users / Team Members | Users1:1 | Mapping required | |
| Clients | Clients1:1 | Fully supported | |
| Skills and Competency Frameworks | Candidate Skills (custom field)1:1 | Mapping required | |
| Employee Records (for internal candidates) | Candidates1:1 | Fully supported | |
| Attachments / Resumes | Attachments1:1 | Mapping required | |
| Surveys / Candidate Feedback | Assessments1:1 | Mapping required | |
| Goals and Roadmaps (recruitment targets) | Custom Module or Noteslossy | Fully supported | |
| Performance Reviews (not applicable to ATS scope) | N/A1:1 | Fully supported | |
| PTO and Leave Balances | N/A1:1 | Fully 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.
Revolut People gotchas
No public HRMS API means no automated export pipeline
US customer suspension limits platform availability
Compensation equity data stored separately from payroll
Custom skills and scorecards vary per tenant
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 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.
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.
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.
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.
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.
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
Revolut People
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 2 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 Revolut People and Zoho Recruit.
Object compatibility
2 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
Revolut People: Not publicly documented..
Data volume sensitivity
Revolut People 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 Revolut People to Zoho Recruit migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Revolut People
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.