Skip to main content

Moving from the old Oho

If your workforce was brought across from the previous Oho system (Duty of Care), your tenant didn't start empty — it started with your people, their credentials and the documents attached to them already in place.

That's a different first week from a tenant built from scratch. This page covers what came across, how old records look now, and what to expect in the first few days while Oho makes up its own mind about each credential.

The short version

Your workers and credentials are here. Credentials the old system had switched off came across switched off, marked Expired or Suspended. Nothing has a verdict yet — Oho decides that by checking each one against its register itself, and some verdicts will move in the first days.

What came across​

  • Workers — name, date of birth, contact details, employee ID and position, each filed under one organisation.
  • Credentials — type, reference number, issuing authority, issue and expiry dates, and a status worked out from the old record.
  • Documents — files attached to a credential came across with it.

What didn't​

  • Exemptions, declarations and qualifications are not part of the migration. If someone was formally excused from a requirement in the old system, record the exemption again here.
  • Records with no reference number. A credential is identified by its type and reference number, so a record with the reference left blank can't be filed against anything. These were left behind rather than guessed at.
  • Credential types with no equivalent in Oho. Where the old system used a type Oho doesn't recognise, the record was skipped rather than filed under something approximate. Ask support if a type you rely on is missing.

Anything in those last two groups is still in the old system. Nothing was deleted to make the move.

How old inactive records look now​

The previous system let an administrator switch a credential off. Those records came across, and they are the ones most likely to surprise you.

Each one arrives:

  • Switched off, so Oho doesn't re-check it. It sits on the worker's profile without consuming checks.
  • Marked Expired if its expiry date has passed, or Suspended if it had no expiry date or one still in the future.
"Suspended" here isn't a regulator's decision

Suspended is the closest word Oho has for "the old system had this switched off". On a migrated record it usually means an administrator deactivated the claim years ago — not that Blue Card Services, AHPRA or a screening unit suspended anybody.

To tell the difference, open the credential and look at Source System on its overview. A migrated record names the system it came from; a real withdrawal came from a register check and has the check in its history.

Because Expired and Suspended are the two words that mean "the issuer took this away", these records are counted on the Withdrawn by the issuer card on your Compliance Overview. On a freshly migrated tenant that number can be in the hundreds on day one, and most of it is history rather than anything to act on. Work through it once, deal with anything that's about a current worker, and it stops being noise.

Verdicts move in the first few days​

Migrated credentials arrive with no verification result at all. The migration deliberately doesn't assert that a card was valid — it didn't check, so it doesn't say.

Two things follow from that:

  • Workers can read At Risk before anything has gone wrong. A credential nobody has checked yet is "waiting on a result", which holds a worker at At Risk rather than Compliant. They move once the first check comes back.
  • The first check stands on its own. Where Oho has already seen a credential pass, a single "Not found" from a flaky register doesn't flip the worker — but a migrated credential has no such history to lean on, so its first answer is the one that counts. When a "Not found" result holds explains the rule.

So expect some movement in both directions in the first week as each credential gets its first real answer. A worker who moves to May not engage and back the next day isn't a bug in your data — it's two register answers on two days.

Organisations are set at import​

Each worker was filed under one organisation as part of the migration, and that is where they stay. The organisation shows on the worker's profile but isn't editable there, so if someone landed in the wrong one, ask support to move them rather than hunting for a field.

Organisations also decide what your administrators can see. Someone who signs in and finds half the workforce missing usually has access to a subset of organisations rather than a permissions problem — see Roles and access.

Your first week​

  1. Check your users and their access. Confirm each administrator can see the organisations they're responsible for.
  2. Open the Compliance Overview. Read it as a starting position, not a verdict — much of it is still waiting on first checks.
  3. Work the Withdrawn by the issuer card once. Separate the legacy records from anything about a current worker.
  4. Connect your verification sources. Until a register is connected, nothing re-checks on a schedule, and credentials stay on whatever the import gave them.
  5. Re-record anything that didn't migrate — exemptions in particular.

What's next​