Heimdallone Docs
Administration

Go-live readiness

An admin-facing overview of what happens when an organization goes live on Heimdallone — what to expect, what to confirm in the app, and who performs the final steps.

AdminHR AdminPayroll AdminTenant Owner

This page explains, in plain terms, what "going live" means for an organization moving onto Heimdallone — what to expect, what to confirm inside the app, and who does what. It is not a technical runbook.

Your administrator runs the final steps

The final data load and the switch to the live system are performed by your administrator during a planned maintenance window. You don't run any commands — this page is so you know what's happening and what to check afterwards.

Before go-live

A few decisions are confirmed with the owner and HR/payroll leads first:

  • Who has a login, and whether anyone still needs a real email before go-live (no placeholder emails are ever created).
  • Tax/statutory details (TIN, NIS, dependents) for people whose pay depends on them.
  • Pay rules and shifts are set up and correct.
  • The biometric device will be registered during the window (see Biometric devices).

What happens during the window

The old system is briefly set to read-only so nothing changes mid-move.
Your administrator loads the organization's data into Heimdallone and verifies it.
Payroll figures are checked against the official rules and the historical record.
Sign-in, payroll, and attendance are smoke-tested before anyone is let in.
Once everything checks out, the organization is switched over to Heimdallone.

What to confirm in the app after go-live

Sign in works for you, and (where applicable) Google sign-in works. Migrated users see a one-time welcome notice.
Employees are all present, in the right departments, with the right managers — see Employees.
Payslips — historical payslips are present and unchanged; a current draft run matches expectations — see Payroll runs and Payslips.
Attendance records look right and the biometric device shows a recent successful sync with no stuck unmatched punches.
Finance figures (cost reports / trial balance) look sensible — see Finance.

If something looks wrong

  • Don't edit historical records directly. Historical payslips are immutable; changes go through a proper, audited correction.
  • Tell your administrator — go-live can be paused or rolled back to the old system if a check doesn't pass.
  • For migrated logins and access questions, see the migrated logins checklist.

What gets migrated

For the full picture of what data comes across and the safety guarantees, see Migration & cutover.

Your first sign-in (migrated users)

What migrated employees see the first time they sign in to Heimdallone v2 — the welcome notice and how to review and update your profile.

Developer / Operator

Architecture, module boundaries, quality gates, deployment, and how to keep docs in sync with code.

On this page

Before go-liveWhat happens during the windowWhat to confirm in the app after go-liveIf something looks wrong