Migrate your ELMO Suite data

Employee records carry standard fields: name, email, job title, department, location, start date, employment type, and status. We map these directly to the destination HRMS Contacts or Employees object. Custom employee properties are flagged for field-level mapping during scoping.

Each Employee has a linked employment history covering job title changes, department transfers, and status transitions. We preserve the full sequence as a chronological timeline in the target system.

Pay groups, pay rates, salary history, and superannuation contribution records require value mapping. ANZ-specific fields like TFN declarations and Super Fund details are mapped to equivalent fields in the destination or stored as custom properties where the target schema does not accommodate them natively.

Leave entitlements, accrual rules, and balance snapshots are source-system values that must be reconciled against the destination's accrual engine. We export the balance as of the migration date and store it as an opening balance record in the target.

Departments, cost centres, business units, and the reporting hierarchy are mapped to the destination org chart or equivalent structure. Reporting lines and manager assignments are preserved at import time.

Roster templates, recurring shifts, and historical time entries require transformation to match the destination's time-and-attendance schema. We chunk large rosters by pay period and map shift codes to the equivalent in the target system.

Review cycles, objectives, goals, and appraisal ratings are carried over, but the schema for ratings scales, competency frameworks, and custom review forms varies significantly. We flag custom review templates for manual post-migration review.

Course completions, certifications, and skill profiles are migrated as-is, but custom learning paths and completion due dates require field-level mapping. Completion status and expiry dates are preserved.

Onboarding tasks, document checklists, and assignee ownership are carried over where the destination supports a comparable onboarding object. Standalone task lists that do not map to a named object are exported as a flat task record.

Candidate profiles, applications, interview scores, and offer letters require mapping to the destination ATS schema. Position titles and department associations are reconciled during the field-mapping phase.

Survey responses, participation rates, and sentiment scores are exported as historical records. The destination may not support the same survey object type, so we store results as a structured custom object or tagged note block.

Expense claims, receipts, approval workflows, and reimbursement status are migrated as claims records. The destination's expense module may require re-mapping of category codes and approval routing.