Migrate from Infor HCM to Zoho Recruit

Infor HCM's employee records from the Talent Management module serve as the candidate source. We extract biographical fields (name, email, phone, address), employment eligibility status, and any recruiter-assigned ratings. The Infor talent profile's skills and certifications map to Zoho Recruit Candidate tags. Where Infor stores a skills taxonomy from Talent Science, we flatten it into tagged attributes and apply them as candidate tags during load. If the Infor record has no email address, we flag it for manual enrichment because Zoho Recruit requires a contact method on candidate records.

Infor HCM position management records with active headcount slots map to Zoho Recruit Job Opening records. We extract the position title, department, job description, hiring manager assignment, and requisition status. Infor's position approval chain (hierarchical approval workflow tied to ERP GL headcount budget) has no equivalent in Zoho Recruit and is excluded from migration; we document it as a manual workflow to rebuild in Zoho Recruit's Blueprint builder if needed.

Infor HCM users with recruiter or hiring manager roles map to Zoho Recruit Users. We resolve by email match. Zoho Recruit requires at least one additional user to be present before CSV user import; we provision a temporary admin account if the destination is blank, then import all source users by email. Users with separate existing Zoho Recruit accounts must close those accounts before migration import proceeds per Zoho Recruit's migration tool documentation.

Infor's Talent Science module stores skills, certifications, and credential data as tagged attributes linked to employee records. Zoho Recruit stores skills as Candidate tags (multi-select tagging). We extract the full skills taxonomy from Infor, deduplicate, and create matching tags in Zoho Recruit before candidate import. Skill taxonomy hierarchies in Infor (skill groups, proficiency levels) are flattened into a single tag string; any proficiency level metadata is stored in a Zoho Recruit custom field if the customer's plan supports it.

Infor Talent Management interview and assessment records map to Zoho Recruit Interview records. We extract the candidate reference, job opening reference, interviewer name, scheduled datetime, interview type, and feedback score. Interview disposition notes and rating values migrate to the Zoho Recruit Interview Feedback form as custom fields if the customer's Professional or Enterprise plan supports them.

Infor records tracking which candidate applied to which position map to the association between Zoho Recruit Candidate and Job Opening. We create the association by matching the Infor candidate reference and job opening reference. If Infor tracks application stage (applied, screening, shortlist, offer, rejected), we populate the corresponding Zoho Recruit pipeline stage on the association.

Infor M3 and HCM support alphanumeric, numeric, date, and text user-defined fields attached to master data records. We extract every UDF referenced on employee and talent records and map them to Zoho Recruit custom fields by type. Zoho Recruit Standard edition allows 50 custom fields per module; Professional and Enterprise allow 300. If the customer has more than 50 UDFs on a given object, we prioritize migration of active or reporting-relevant fields and document the remainder for manual field creation post-migration. Custom fields are not available in Zoho Recruit Free edition.

Infor HCM Enterprise includes RAVE recognition and Talent Science engagement analytics. These numeric scores and recognition badges have no native Zoho Recruit equivalent. We store them as numeric custom fields on the candidate record for reporting and reference. Engagement trend data (time-series analytics) does not migrate as a structured object; we document the latest score as a static value and flag the trend data for the customer's analytics team to reconstruct from Infor exports.

Infor HCM organizational units and department hierarchies map to Zoho Recruit Departments. We extract the department name, cost center, and parent department for hierarchical reconstruction. Zoho Recruit Standard and above include department hierarchy support. If the customer's Infor deployment uses complex multi-level hierarchies with cost center associations, we document the full tree for manual rebuild in Zoho Recruit's department structure post-migration.

Employee documents (contracts, certifications, performance records) stored in Infor Document Management (IDM) are linked to candidate records in Zoho Recruit as attachments. The IDM export tool only exports the current version of each document, not version history. We extract current-version documents as files and attach them to the corresponding candidate record during migration. Any compliance requirement for document version history is flagged and handled via a supplemental IDM extraction documented separately.

Infor HCM stores salary, bonus, and equity entries with effective dates in a compensation history table. Zoho Recruit's ATS model does not include a compensation or payroll object. This data does not migrate. We flag each compensation history record as excluded and document the full history table in the scope deliverable for the customer's finance and HR team to retain or re-enter manually if required.

Benefit plans, enrollment elections, and coverage tiers stored in Infor HCM have no equivalent in Zoho Recruit's ATS data model. Benefits administration is not within Zoho Recruit's scope. This data does not migrate and is documented as excluded in the scope deliverable.