Field maps and opening balances: checks before you load
Since release 20261115 a field map’s To is chosen from the fields the object accepts, its Arguments are checked against How, and Check the rows on an opening-balance step checks accounts exactly as Post does.
Platform › Operations › Legacy Migration.
- Field Maps: To is a pick-list of the fields the chosen object accepts. It is free text only where the object declares no fields. Saving a To the object does not have is refused and the valid fields are named.
- Arguments must fit How: value_map, constant, concat and lookup each need their own shape, and a wrong one is refused when you save, not when you load.
- Opening-balance steps: Check the rows looks up every account the way Post does and refuses a missing or heading account. TOTAL lines and zero rows are left alone.
- Legacy payroll registers: each source system’s payslip history columns map onto the payroll archive, so a year of payslips is no longer collapsed into one.
Employee codes in migration files (since release 20261116b)
In Field Maps, map the file’s employee column (for example “Employee No”) straight to the Employee field. Copy or Trim is enough; Lookup is not needed. When you Check the rows in the Migration Cockpit, each code is matched to the employee in this company by employee number, or by the code the employee was migrated with. Rows whose code matches nobody, or several people, are listed as rejected with the code shown.