Migrate your Infor HCM data

Employee records in Infor HCM include standard biographical fields, employment status, manager assignments, and effective-dated changes. We export these via file extraction or IDM tools and map them 1:1 to the destination employee object. Custom employee properties require field-level mapping.

Positions define headcount slots with grade, department, and salary grade associations. Infor stores position hierarchies separately from org units, and we preserve these relationships during migration by mapping position IDs and linked cost center codes.

Org structures in Infor HCM are stored as hierarchical trees with cost center and location associations. We traverse the parent-child tree and reconstruct the org chart in the destination system, preserving department-level custom fields.

Pay history records in Infor HCM include salary, bonus, and equity entries with effective dates. We extract these as a dated history table and load them into the destination as a compensation timeline, flagging any currency-conversion requirements for multi-country datasets.

Benefit plans, enrollment elections, and coverage tiers are stored in Infor HCM with plan-to-employee associations. We map these to destination benefit objects, but benefit plan identifiers differ between systems and require explicit crosswalk configuration.

Time entries, absence balances, and accrual calculations live in the Infor Workforce Management module. We extract time-off balances and leave histories, but accrual calculation rules (accrual rates, carryover limits) may not be exportable and require manual reconfirmation at the destination.

Performance documents, goal alignments, and review ratings are stored in the Talent Management module. We extract completed review cycles as flat records, but review template structures and competency taxonomies vary and require destination-specific configuration.

Skills, certifications, and credential data live in the Talent Science module and are linked to employee records. We extract these as tagged attributes, but skill taxonomies differ between Infor and destination systems and must be mapped explicitly.

Infor M3 and HCM support alphanumeric, numeric, date, and text user-defined fields attached to master data records. These are defined in sessions like CMS470 and can number in the dozens per object. We export field definitions alongside data and map them to destination custom field equivalents.

Employee documents (contracts, IDs, performance records) are stored in Infor Document Management (IDM) or attached via SharePoint integration. The IDM export tool does not include document version history, and a limit of 5,000 documents applies per export run. We recommend a separate document migration strategy using IDM's export zip functionality, and we do not include active SharePoint-lifecycle documents in standard HCM migration scopes.

Payroll journal entries and GL postings live in Infor LN's financial module, not in HCM proper. We extract payroll register data via file export, but pay calculation rules, tax jurisdiction configurations, and historical GL postings require Infor Financials expertise and are flagged as out-of-scope unless explicitly contracted.