Start with operating decisions
Software configuration becomes easier when policy owners agree how joining, attendance exceptions, leave, approvals and payroll cut-offs should work. Document the current rule, the intended rule and who can approve a change.
- Name an executive sponsor and operational owners
- Separate must-have launch scope from later optimisation
- Record exceptions that cannot be inferred from spreadsheets
Treat migration as a controlled product
Map every source field to an owner, a validation rule and a destination. Use a rehearsal import before launch, compare control totals and preserve the source snapshot used for sign-off.
- Validate employee identities and reporting lines first
- Reconcile balances and effective dates
- Keep rejected rows visible and correctable
Prove complete workflows
A green page is not launch evidence. Test real role journeys from request through approval, notification, audit and downstream output, including stale sessions and rejected actions.
- Use at least two tenant-safe test companies
- Test mobile and narrow screens
- Agree rollback and support ownership
Adapt the checklist to your policies, legal advice, workforce and implementation scope. A product demonstration should prove the representative workflows you identify here.