Migrate from OnePoint HCM to Zoho Recruit

OnePoint Employee records map to Zoho Recruit Candidate records. We extract employee first name, last name, email, phone, hire date, department, job title, employment status, and work location as the candidate base. Any employee records without a last name in OnePoint must be flagged with a placeholder value (not provided or none) because Last Name is a mandatory field in Zoho Recruit that cannot be left blank during import; records with missing mandatory fields are ignored by the import wizard.

OnePoint assignment-level data including assignment type, HR assignment status code, system person type, and original hire date map to custom Candidate fields in Zoho Recruit. Assignment status (active, terminated, leave of absence) migrates as a picklist field on the Candidate record. We preserve the original OnePoint assignment effective date to support compliance and tenure reporting in Zoho Recruit.

OnePoint departments, cost centers, and locations extract as reference data and load into Zoho Recruit's Department module before candidate records. Department hierarchy and reporting relationships in OnePoint do not have a direct equivalent in Zoho Recruit's flat Department structure, so we flatten the org tree and map the primary department assignment per employee to the Candidate record for sourcing context.

OnePoint location records (office addresses, regional sites, remote-work designations) map to Zoho Recruit's Location module. Location is linked to Job Openings in Zoho Recruit, so we establish Location records before importing or creating job opening records.

OnePoint user accounts and manager assignments map to Zoho Recruit Users. We resolve users by email match against the Zoho Recruit User table. Any OnePoint user with an existing separate Zoho Recruit account must close that account before import; Zoho Recruit's import wizard rejects users who already have a Recruit account. This step requires coordination with the customer's IT team to provision Zoho Recruit licenses before migration begins.

If OnePoint contains internal job postings, requisitions, or position records tied to the HR module, these map to Zoho Recruit Job Opening records. Job Opening title, department, location, employment type, and description map from OnePoint position or job record fields. Active job openings from OnePoint become open Job Openings in Zoho Recruit; closed positions become closed Job Openings with hiring timeline preserved.

Employee document files accessible via OnePoint's file management (onboarding paperwork, signed forms, certifications) export as file attachments and associate to the corresponding Candidate record in Zoho Recruit. We export available document file types and map them to Candidate Attachments. Zoho Recruit supports file attachments on Candidate records up to the storage limits of the account's edition.

OnePoint salary, pay grade, and compensation change history do not map to any native Zoho Recruit object. We extract the most recent compensation entry (base salary, pay frequency, pay grade) as custom fields on the Candidate record for reference purposes only. Historical compensation timelines and earnings records are not migrated because Zoho Recruit does not have a payroll or compensation module. We flag these as out-of-scope and note that historical payroll data should be retained in OnePoint or exported to a separate payroll archive.

Benefits plan assignments, coverage tiers, and carrier connections have no equivalent in Zoho Recruit's ATS schema. These records are out of scope. We export a benefits enrollment summary as a supplemental data dictionary and recommend the customer retain OnePoint access for benefits administration or migrate to a dedicated benefits administration platform.

PTO, sick, and leave accrual balances calculated by OnePoint's rules engine do not migrate to Zoho Recruit. Zoho Recruit does not track leave balances or time-off data. We recommend the customer retain accrual records in OnePoint or migrate them separately to a time-and-attendance system if leave tracking is required post-transition.

Historical payroll runs, earnings, deductions, and tax withholdings are out of scope for Zoho Recruit migration. Zoho Recruit's ATS schema has no payroll or compensation history objects. We recommend a separate payroll migration to Zoho Payroll or a dedicated payroll platform if the customer plans to consolidate onto Zoho's HCM suite.

Performance reviews, ratings, and goals from OnePoint map to custom fields on the Candidate record if the customer wants to preserve performance history for internal hiring or promotion pipelines. We extract the most recent performance rating and review date as custom Candidate fields. Historical performance timelines are packaged as supplemental data export. Zoho Recruit does not have a native performance management module.

Any OnePoint custom objects or configuration tables (custom benefit types, variable pay plans, certification tracking, compliance codes) that the customer wants to preserve are mapped to Zoho Recruit Custom Modules. Custom modules in Zoho Recruit require Standard edition or above and must be created via Setup > Customization > Modules before data import. We pre-create the schema and all custom fields before migration begins.