Migrate from Infor HCM to Crelate

Infor employee records from the Talent Management module map to Crelate Contact records as candidates. Standard biographical fields (name, email, phone, address) migrate directly. Infor's user-defined fields on talent profiles (defined in CMS470 or HCM configuration sessions) are mapped to Crelate custom fields on the Contact object. The customer's Infor admin identifies which employee records are active candidates versus internal HR records during scoping; we only migrate the active candidate population. Effective-dated job history from Infor is preserved as Crelate Activity records with date-ordered entries.

Infor Talent Science skills, certifications, and credential data attach to employee records as structured taxonomies. Crelate uses a tag-based keyword model for skills searchability rather than a hierarchical taxonomy. We extract skill names from Infor's structured fields, normalize them to plain-text keywords, and load them as Crelate tags on the Contact record. Certifications with expiry dates are mapped to Crelate custom date fields if the customer's Crelate admin configures them, or retained as tags with an expiry-note suffix. Taxonomy hierarchy is flattened during extraction since Crelate does not support nested skill taxonomies.

Infor HCM job requisition records from the Talent Management module map to Crelate Job records. Infor stores requisition status, department, headcount, and job description; we map these to Crelate's Job Title, Job Description, Status, and Department fields. Infor's requisition-to-candidate association (which candidates were sourced for which requisition) migrates as Crelate Job-Contact links. If Infor uses a separate approval workflow for requisitions, that workflow is documented for manual rebuild in Crelate since automations do not migrate.

Infor HCM org structures stored as hierarchical trees with cost center and location associations are mapped to Crelate Division and Team objects. The Infor parent-child org hierarchy is traversed during extraction, and department names are created as Crelate Divisions. Recruiters are assigned to Teams based on the Infor department-to-recruiter association. Position management headcount slots do not have a Crelate equivalent and are documented separately for the customer's workforce planning team.

Infor HCM pay history records include salary, bonus, and equity entries with effective dates. Crelate does not have a compensation or payroll object. We do not migrate compensation history to Crelate. If the customer needs to retain this data, we recommend a separate HRMS migration to a platform with compensation management (Workday, SAP SuccessFactors, Dayforce) or a manual archive export of the compensation history table from Infor as a CSV kept in the customer's records system.

Infor HCM benefit plans, enrollment elections, and coverage tiers live in the benefits administration module. Crelate is an ATS and recruiting CRM with no benefits management capability. Benefits enrollments do not migrate. We document the enrollment data volume during scoping so the customer can decide whether to retain it in an HR archive or a separate benefits administration platform.

Infor HCM performance documents, goal alignments, and review ratings from the Talent Management module do not have a Crelate equivalent. Crelate's ATS data model supports candidate notes and activity history but not structured performance review templates or competency ratings. Completed review cycles are documented as a flat record set in the migration inventory if the customer requires an audit trail, but they are not loaded into Crelate.

Infor Workforce Management time entries, absence balances, and accrual calculations are HRMS-layer data with no ATS analog. Crelate does not track time-off balances or attendance. We do not migrate time and attendance data. If the customer requires this functionality post-migration, a separate HRMS platform (Workday, UKG Pro, Dayforce) is recommended alongside Crelate for recruiting.

Employee documents stored in Infor Document Management (IDM) or SharePoint integration do not migrate. The IDM export tool exports only the current version of each document, not the full version history, and there is no Crelate document management module for HR records. Crelate supports candidate document attachments (resumes, cover letters) but not HRMS-type documents like contracts, policies, or performance records. We recommend a separate document archive strategy for any compliance-required records.

Infor M3 and HCM support alphanumeric, numeric, date, and text user-defined fields attached to master data records. These are defined in configuration sessions and can number in the dozens per object. We extract the UDF schema during discovery, map each UDF to the corresponding Crelate field type (text, number, date, picklist), and pre-create the Crelate custom fields before candidate data loads. UDF values migrate as custom field values on the mapped Crelate record.

Infor HCM records of hires, internal mobility events, and talent placements map to Crelate Placement records if the customer's Infor instance tracks placement outcomes. The Infor hire date, job title at hire, and department assignment become the Crelate Placement start date, job title, and division. Status (active, terminated, promoted) migrates to Crelate Placement status. Historical placements from prior years are loaded as closed Placement records.

Infor Talent Management interaction history—recruiter notes, interview outcomes, sourcing activity, and engagement timestamps—maps to Crelate Activity records on the Contact. Each Infor interaction timestamp becomes a Crelate Activity date; interaction type maps to Crelate Activity type (call, email, meeting, task). Notes and outcome comments migrate as Crelate Activity notes. Activity ordering is preserved by date during load. Bulk API or CSV import is used depending on record volume; chunking is applied for histories exceeding 50,000 activity records.