Migrate from CatalystOne to Recruit CRM & ATS

CatalystOne Person records map to Recruit CRM Candidates. Core fields (name, email, phone, employment status, start date, department, manager reference) transfer directly. Custom properties on the Person object vary by customer tenant and are enumerated during pre-migration schema discovery. Address and nationality fields require format normalisation before Recruit CRM import since CatalystOne stores Nordic address formats that Recruit CRM's standard fields may truncate.

CatalystOne's position-based model (title, department, hierarchy) does not have a direct Recruit CRM equivalent. We map the most recent Position title to the Candidate's current or most-recent role field. Where the customer maintains an internal job architecture, we replicate it as a custom picklist in Recruit CRM or store the position code as a custom field for reporting consistency.

CatalystOne department hierarchy maps to Recruit CRM Client records when the departments represent billable client organisations, or to a custom organisational hierarchy field when they represent internal cost centres. Multi-level Nordic org structures (legal entity to division to department) may require flattening in Recruit CRM, which uses a flat client list with optional tagging.

CatalystOne competency records (skill, rating, valid-from date) map to Recruit CRM Skills attached to the Candidate record. Many-to-many person-to-competency relationships split into individual skill entries. Rating scales differ per customer and require normalisation during transform. We flag any competency taxonomy that exceeds Recruit CRM's skill management depth for manual post-migration cleanup.

CatalystOne Performance Reviews have no equivalent object in Recruit CRM. Recruit CRM is an ATS, not an HCM or performance management platform. We export the review records as a structured CSV during migration and store them in a separate archive for the customer's HR team to handle independently. The existence of this export is noted in the deliverables inventory so no data is assumed lost.

CatalystOne Succession Plans (position-to-candidate readiness ratings) have no equivalent in Recruit CRM. Succession planning is an HCM concept outside Recruit CRM's ATS scope. We export the plan hierarchy as a structured report during the data inventory phase and flag it as a separate workstream for HR leadership. The customer may address this in a dedicated succession tool post-migration.

CatalystOne employee documents (contracts, certifications, policies) stored as binary attachments migrate as file attachments on the corresponding Recruit CRM Candidate record. We transfer the file binary alongside metadata (document type, date, owner). Some document types require renaming to fit Recruit CRM's attachment naming convention.

AD and SSO provisioning data linked from CatalystOne's HR master is not applicable to Recruit CRM. We export the current access record state for the customer's IT team to use in provisioning Recruit CRM user accounts independently. This is a manual IT task, not a data migration task.

CatalystOne's payroll provider sync (Visma, SAP, and other Nordic payroll integrations) has no Recruit CRM equivalent. Recruit CRM is an ATS and does not manage payroll. We document the payroll integration configuration during discovery so the customer's HRIS or IT team can evaluate replacement payroll connectors independently. The payroll mapping is excluded from migration scope.

CatalystOne approval workflows and HR process automation rules are not exposed via API and cannot be exported as configuration. We document the active workflow configurations during discovery and deliver a written inventory for the customer's HR team to rebuild in Recruit CRM's workflow automation builder or handle manually. This is a standard scope exclusion for all CatalystOne migrations.

If the customer uses CatalystOne's time-tracking module, we scope the export of timesheet records and accrual balances during discovery. However, many customers route time data through a dedicated time system. Recruit CRM does not handle time and attendance. We export what exists in CatalystOne as a structured report for the customer's payroll or finance team to handle separately.