Switching security software providers without losing your data

Switching provider is rarely blocked by the decision itself — most contractors know within a demo or two whether a new system is better than what they have. What actually slows a switch down, or stops it happening at all, is uncertainty about what happens to the records already sitting in the old system.

What actually needs to move

• –Licence history per officer — not just the current status, but the record of past checks and renewals
• –Screening files, complete, in a form that would still satisfy an assessor after the move
• –Training and induction records, including refresher history and what is coming due
• –Historical shift, attendance and incident records, in case they are needed for a client query or an investigation after the fact
• –Subcontractor and officer identity mapping, so "who was on site" queries still work for shifts worked before the switch

Losing any of these is not just an inconvenience. A screening file that cannot be reproduced for an officer who joined two years ago is a genuine gap the next time that file is requested, regardless of how good the new system is going forward.

Questions worth asking before you commit

Ask the new provider directly what format historical data can be exported to from your current system, and ask your current provider — separately — what they will actually let you take with you when you leave. See what to look for in security management software for why exit terms deserve attention before signing, not after.

Running two systems in parallel

A clean cutover on a single date is rarely realistic for an operation running continuous shifts. Most switches involve a period where both systems are technically live, and the risk in that window is a record being entered in one and not the other — which is exactly the kind of gap a licence check or an incident lookup can fall into. Plan the overlap deliberately, with one system designated as the source of truth for that period, rather than letting it happen informally.

What you can actually take with you

The question to settle before signing, not before leaving, is what export looks like: which records, in what format, and whether attached documents come with them. Screening evidence, training certificates and incident reports are frequently held as attachments, and an export that produces records without their attachments leaves the historically important half behind.

This matters more in security than in most sectors, because the records are ones that may need producing years later — potentially long after the relationship with the vendor has ended.

Running parallel on the difficult contract

When migrating, the instinct is to start with a simple contract. It proves little. Running one genuinely awkward account in parallel — multiple sites, subcontracted cover, a client with particular reporting requirements — surfaces the real gaps while there is still time to act on them.

Common mistakes

• –Not establishing export terms before signing
• –Exports that omit attached documents
• –Migrating simple contracts first and hitting hard cases too late
• –Retiring the old system before confirming everything transferred
• –Migrating unreviewed data and inheriting existing gaps
• –No parallel period on the contracts that matter most

What separates a clean migration

Settling the exit terms at the start rather than the end. What exports, in what format, whether attachments come with it, and how long the outgoing provider will keep data available — all far easier to agree while signing than while leaving.

The second is sequencing by difficulty rather than by ease: running the hardest contract in parallel early, where the gaps are still cheap to discover.

One practical test: ask for an export now

Before signing, ask a prospective vendor to show you an actual export from an existing customer's account — format, scope, and whether attachments come with it.

Screening evidence, training certificates and incident reports are usually held as attachments, and an export producing records without them leaves the half you most need behind. This is far easier to establish while they are selling than while you are leaving.

• –Establish export scope and format before signing
• –Confirm attachments export alongside records
• –Ask how long data stays available after termination
• –Run one difficult contract in parallel rather than a simple one
• –Confirm everything transferred before retiring the old system