Case studies

An MSP director, on HaloPSA since April 2026

Five months on HaloPSA. About 45 warning signs on the first scan.

~45

warning signs on the first scan

Moved to HaloPSA
April 2026
Of history at scan time
~5 months
Typical scan time
About a minute

The worry: is five months enough?

The director had moved the business onto HaloPSA in April 2026, so by the time he ran the scan it held about five months of tickets.

The fair question was whether a tool that compares clients against their own history would have anything to say yet.

What the scan found

He ran the free, read-only scan himself. It picked up around 45 warning signs across his client base.

Handover works out each client's normal range from about six months of its tickets: three to learn what usual looks like, and the latest three to compare against it. A business five or six months into a new PSA is right at that line, which is enough for most clients that raise tickets regularly.

Some checks need no history at all. Contracts coming up for renewal, quotes left waiting and active contracts with no recent activity are checked from the first day.

Why that matters after a PSA move

The months after a migration are when things slip: tickets land in the wrong queue, owners are not set, contracts are half moved across. That is the kind of thing the scan's housekeeping checks look for, alongside the warning signs.

Handover is also honest about what it cannot measure yet. Where a client has too little history to compare, it says so instead of guessing, and a sign measured on a short history is labelled worth a look rather than strong.

You do not need years of PSA history to start. You need a read-only API key and a minute.

How many warning signs are in your PSA?

Free, read-only scan. No card, nothing to cancel.

Run your free scan