Migrate from Revolut People to Crelate

Revolut People applicant records map to Crelate Candidate objects. Application status values (Applied, Screening, Interview, Offer, Hired, Rejected) from Revolut People map to Crelate pipeline stages, which are configurable per customer. We extract applicant name, email, phone, LinkedIn URL, source, and application date as structured fields. Interview notes and scorecards from Revolut People's scheduling module map to Crelate Activity records attached to the Candidate. Resume files are extracted as document blobs and loaded into Crelate's Resume Toolbox.

Revolut People job postings map to Crelate Job Orders. The job title, description, location, employment type (full-time, part-time, contract), and department fields transfer directly. Job status (Open, Closed, On Hold) maps to Crelate Job Order status. We flag any custom job fields that have no Crelate equivalent and either map them to Crelate custom fields (if available on the customer's plan) or document them in the handoff report.

Candidates who have been hired through Revolut People's recruitment workflow and converted to employees can be represented in Crelate as Contact records if the customer also uses Crelate as a CRM for client relationship management. We maintain the candidate-to-contact link by preserving the original application ID as a custom field on the Contact record. Hired candidates who do not need CRM contact records are excluded from this mapping.

Revolut People's hierarchical org chart with departments, managers, and reporting lines does not have a direct equivalent in Crelate's ATS model. We extract the org tree as a flat parent-child dataset and store it in a custom Candidate or Job Order field group (if the customer's Crelate plan supports custom fields) or document it in the handoff report for manual entry. Org structure intended for HR purposes rather than recruiting purposes should be migrated to a dedicated HRMS.

Revolut People performance cycles with date-bounded review periods, reviewer assignments, and rating scores have no equivalent object in Crelate. Crelate is an ATS and does not include a performance management module. We extract the full performance cycle data as a structured CSV and deliver it alongside the migration, flagging it as requiring a separate performance management tool such as Lattice, Leapsome, or HiBob HRIS for the customer to handle post-migration.

Review records containing structured feedback, rating scores, and reviewer comments from Revolut People do not migrate to Crelate. Crelate's interview scorecards capture candidate evaluation data but not employee performance reviews. We extract full review text, rating values, reviewer identity, and cycle dates as a structured dataset for the customer to import into a dedicated performance management platform or preserve as a reference archive.

Revolut People's custom skills, proficiency levels, and competency matrices per role vary significantly between tenants and have no native equivalent in Crelate's data model. We audit the full skills library during discovery, normalise skill names and proficiency scales, and store them as Crelate tags on the Candidate record. Customers with complex competency frameworks should consider rebuilding them as custom fields or a separate skills taxonomy in Crelate after migration.

Goal tracking with customisable roadmaps and date-based milestones from Revolut People has no equivalent in Crelate. Goal ownership and progress percentages do not transfer. We extract goal data as a structured CSV for the customer to evaluate against Crelate's Activity and Task features (which can partially substitute for goal tracking in a recruiting context) or to migrate to a dedicated goals and OKRs platform.

Revolut People's engagement survey responses and pulse survey data do not migrate to Crelate. Survey questions, answer scales, and employee response data are exported as a structured dataset. If the customer uses engagement survey data for recruiting decisions (such as using engagement scores as part of internal mobility or promotion tracking), we recommend a dedicated engagement platform such as Culture Amp or Lattice as the destination for this data.

Time, attendance, PTO, and sick leave balances per employee from Revolut People do not migrate to Crelate. Crelate does not include a time-tracking or leave management module. We extract current balances and leave type assignments as a structured export. Customers needing leave management post-migration should evaluate dedicated HR tools such as BambooHR, HiBob, or Rippling.

Pay grades, position descriptions, base salary, and equity details stored in Revolut People's compensation insights dashboard sit in a separate data partition from standard employee records. This data is exported as a separate dataset and joined to the employee record at extraction time. Equity projections and vesting schedules may not export cleanly. Crelate has no compensation management object. We recommend a dedicated compensation platform such as Rippling, Paycor, or a custom equity management tool as the destination for this data.

Revolut People role-based access controls assign permissions at the user level across performance, recruiting, and HR modules. We extract role assignments and flag them for explicit mapping to Crelate's user roles and permissions structure. Crelate's Role-Based Access Control (RBAC) on the Business plan supports Advanced User Roles and Permissions including IP restrictions and two-factor authentication. We document the Revolut People permission model and recommend a Crelate RBAC configuration that maps to the nearest equivalent access level.

Employee document storage for contracts, ID copies, and offer letters is not accessible via any documented public API in Revolut People. We do not migrate document blobs. Instead, we generate a file manifest listing every document name, associated employee, and document type so the customer's admin can manually upload or archive the files post-migration.