Migrate from Revolut People to Recruit CRM & ATS

Revolut People employee records (name, email, role, department, employment dates, employment status) migrate to Recruit CRM candidate profiles. The mapping is a schema reinterpretation rather than a 1:1 field copy because Recruit CRM's candidate object is optimised for recruitment workflows rather than HR records. We map employee email to candidate email, department to a custom candidate field, and employment status to a custom field. Start dates migrate to a custom field rather than a native Recruit CRM date field since candidate records do not have an employment-date schema.

Revolut People recruitment module applicants map directly to Recruit CRM applications. Application status values (applied, screening, interview, offer, hired, rejected) migrate to Recruit CRM pipeline stages, which we configure to match the source stage names during migration. Job association migrates by resolving the Revolut People job posting reference to the Recruit CRM job record created in parallel.

Revolut People job postings (title, description, department, location, employment type) map to Recruit CRM job records. The job description HTML migrates as rich text. Any active job posting status (open, paused, closed) maps to Recruit CRM job status. We create Recruit CRM jobs before the application import so that the job reference is satisfied at the point of application insert.

Revolut People compensation insights data including base salary, pay grade, and equity details reside in a separate data partition from standard employee records. We export this as a distinct dataset and join it to the employee record at migration time. Base salary maps to a custom numeric candidate field in Recruit CRM (current_salary__c). Equity and total compensation figures map to additional custom numeric fields. These are informational fields; Recruit CRM has no native payroll or equity tracking module.

Revolut People performance cycles and their associated review records have no equivalent object in Recruit CRM. Recruit CRM is an ATS and CRM without performance management, appraisal, or review-cycle functionality. We do not migrate performance cycles or their associated review data. We flag the existence of active or historical performance cycles in the migration scope document so that the customer's HR admin can decide whether to retain this data in a spreadsheet or a dedicated performance management tool.

Revolut People skills and competency matrices vary per tenant with fully custom skill names and proficiency scales. There is no standard skill taxonomy enforced. We audit the full custom skill library during discovery, normalise skill names to a flat list, and write them to Recruit CRM candidate custom fields. Proficiency levels migrate as custom picklist values. Because Recruit CRM has no native skills management or competency framework module, this mapping is an informational normalisation rather than a functional feature migration.

Revolut People performance review records contain structured feedback, ratings, reviewer comments, and PIP or probation data. Recruit CRM has no review, appraisal, or feedback module. We do not migrate review records. We flag PIP and probation records separately in the scope document because they represent a compliance-relevant data category that requires explicit handling—either retention as a PDF export or transfer to a dedicated HR system.

Revolut People goal tracking with customisable roadmaps and date-based milestones has no equivalent in Recruit CRM. Goal ownership and progress percentages have no target object. We do not migrate goals or roadmaps. We note the existence of active goals in the migration scope and recommend the customer transfer them to their new HR or performance management platform.

Revolut People engagement survey questions and response data have no target in Recruit CRM. Recruit CRM does not include a survey, pulse-feedback, or engagement module. We do not migrate survey records or responses. We note the existence of engagement survey history in the scope document and flag it as requiring a separate survey platform for future use.

Revolut People hierarchical org structure with reporting lines, department hierarchy, and role-based permissions has no equivalent in Recruit CRM. Recruit CRM manages candidate and client relationships, not internal organisational hierarchies. We do not migrate org structure data. We deliver the reporting hierarchy as a flat parent-child CSV for the customer's reference.

Revolut People time, attendance, PTO, and sick leave balances per employee have no target in Recruit CRM. Recruit CRM does not include a time-tracking or leave-management module. We do not migrate leave balances or accrual data. We note current PTO balances in the scope document for the customer's HR admin to transfer to their new HR system.

Revolut People role-based access controls with per-user permission sets have no equivalent mapping to Recruit CRM. Recruit CRM has its own user role model optimised for recruitment workflows (recruiter, admin, hiring manager). We do not migrate access control configurations. We deliver a role mapping table as a written reference for the customer's admin to configure Recruit CRM roles post-migration.