MSAMM
Back to course

Implementing Global HR: From Enterprise Model to Live Workforce · Module 16 · HCM Data Loader and Data Migration

File structure and business objects

Lesson 155 of 175 · 3 min

The file is a set of .dat files in a zip — one per business object, each with a metadata line and data lines. The metadata line declares what the columns are, and the column order in the data must match it. That is the first thing to check when a file that looks right loads nonsense. Business objects have components. "Worker" is not one row: it comprises person, name, address, work relationship, assignment and more. One object, many components — and a partial worker is a real state you can end up in. Keys decide whether a second load updates or duplicates. Source keys, user keys, GUIDs — how records are identified and matched on reload. Sit with that, because a migration is never one load. You will load, find something wrong, correct the file and load again — and whether that second load fixes your data or doubles…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Implementing Global HR: From Enterprise Model to Live Workforce, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 16 · HCM Data Loader and Data Migration

  1. 1Migration strategy: what to bringFree preview
  2. 2The loading toolset
  3. 3File structure and business objects
  4. 4Your first load
  5. 5The workforce structures load sequenceFree preview
  6. 6Loading workers
  7. 7Spreadsheet Data Loader
  8. 8Diagnosing failures
  9. 9Reconciliation and cutover
  10. 10What breaks
  11. 11Lab: migrate the workforce and reconcile it