Migrate your Revolut People data
Skills-first HRMS built by a fintech disruptor. Designed for mid-market teams that want performance management, recruiting, and core HR on a single platform with AI-assisted 1:1s and competency frameworks.
In its favor
Why people choose Revolut People
The signal that keeps Revolut People on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Skills-first performance management with competency frameworks gives HR teams a structured starting point rather than building from scratch, according to G2 reviewers who highlight ease of setup.
Consolidated HR, recruiting, and performance in one platform removes the need for multiple subscriptions, with pricing at £8–12 per active employee that compares favourably to bundled alternatives.
AI-powered 1:1 meeting assistance is a differentiator for teams that want automated agenda generation and follow-up nudges without a standalone tool.
G2 reviewers consistently highlight ease of use and customer support responsiveness, particularly for mid-sized teams migrating from manual spreadsheet-based performance tracking.
Pre-built probation monitoring tools and PIP templates reduce configuration time for teams implementing structured performance processes for the first time.
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.
Reasons to switch
Why people leave Revolut People
The recurring reasons buyers give for replacing Revolut People. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Revolut People fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Revolut People pricing overview
Pricing is per active employee per month in GBP, with four tiers from £8 to £12. Recruitment and HR are add-on modules at £3 above the base Performance tier, with the full bundle at £12. No implementation fees are charged.
Performance
Tier 1 of 4
£8 per active employee per month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Revolut People's schedule — see our quote-based pricing →
What gets migrated
Revolut People object support
Object-by-object support for Revolut People migrations. Per-pair details surface during scoping.
Employees
Fully supportedCore employee records with name, role, department, employment dates, and employment status are well-structured and exportable. We migrate these 1:1 to the destination employee object, preserving reporting lines via the org structure reference.
Org Structure
Mapping requiredRevolut People organizes employees in a hierarchical structure used for permissions and reporting. The hierarchy depth and naming conventions vary by tenant. We extract the tree as a flat parent-child mapping and reconstruct it at the destination.
Performance Cycles
Fully supportedPerformance cycles are date-bounded review periods. Each cycle contains review records linking employees to reviewers. We map these to the destination's review cycle or appraisal object, preserving cycle dates and completion status.
Skills and Competency Frameworks
Mapping requiredSkills are defined per role with proficiency levels and customisable competency matrices. The schema for custom skills varies significantly between tenants. We normalise skill names and proficiency scales to a standard set before writing to the destination.
Performance Reviews
Fully supportedReview records contain structured feedback, ratings, and reviewer comments. We preserve the full review text, rating scores, and reviewer identity. Where PIP or probation records exist, we flag them separately for explicit destination-field mapping.
Goals and Roadmaps
Mapping requiredGoal tracking with customisable roadmaps allows date-based milestones. Goal ownership and progress percentages transfer, though custom roadmap layouts require field-level remapping to the destination goal object.
Surveys (Engagement)
Mapping requiredEngagement surveys produce response data per employee. Survey questions and answer scales are customisable. We export questions and responses as a structured set and map them to the destination survey object, flagging any free-text questions.
Recruitment / Applicants
Mapping requiredJob postings, applicant records, interview scheduling, and application status live in the Recruitment module. Application status values and pipeline stage names vary per tenant. We map these to the destination ATS object, preserving stage history.
PTO / Leave Balances
Fully supportedTime, attendance, PTO, and sick leave are tracked per employee. Leave type names and accrual rules are configurable. We export current balances and leave type assignments, then map them to the destination time-off object.
Salary Structures
Mapping requiredPay grades and position descriptions are stored per role. Compensation data including base salary and equity details are accessible via the compensation insights feature. We export pay structure definitions and individual compensation records for mapping to the destination payroll or HR module.
User Roles and Access
Mapping requiredRole-based access controls assign permissions at the user level. Role names and permission sets differ between Revolut People and the destination. We extract the role assignments and flag them for explicit remapping during the access control migration.
Documents
Not in this platformDocument storage for employee files such as contracts, ID copies, and offer letters is not accessible via a documented public API. We do not migrate document blobs and instead generate a file manifest listing documents that must be transferred manually or via a separate file-transfer process.
| Object | Support | Notes |
|---|---|---|
| Employees | Fully supported | Core employee records with name, role, department, employment dates, and employment status are well-structured and exportable. We migrate these 1:1 to the destination employee object, preserving reporting lines via the org structure reference. |
| Org Structure | Mapping required | Revolut People organizes employees in a hierarchical structure used for permissions and reporting. The hierarchy depth and naming conventions vary by tenant. We extract the tree as a flat parent-child mapping and reconstruct it at the destination. |
| Performance Cycles | Fully supported | Performance cycles are date-bounded review periods. Each cycle contains review records linking employees to reviewers. We map these to the destination's review cycle or appraisal object, preserving cycle dates and completion status. |
| Skills and Competency Frameworks | Mapping required | Skills are defined per role with proficiency levels and customisable competency matrices. The schema for custom skills varies significantly between tenants. We normalise skill names and proficiency scales to a standard set before writing to the destination. |
| Performance Reviews | Fully supported | Review records contain structured feedback, ratings, and reviewer comments. We preserve the full review text, rating scores, and reviewer identity. Where PIP or probation records exist, we flag them separately for explicit destination-field mapping. |
| Goals and Roadmaps | Mapping required | Goal tracking with customisable roadmaps allows date-based milestones. Goal ownership and progress percentages transfer, though custom roadmap layouts require field-level remapping to the destination goal object. |
| Surveys (Engagement) | Mapping required | Engagement surveys produce response data per employee. Survey questions and answer scales are customisable. We export questions and responses as a structured set and map them to the destination survey object, flagging any free-text questions. |
| Recruitment / Applicants | Mapping required | Job postings, applicant records, interview scheduling, and application status live in the Recruitment module. Application status values and pipeline stage names vary per tenant. We map these to the destination ATS object, preserving stage history. |
| PTO / Leave Balances | Fully supported | Time, attendance, PTO, and sick leave are tracked per employee. Leave type names and accrual rules are configurable. We export current balances and leave type assignments, then map them to the destination time-off object. |
| Salary Structures | Mapping required | Pay grades and position descriptions are stored per role. Compensation data including base salary and equity details are accessible via the compensation insights feature. We export pay structure definitions and individual compensation records for mapping to the destination payroll or HR module. |
| User Roles and Access | Mapping required | Role-based access controls assign permissions at the user level. Role names and permission sets differ between Revolut People and the destination. We extract the role assignments and flag them for explicit remapping during the access control migration. |
| Documents | Not in this platform | Document storage for employee files such as contracts, ID copies, and offer letters is not accessible via a documented public API. We do not migrate document blobs and instead generate a file manifest listing documents that must be transferred manually or via a separate file-transfer process. |
Gotchas
What to watch for in Revolut People migrations
Issues we've hit on past Revolut People migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Revolut People?
Where Revolut People customers move next
5 destinations Revolut People can migrate to.
How a Revolut People migration works
Four steps, Revolut People-specific
Connect
Not publicly documented as a developer-facing REST API. Most third-party integrations rely on connectors managed by partner platforms (Deskbird, ClickUp, Monday.com, Notion, Jira). into Revolut People. Scopes limited to read-only on the data we move.
Map
We translate Revolut People-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Revolut People quirks before production.
Migrate
Full migration with Revolut People rate-limit handling. Rollback available throughout.
FAQ
Revolut People migration FAQ
Answers to the questions buyers ask most during Revolut People migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Revolut People migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Revolut People.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Revolut People setup and destination — written quote back within a business day.