Replace an unsupported access-control controller before its failure disrupts entry, but do not treat the controller as the whole system. Inventory the readers, locks, power supplies, credentials, network links, software and door conditions that depend on it. Then prioritize parts that cannot be supported, recovered or safely worked around, and test the replacement door by door.
In This Article
- What should we replace first when controller support ends?
- How can we tell whether a reader, lock or power supply needs replacement?
- What should we check before choosing a replacement controller?
- How do we upgrade without disrupting tenants and staff?
- What should Atlanta businesses include in an access-control replacement plan?
- Frequently Asked Questions
What should we replace first when controller support ends?
Start with the controller and its software or licensing dependencies. Confirm the exact model, operating version, support status, configuration backup, and whether replacement equipment can use the existing configuration. An unsupported controller may still operate, but a fault can leave you without a vendor-supported repair path or a reliable way to restore settings.
Next, identify components that depend on that controller: readers, locking hardware, input devices, power supplies, communication modules and any interface used by another building system. The goal is not to replace every device automatically. It is to find the components that will fail with the controller, cannot communicate with its replacement, or have no practical service path.
Credentials and access permissions deserve a separate review. A hardware migration can expose gaps in who has access, which doors they can use and how access is changed when a person's responsibilities change. Record the current permission structure before migration so the new system does not carry forward outdated access by default.
Three dependency groups to map: door hardware, controller and software, and power or network connections.
Replace the unsupported core and any incompatible dependencies first. Keep components with a verified support and compatibility path only when they meet the operating need.
How can we tell whether a reader, lock or power supply needs replacement?
Test each door as a working assembly, not as a line item on an equipment list. Confirm that a valid credential is read, the controller receives the event, the lock responds as intended, and the door returns to its normal secured state. Document intermittent behavior as well as complete failure; a door that works only after repeated attempts is still an operational problem.
Inspect the physical condition and compatibility of the reader, locking hardware, door position or request-to-exit inputs, and power supply. A new controller cannot correct a binding door, damaged wiring, unstable power or hardware that the replacement system cannot control. Trace the fault to its dependency before approving a part swap.
Check how the system behaves during loss of power or network communication, and confirm the intended operation with the building's responsible parties. These behaviors can affect entry, security procedures and other building operations. Do not assume a replacement design or setting is acceptable for life-safety use; coordinate applicable requirements and authority review for the specific project.
For Atlanta-area properties, involve facilities, IT and the people responsible for building operations before changing doors or credentials. In a multi-tenant building, a door schedule and tenant access expectations may be different from a single-office setup. Agree on who can approve access changes and how occupants will be informed before work starts.
Door testing identifies the actual failure path. Replace the failed dependency, not the symptom alone.
What should we check before choosing a replacement controller?
Begin with an accurate inventory. Record controller model and location, connected doors, reader types, lock hardware, power source, network connection, software version, credential format and any integrations. Mark unknowns explicitly. A partial inventory is better than assuming that two similar doors have identical wiring or configuration.
Then define the operating requirements. Which doors must remain available during the work? Who needs access, at what times, and who authorizes changes? What should happen if power or network connectivity is interrupted? Which existing components must remain, and which are candidates for replacement? These answers shape the scope more reliably than choosing a controller by feature list alone.
Ask the installer or provider to document compatibility, configuration migration, credential handling, functional tests and handoff responsibilities. Clarify which hardware is included and which conditions require separate work, such as door repairs, wiring corrections or changes to another building system. A quote should make those boundaries visible before installation.
For systems already in place, GDS Technology supports existing Lenel OnGuard access-control environments and provides scoped access-control maintenance and electronic access-control system work. The appropriate scope depends on the installed equipment, door conditions and agreed responsibilities. No controller or platform should be treated as a fit before that review.
A sound replacement decision starts with operating requirements and a verified compatibility path.
How do we upgrade without disrupting tenants and staff?
Plan the work around actual door use. Identify busy periods, deliveries, visitor procedures, after-hours access and any doors that cannot be unavailable at the same time. Coordinate the sequence with facilities, IT, security administrators and tenant representatives. A technically successful cutover still creates avoidable disruption if people do not know which entrances or procedures have changed.
Before work begins, preserve available configuration and document the current door behavior and permissions. Set a clear change window, identify who can authorize access changes, and agree on a temporary procedure for any door affected during installation. Do not rely on an informal workaround that only one person knows.
After installation, verify each door in normal operation and test the agreed failure conditions. Confirm credentials for representative user roles, door status reporting where included, and the handoff of configuration and service records. Track unresolved items with an owner and next step rather than calling the migration complete because the controller powers on.
A professional-services customer described a door sensor issue this way: "GDS followed up the next day to make sure the door sensor issue is resolved. That kind of attention shows real customer service." The example is a reminder to include follow-up in the operating plan: confirm that the reported door condition is actually resolved after the change.
Coordinate the sequence, verify the doors and close the loop with the people who use them.
What should Atlanta businesses include in an access-control replacement plan?
In Metro Atlanta, buildings may have different operating needs across office, medical, professional-services and multi-tenant settings. The same controller choice will not fit every property. Account for the specific doors, occupants, work schedules and building responsibilities at the site, including how facilities and IT divide ownership.
Georgia's data-breach notification requirements and applicable industry obligations can shape how a business governs information and access. They do not make a particular controller or access-control product a compliance solution. Keep the review practical: decide who may enter, who can change permissions, how those changes are documented, and how access is removed when it is no longer needed. For legal interpretation, consult qualified counsel.
Use this checklist to turn an end-of-support notice into a controlled project:
- Confirm the controller and software support status, backup options and replacement path.
- Map every connected door, reader, lock, input, power source and network dependency.
- Record current credentials, roles, permissions and the process for approving changes.
- Identify incompatible, unreliable or unserviceable components, then define what stays and what goes.
- Agree on door sequence, work windows, temporary procedures and occupant communication.
- Test each door and the agreed failure conditions, document results and assign follow-up items.
GDS Technology's access-control work can include system inventory, fault investigation, door-operation and configuration review, scoped maintenance, system design, controller and reader installation, component integration, access configuration, functional verification and handoff, according to the agreed scope. The practical next step is to walk the doors with facilities and IT, then map the dependencies before the unsupported controller fails.
Make the upgrade a documented operating change, not an emergency hardware swap.
We talked about this on our podcast (Build Wired Secured - Podcast): What to Do When Access Control Fails.
Frequently Asked Questions
Which access control components should we replace before an unsupported controller fails?
Prioritize the unsupported controller and any software or licensing dependency without a supported recovery path. Then verify connected readers, locks, power supplies, communication modules, wiring and credentials for compatibility and condition. Replace parts that cannot work with the planned system or cannot be maintained. Do not assume every connected device needs replacement without checking its actual dependency.
Can we keep existing readers and locks when replacing a controller?
Possibly, but compatibility depends on the specific controller, reader, credential format, locking hardware, wiring and configuration. Inventory and test those components before approving a reuse plan. Confirm the replacement system can operate each door as required, and document any exceptions. Reusing hardware without verifying the full door assembly can shift a controller problem into a door-level failure.
How do we reduce disruption during an access-control upgrade?
Schedule work around door use, deliveries, visitors and tenant operations. Coordinate facilities, IT, security administrators and affected occupants, then agree on sequencing and temporary procedures before installation. Preserve available configuration, test each door after the change and track unresolved issues with named owners. A staged plan makes the operational impact visible before a door is taken out of service.
Does replacing an access controller make our business compliant?
No. A controller replacement does not by itself establish compliance with Georgia law or an industry requirement. Businesses remain responsible for their legal and operational obligations. Review who has access, how permissions are approved and removed, and what records are retained. Consult qualified counsel or the appropriate compliance professional for interpretation of requirements that apply to your organization.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.