Migrate from Infor HCM to Recruit CRM & ATS

Infor HCM talent profiles containing skills, certifications, and credential data from the Talent Science module map to Recruit CRM candidate records. Skill taxonomies differ between Infor and Recruit CRM, so we extract skills as tagged attributes and map them to Recruit CRM's skill fields and custom candidate tags. Any Infor competency ratings or proficiency levels migrate as custom fields on the Candidate record. This is the primary overlap object between Infor HCM's talent management module and Recruit CRM's candidate profile.

Completed performance review cycles and goal alignments in Infor HCM's Talent Management module do not map directly to any Recruit CRM object. We extract review summaries as dated notes and attach them to the corresponding Candidate record in Recruit CRM as an internal note. Review template structures, competency matrices, and rating scales do not migrate because Recruit CRM has no performance management schema. We flag this as a data-loss boundary during scoping.

Infor HCM positions with external-facing job requisition data map to Recruit CRM job records. Position title, department, location, employment type, and job description fields extract from Infor and load into Recruit CRM's Job object. Headcount slots and internal position hierarchies (headcount budgeting, approval workflows) do not migrate because Recruit CRM manages placement volume through job order records, not position budgets.

Infor HCM organizational hierarchies map partially to Recruit CRM's client structure. Cost center information from Infor maps to Recruit CRM Company/Client records. The hierarchical parent-child tree is preserved as a flat client account structure in Recruit CRM; multi-level org chart traversal is not applicable in Recruit CRM's agency-focused data model. We recommend the customer's admin review the client mapping during sandbox validation.

Infor HCM employee records do not map to Recruit CRM candidates in a standard migration. However, if the customer uses Infor HCM's Talent Management module to track internal applicants who have applied for open positions, those applicant records can migrate as Candidate records in Recruit CRM. Standard employee biographical data (biography, emergency contacts, bank details, employment contracts) does not migrate because Recruit CRM stores candidate profiles, not employee records. We explicitly scope out all employee personal data during discovery.

Infor M3 and HCM user-defined fields (defined in CMS470 sessions) attached to talent, position, and organizational records map to Recruit CRM custom fields on Candidate, Job, and Company objects. We extract all UDF definitions during discovery, map each to the equivalent Recruit CRM field type (text, numeric, date, picklist), and pre-create the schema before data import. Any Infor UDFs with no Recruit CRM equivalent are flagged for the customer's admin to evaluate for mapping or omission.

Infor HCM pay history records (salary, bonus, equity entries with effective dates) have no equivalent in Recruit CRM's candidate data model. We do not migrate compensation history to Recruit CRM. If the customer needs this data retained, we can export it as a dated CSV table and store it as an archive file outside the Recruit CRM migration scope. This is a hard data-loss boundary that we document explicitly during discovery.

Benefit plans, enrollment elections, and coverage tiers in Infor HCM have no Recruit CRM equivalent. Recruit CRM does not store benefits data. We do not migrate benefit enrollments. The customer's HR team should retain this data in Infor HCM or a downstream HRMS if statutory retention requirements apply.

Time entries, absence balances, and accrual calculations from Infor Workforce Management do not migrate to Recruit CRM. Recruit CRM has no schema for time tracking or absence management. We exclude these records from migration scope and recommend the customer's HR team evaluate Workday, BambooHR, or a payroll platform for ongoing absence and accrual management post-migration.

Infor Document Management (IDM) files attached to talent profiles and employee records migrate as attachments on the corresponding Recruit CRM Candidate record. We note that IDM export only retrieves the current document version, not version history. Candidate resumes extracted from Infor HCM talent profiles migrate as Resume attachments in Recruit CRM. SharePoint-integrated document exports are limited to 5,000 documents per export run.