Migrate from Varbi Recruit to Recruit CRM & ATS

Varbi Candidate profiles map to Recruit CRM Candidates with contact details, address, phone, and email transferred directly. National identity numbers (Swedish personnummer, Norwegian fødselsnummer, Danish CPR) require explicit customer consent during scoping under GDPR Article 9; we flag these fields and do not include them in the standard payload without documented sign-off. Multi-select custom fields are flattened into delimited columns before import.

Varbi Adverts map to Recruit CRM Jobs with title, description, department, location, employment type, and application deadline transferred directly. Application deadline maps to the closing_date field. We preserve the advert status (Draft, Published, Closed) and map it to Recruit CRM's job_status field.

Each Varbi Application links a Candidate to a Job Advert via a Hiring Process. We map the application record with its current stage, stage history, and timestamps preserved. The Hiring Process stage name re-mapping is completed during scoping with hiring manager sign-off before migration; stages with no Recruit CRM equivalent are flagged as collapsed or expanded in the mapping documentation.

Varbi Hiring Processes define stage sequences per role type. Each Hiring Process becomes a Recruit CRM Pipeline with stages re-mapped to the destination stage names. Stage probabilities migrate as custom fields if the customer requires them; Recruit CRM does not enforce stage probabilities natively. We configure pipeline access permissions to match the Varbi hiring team structure during the configuration phase.

Varbi Competency profiles used in structured interview scoring are custom-defined per organisation and do not have a native Recruit CRM equivalent object. We export the competency framework (name, definition, rating scale) and re-create it as custom candidate fields or a linked custom object in Recruit CRM. The exact mapping depends on the competency complexity; simple frameworks map to multi-select picklists, complex multi-level rubrics may require a separate Competency custom object with lookup to Candidate.

Varbi Interview Scorecards capture structured ratings and notes against Competencies per interview stage. We export scorecard data and map it to Recruit CRM's candidate evaluation fields or custom evaluation objects. Where Recruit CRM does not support structured scorecard objects natively, we flag the gap and provide a documentation of the original scorecard structure for manual re-entry or custom development.

Varbi custom fields vary by tenant with no enforced schema standardisation. We audit all custom fields during scoping, categorise them by type (text, number, date, multi-select, lookup), flatten multi-select values into delimited columns, and map each to the appropriate Recruit CRM field type. Fields that cannot be flattened (nested objects, complex hierarchies) are flagged as manual recreation required.

CVs, cover letters, portfolios, and other documents attached to candidate profiles export as binary files alongside record metadata. We store them in a mapped folder structure and push the file URLs into Recruit CRM's document fields or link them via the candidate record. Recruit CRM's attachment size limits and supported formats are checked during scoping.

Varbi offer record metadata and attached offer letter documents migrate to Recruit CRM Offers. Offer status (Pending, Accepted, Declined, Withdrawn) maps to Recruit CRM's offer_status field. Note that offer workflow automation does not migrate; we document the original offer-stage triggers for admin rebuild.

Varbi user accounts (recruiters, hiring managers, approvers) map to Recruit CRM Users by email match. Role and team assignments migrate to Recruit CRM's team structure and permission sets. Owners without a matching Recruit CRM User are held in a reconciliation queue for the customer to provision before record import.

Varbi tags and labels used for candidate segmentation, sourcing channel, or internal categorisation export as flat label arrays. We map them to Recruit CRM Tags on the candidate record. Tag naming conventions vary by tenant and are preserved as-is unless a tag standardisation decision is made during scoping.

Varbi's digital onboarding module is a separate product layer triggered after offer acceptance. Onboarding task lists, workflow states, and onboarding documents are not included in the standard candidate or advert export and are not migrated by FlitStack AI. Teams switching ATS platforms must treat onboarding as a separate workstream; Recruit CRM's integrated onboarding features can be configured post-migration as a parallel activity.