Migrate from Infor HCM to BambooHR

Infor employee records map directly to BambooHR employee records. We extract biographical fields (name, date of birth, hire date, termination date, employment status, employee number), emergency contacts, and address data via file export. The BambooHR employee record is the parent; we map the Infor employment status values (Active, Terminated, On Leave, etc.) to BambooHR's status list, and we flag any Infor-specific status value that requires a custom BambooHR field for accurate representation. We load employees after department and job title lists are in place so that the department and job title references resolve at insert time.

Infor org structures are stored as hierarchical trees with cost center and location associations. We traverse the parent-child tree and flatten it into BambooHR department records, preserving the top-level org unit as the root department. Cost center values that have no BambooHR equivalent become either department names or a custom department field, depending on the customer's preference during scoping. The migration must load departments before employees so that the department reference on each employee record is valid at insert time.

Infor positions define headcount slots with grade, salary range, and manager associations. BambooHR does not model positions as a separate object; instead it uses a flat job title list attached to the employee record. We extract distinct Infor position titles, merge them into a deduplicated BambooHR job title list, and map the employee's primary position title to the BambooHR job title field. Salary grade information from Infor positions migrates as a custom field in BambooHR rather than as a structured grade table because BambooHR does not support a native position-budget model.

Infor stores compensation changes as effective-dated rows (salary, bonus, equity, pay rate changes). We extract the full compensation history table in ascending effective-date order and load each row as a BambooHR job history entry with the corresponding effective date, compensation amount, and pay type. BambooHR's job table supports multiple entries per employee with effective dates, which matches Infor's history model. We flag the Infor pay frequency (annual, hourly, salaried) and map it to BambooHR's pay rate type. Multi-currency compensation entries require currency conversion or storage in a custom field; we flag this during scoping.

Infor benefit plans, enrollment elections, and coverage tiers map to BambooHR benefits tracking. We extract the current benefit elections per employee (health, dental, vision, 401k, etc.) and load them as BambooHR benefit records. Benefit plan identifiers are Infor-specific and will not match any BambooHR plan list, so we create custom benefit type fields and enter plan names as free text. Historical enrollment elections (prior year elections) migrate as a benefits history note or custom text field. We do not migrate the underlying Infor benefits administration configuration because BambooHR's benefits module is for tracking elections, not administering plan rules.

Infor Workforce Management stores time entries, absence balances, and accrual calculations. We extract current accrual balances (PTO, sick, personal) and load them as BambooHR time-off balances at the employee's hire date or the migration effective date. Infor accrual calculation rules (accrual rates, carryover limits, negative balance policies) are Infor-specific and do not transfer to BambooHR; we document them in a written benefits administration configuration summary for the customer's HR admin to rebuild in BambooHR's time-off policy settings.

Infor Talent Management stores completed review cycles, ratings, and goal alignments as structured records. We extract completed review data as a flat BambooHR performance record with the review date, overall rating, and reviewer name. Infor competency ratings and goal descriptions migrate as custom fields in BambooHR. Review template structures, rating scales, and competency frameworks are Infor-specific and do not map directly to BambooHR's performance module; we deliver a written performance template inventory for the customer's admin to configure in BambooHR.

Infor Talent Science stores skills, certifications, and credential data linked to employee records. We extract these as tagged attributes and map them to BambooHR custom fields on the employee record. Skill taxonomies differ between Infor and BambooHR; we create a custom skill taxonomy in BambooHR that matches the customer's most-used Infor skill tags during scoping. Certifications and credentials migrate as custom fields with expiration dates where applicable.

Infor M3 and HCM support alphanumeric, numeric, date, and text user-defined fields defined in CMS470 sessions. We extract every UDF attached to employee, position, and compensation records and map each to the equivalent BambooHR custom field type (text, number, date, dropdown, checkbox, etc.). Infor multi-select UDFs require a custom field in BambooHR. We pre-create the custom field schema in BambooHR before any employee data loads so that the fields are available during import. Any Infor UDF that has no equivalent BambooHR field type is documented as a custom-field gap for the customer to resolve.

Employee documents stored in Infor Document Management (IDM) or SharePoint integration do not migrate through the standard IDM export because the export tool only exports the current version of each document, not the full version history. If document version history is a compliance requirement, we recommend a supplemental extraction through the customer's IT team. We migrate current-version documents as file attachments on the corresponding BambooHR employee record where the employee file feature is available, but we flag this as a partial migration with version history loss.

Infor payroll journal entries and GL postings live in Infor LN's financial module, not in HCM proper. Pay calculation rules, tax jurisdiction configurations, and earnings codes are Infor LN-specific and do not have equivalents in BambooHR's payroll add-on module. We do not migrate payroll transaction history. We extract the employee's current pay rate, pay frequency, and exempt/non-exempt FLSA status and load those into BambooHR's compensation section as the current active pay entry. Multi-jurisdiction tax withholding configurations are not portable.