Migrate from CatalystOne to Zoho Recruit

CatalystOne Person records map to Zoho Recruit Candidate. We export core fields (full name, email, phone, employment status, start date, department, manager) and preserve them as typed Candidate fields. The Last Name field is mandatory in Zoho Recruit; any CatalystOne Person records without a last name are flagged during pre-migration discovery and either enriched from the source or mapped to a 'not provided' placeholder. Custom properties on the Person object (which vary per customer tenant and are not publicly documented) are enumerated during schema discovery and mapped to Zoho Recruit Candidate custom fields, subject to the edition limit (50 per module on Standard, 300 on Enterprise).

CatalystOne Position records carry title, department, hierarchy relationships, and job description. We map active Positions to Zoho Recruit Job Openings, preserving the Position title as Job Title, the department assignment as Department lookup, and the job description as the Opening Description field. A Position can generate one or more Job Opening records in Zoho Recruit if the same role is posted multiple times; we handle this as a 1:N split where the position identifier is stored as a custom field on each Job Opening for traceability.

CatalystOne links Persons to Positions through employment assignments. In Zoho Recruit, the association between a Candidate and a Job Opening is the Application object. We create a Candidate record for the Person and then an Application linking that Candidate to the corresponding Job Opening derived from the Position. The assignment's effective date is stored as a custom field on the Application for historical reference.

CatalystOne Competency records exist as many-to-many relationships between Persons and Competency definitions (skills, certifications, ratings). We split these into individual skill entries on the Candidate record. Each unique Competency type in CatalystOne becomes either a custom picklist field (for structured competency names) or a multi-select picklist (for candidates with multiple competency tags) on the Candidate layout in Zoho Recruit. Rating and scoring scales differ between source and destination; we normalise scores to a common scale and store the original source value as a secondary field.

CatalystOne Succession Plans store relationships between a Position and one or more candidate Persons with readiness ratings. Since Zoho Recruit is a recruiting ATS rather than a succession planning tool, we map succession data as a custom module (Succession Candidates) linked to the Job Opening, or as custom fields on the Job Opening itself for organisations with a small succession candidate pool. Readiness ratings migrate as picklist values in a custom Readiness field.

CatalystOne Performance Review records carry effective dates, reviewer assignments, ratings, and custom review template content. We map the review cycle name, overall rating, and review date to custom fields on the associated Candidate record. Custom review template fields (which vary per customer due to CatalystOne's template flexibility) are enumerated during schema discovery and mapped individually to Zoho Recruit custom fields, subject to the edition field limit.

CatalystOne maintains a department hierarchy with cost centre assignments and reporting lines. We map this to Zoho Recruit's Department module, preserving the department name, parent department relationship (for nested hierarchies), and cost centre code as a custom field. Historical structure changes are preserved via effective-dated records; we migrate the most recent active structure as the current state in Zoho Recruit.

CatalystOne stores employee documents (employment contracts, certifications, policies) as binary attachments with metadata (type, date, owner). We export each document as a file alongside its metadata. In Zoho Recruit, attachments associate with the Candidate record. Document types that do not map directly to Zoho Recruit's attachment type taxonomy are stored as general attachments with the original document type label preserved as a custom field for classification.

CatalystOne links AD/SSO provisioning data and role/group assignments from HR master data. We export the current state of role assignments as custom picklist or text fields on the Candidate record. The offboarding automation logic (which CatalystOne manages through its managed integration services) does not migrate as it lives in the identity provider, not in CatalystOne's API-accessible data layer.

CatalystOne syncs HR data to payroll providers (Visma, SAP, and others common across Norway, Sweden, and Denmark). The integration configuration and field-to-field mapping rules are CatalystOne intellectual property and are not handed over on exit. We export the current payroll-related field values (salary, pay grade, bank details if stored in CatalystOne) as custom fields on the Candidate record and document the integration mapping logic as a written specification for the customer to re-implement in their target payroll system.

If the customer uses CatalystOne's time-tracking module, we export timesheet records and accrual balances as a custom module in Zoho Recruit linked to the Candidate record. However, many organisations route time data through a dedicated time and attendance system; we scope this object during discovery and include it only if the data lives in CatalystOne rather than a specialist time platform.

Organisations frequently add custom fields to core CatalystOne objects (Persons, Positions, Competencies) for industry-specific or company-specific data. These custom fields are not documented in any public reference and require a pre-migration schema discovery pass against the specific customer tenant to enumerate all active fields. We map each discovered custom field to an equivalent Zoho Recruit custom field, noting any edition-gated constraints (50 per module on Standard, 300 on Enterprise) that may require consolidating low-value fields into free-text notes during migration.