Understand HRM migration 130
Understand the v1.3.0 tenant schema reconciliation for authoritative employee records, controlled amendments and document versioning.
Exact navigation Admin Area → Setup → Modules → Human Resource Management → Upgrade Database
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.
What you need before you start
- Access to Admin Area → Setup → Modules → Human Resource Management → Upgrade Database.
- The Human Resource Management: View capability or administrator access.
- The correct employee, record, period or authorised evidence.
How to do it
- Run the normal module database upgrade after migration 120 is available.
- Confirm migration 130 completes.
- Open Human Resources → Employee Record Centre.
- Open an employee and verify Current Record, Approval Queue, Documents, Change History and Automation tabs.
- Open an existing document and confirm a version history is present after the upgrade backfill.
Fields and options
hrm_employee_record_dataEncrypted authoritative current-record payload and record version.
hrm_employee_change_requestsPending/approved/rejected/applied/failed controlled amendments.
hrm_employee_document_versionsImmutable file-version history and active/superseded/withdrawn state.
hrm_employee_sync_logsPer-target synchronisation success/failure evidence.
Profile/document columnsLinks, work email, profile version, current document version and change timestamps.
What the module checks
- Existing non-deleted employee documents are backfilled as initial versions.
- Existing profiles are linked to master employee and onboarding records when matching evidence exists.
- The migration is current-tenant only and does not alter unrelated tenant databases.
What happens next
The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.
Troubleshooting
- If the control is missing, confirm the required HRM permission and module version 1.3.0.
- If saving fails, correct the exact field or state named in the validation message.
- If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: employee record centrehuman resource management version 1 3 0