Service — Migration

Security Configuration Migration

Moving doors, cardholders, cards, and panels from one PACS to another is a live-data operation on your building's access control — we treat it that way.

What moves

Every credential, every door, mapped before anything cuts over.

1
Doors & panels
Controller configuration, door groups, schedules, and hardware wiring maps carried over and verified device by device.
2
Cardholders
Every cardholder record, role, and access-group assignment reconciled against the source system before migration.
3
Cards & credentials
Card formats and credential data re-encoded or re-issued to match the destination platform's requirements.
4
Access rules & schedules
Time-based and role-based access rules rebuilt to match, not approximate, current behavior.
SOURCE PACS 412 doors 6,204 cardholders 88 panels verified DESTINATION PACS 412 doors 6,204 cardholders 88 panels (3 pending)

Reconciled record-for-record before the source system is ever decommissioned.

Why this is different from a data export

The risk isn't the migration — it's the gap.

A door that silently loses its access rules for even an hour is a security incident, not an inconvenience. Our process is built around never creating that gap.

Parallel run

Source and destination systems run side by side before cutover, with discrepancies flagged and resolved, not assumed.

Reconciliation, not just export

Every door, cardholder, and panel is verified against the source of truth — a completed import is not treated as a completed migration.

Rollback plan at every stage

Every cutover step has a documented path back to the previous state, decided before migration night, not during it.

Migrating off a legacy PACS?

We'll scope the door and cardholder count, the target platform, and a cutover plan with zero unplanned downtime.

Talk to us