Planning an EntraPass Server Migration

01

Inventory the current environment

Document the EntraPass edition and version, server operating system, database size, workstations, controller count, communications paths, integrations, scheduled tasks, reports, and any remote or web components.

• Confirm software and operating-system compatibility before choosing the target server.
• Identify how licensing or registration will move.
• Record service accounts and required permissions without placing passwords in the project notes.
• List firewall rules, hostnames, fixed addresses, and third-party dependencies.

02

Protect the source system

Create and verify a fresh EntraPass database backup. Keep the original server intact until the replacement has passed testing and the cutover is accepted. Define who can authorize rollback and how long the old environment will remain available.

03

Build a test plan

A successful login is not enough. Test operator access, live events, controller communications, door commands, schedule behavior, reporting, workstation connectivity, backups, and each integrated subsystem relevant to the customer.

04

Choose the cutover window

Match the change window to the site’s security risk and staff availability. Ensure the access control operator, IT contact, security dealer, and remote Kantech technician know their roles before changes begin.