Assess the real requirement

Start with an estate register: doors, locks, readers, controllers, power supplies, software, credentials, integrations, firmware and responsible teams. Review faults, unavailable parts, unsupported versions, user complaints and realistic growth.

Design and coordination decisions

Decide whether to retain, repair, migrate or replace each layer. Existing cabling, locks and credentials may be reusable only after inspection and compatibility checks. Protect current configuration and event data before altering a live system.

Testing, records and ongoing ownership

Plan coexistence, credential migration, temporary entry, testing and rollback. Alarm, CCTV, intercom, lift and gate connections must be retested end to end. Handover should update drawings, door schedules, backups and support responsibilities.

Decision checklist

• What user or operational problem must be solved?
• Which physical openings and related systems are in scope?
• Who approves, administers, maintains and reviews the result?
• What happens during power, network, controller or service failure?
• Which current product documents and licences support the proposed function?
• What drawings, schedules, backups, tests and training form part of handover?

Upgrade decision evidence

Implementation checklist

• Preserve current database and configuration
• Pilot representative doors and credentials
• Plan coexistence and temporary access
• Retest every integration end to end
• Update door schedules, drawings and training

Evidence to retain at acceptance

• Approved scope, assumptions and responsible parties
• Current models, versions, licences and interface description
• Door, event or workflow commissioning results
• Relevant network, power and failure behaviour
• As-installed drawings or schedules
• Administrator and operator training record
• Known limitations and outstanding actions

For Access Control Upgrades, acceptance should prove the customer-facing outcome, not merely that individual devices power on.

Plan migration and rollback before the first controller is removed

Export and verify the existing user database, access groups, schedules, door names, alarm permissions and integration settings where the current platform allows it. Record which data can be imported, which must be rebuilt and which old events need to remain accessible after cutover.

Stage credentials so authorised people can use the old and new systems only for the minimum controlled overlap. Define the point at which the old system can no longer be restored, who authorises that decision and how doors will operate if migration fails. After cutover, disable obsolete accounts and remote access, archive approved records, retest integrations and update support contacts.

Capture a before-and-after baseline

Before cutover, export or record active users, access groups, schedules, door names, integrations and known faults. After migration, reconcile each item and obtain approval for deliberate changes. This prevents an old programming error from being copied silently or a valid exception disappearing without explanation.

Questions to ask