Editorial dates are assigned for this collection; they do not represent original publication or author approval dates. The update date records this site revision.
Audit the current groups
List active users, visitor rules, schedules and exceptions. Remove stale permissions with customer approval before copying groups to the new platform.
Choose a manageable cutover
Test readers and credentials at representative openings, plan temporary parallel operation if supported, and coordinate the change with users and the help desk.
Confirm the final rights
Sample actual access by role, verify denied entry and audit logs, then retire old credentials under an approved process. Preserve records needed for support.
Working example: The scenario below is illustrative. It describes a practical design and review method, not a completed customer project or a guaranteed result.
A working scenario
A new reader can accept modern credentials, but hundreds of old badges and a tenant turnover schedule make immediate cutover impractical.
The decision to make before buying
Inventory credential types, reader compatibility, issuance authority, revocation, enrollment, shared entrances and overlap risks. Decide how long a mixed population is acceptable.
A useful acceptance test
Pilot representative badges and mobile credentials at selected doors; test deactivation, denied entry, offline behavior and batch migration reporting.
What the owner should receive
Keep a migration roster with privacy protections, reader map, cutover gates, help-desk script and a firm plan to retire weak legacy formats.
Questions owners ask
Why can dual credential support be risky?
Keeping old media active for convenience may retain a weaker authentication path even after new readers are installed. Decide the overlap period, which entrances accept each format and how exceptions expire. Confirm any current policy or compliance requirement with the owner.
What does a pilot prove?
It should cover representative users, different reader generations, offline behavior, enrollment, lost credentials and deactivation. Record incompatibilities and desk-support workload before the broad issuance campaign. A single successful badge tap is not a migration plan.