When to Upgrade an Access Control System and How Long It Takes

Most access control upgrades happen for the wrong reason. A business waits until readers fail or a break-in forces action, then pays for a rushed job. A better test is simpler: if your credentials can be cloned or your controller gets no patches, it is time to plan, and the downtime is smaller than you might think.
Forget the calendar and check support status
Age tells you very little. Support status tells you almost everything.
Manufacturers issue end-of-life notices when they stop building a controller or reader line. Past that date, firmware security patches stop and spare parts become harder to find. Your doors still open, but your risk keeps climbing. If the controller can’t run modern encrypted protocols such as OSDP over RS-485 and AES-128, it is a liability even when it looks fine.
That gap often shows up around year six or seven. Hardware may last 10 to 15 years, while software does not keep pace. An old on-premise controller may need a site visit for every user change. It may not feed events to CCTV or intercoms for video verification. It may store only a few thousand events locally, leaving thin audit trails for after-hours incidents.
The market has moved on. The physical access control market is projected to grow from US$9.3 billion in 2021 to US$14.7 billion by 2027 (MarketsandMarkets). Much of that spend is going to cloud-based access control with browser admin and remote lockdown. Updates arrive automatically. A business that stays on a closed legacy platform gets left behind on integrations and patches.
So don’t ask only how old the system is. Ask whether it is still supported and still patched.
Old cards are the weakest link
If your staff still tap grey plastic cards from before 2015, assume they can be copied. Most of those cards are MIFARE Classic using CRYPTO1. That cipher was reverse-engineered in 2007. Clone gear now costs well under $100, and an intruder can copy a card in under a minute with commodity hardware.
This is seen in audits all the time. A lost card is not cancelled for days. Temps keep cards after jobs end. One card gets shared for the back door because it is easier than issuing three. The plastic may look controlled, but it isn’t.
Printing and programming replacements adds up. There is the per-card cost, along with printing and admin time. There is the locksmith callout when a high-use door stops reading worn cards. There is also the gap when audit trails can’t prove who was where.
Mobile credentials fix most of that churn. Phones with Apple Wallet and Google Wallet, or platforms such as HID Mobile Access and SALTO, let you issue and revoke access without plastic. A contractor gets access for two days and it expires on its own. A lost phone gets suspended in minutes, with nothing to reprint.
A locksmith can test a sample card in minutes to show whether cloning is possible. That quick demo often settles the upgrade debate.
Plastic does not have to vanish on day one. Many upgrades run mixed credentials while staff adjust. The point is that the old cipher has to go. If your readers can’t handle encrypted smart cards and mobile passes, the readers have to go too.
Daily friction tells you before the budget does
You don’t need a spreadsheet to feel a system working against you. Cards go missing weekly. You wait days for an installer to add a user. Staff prop a side door because the reader is flaky. No one can lock the site from a phone at night. That friction is useful data.
Credential churn eats hours you never see. Each re-issue means deactivating the old credential and updating the log. Multiply that across temps and shift changes, and credential lifecycle management turns into a part-time job. A modern system lets an admin add and suspend users in seconds from a browser, without waiting for a site visit.
Staff choose ease over security when technology gets in the way.
Money gives you a clean rule. When annual maintenance and ad-hoc callouts approach roughly half the cost of replacing the whole system outright, replacement is cheaper over a three-year horizon. You’re paying to keep weak cryptography alive, while new readers and cloud admin cut those repeat visits.
Capability gaps push the same way. Older controllers often lack anti-passback and dual authentication for server rooms and cash-handling areas. They can’t enforce two-person rules for pharmacies and laboratories. Audit trails are short and hard to search, which becomes a problem when you need to investigate a safety incident or after-hours theft. If your needs have grown past what the panel was built for, no repair fixes that.
What the upgrade timeline looks like in practice
Most single-site upgrades follow the same five phases: site audit and scoping, quote and system design, hardware procurement, installation and cabling, then commissioning with training.
Slippage rarely comes from the screwdriver work. It comes from unknowns found early. Old wiring may have no labels, and electric locks may not suit new readers. Fire doors have egress rules, while network points for PoE controllers are often missing. Sort those issues during the audit and the rest moves quickly.
A phased, off-hours cutover is normal. A good installer brings the new system up zone by zone outside business hours or over a weekend. Your site never sits unlocked. Staff return to new readers and clear instructions.
Site audit and scoping is where timelines are set
For a single-site business, the audit often takes one to two days. The quote and system design then takes three to five business days. Don’t accept a fixed timeline until you’ve had an on-site walkthrough from a licensed WA installer for access control systems perth who has checked wiring, doors, power and network points in person.
The walkthrough must start with wiring. If your readers still run unencrypted Wiegand, the installer will test whether the cable can carry OSDP over RS-485. Good cable can stay. Damaged or undocumented cable cannot. Locating old runs takes longer than most businesses expect, and it is the main reason quotes vary.
Next come the doors and locks. Electric strikes and electrified mortise locks often suit a retrofit. Electromagnetic locks suit a different use and need separate checks for holding force and release. Compatibility decides whether the job is a swap or a rebuild. At the same time, you must settle fail-secure versus fail-safe. Fail-secure stays locked without power. Fail-safe unlocks. Life safety and egress rules decide that choice, not preference. Fire and emergency exit doors have strict requirements under NCC egress compliance.
The third area is power and network access. Modern 802.3bt PoE door controllers can remove separate power runs. That can change the cost considerably, but only if network drops exist near each door. No drops means more cabling time.
In Western Australia, there is one more check. Installing electronic access hardware is a licensed security activity under the Security and Related Activities (Control) Act 1996. Ask for the licence type before you accept a quote. Also ask who does the data cabling. That question can prevent arguments later.
Installation, cabling and commissioning
Hardware procurement often takes one to three weeks, depending on stock and lead time. Common readers and strikes move quickly. Less common controllers and finishes do not. Your installer should confirm what is on the shelf before pulling old gear off the wall. That one check prevents a site from sitting half finished.
Installation speed comes down to cable. Where existing wiring can be reused, a retrofit door often takes about 30 to 60 minutes. Where new network cabling is required, each door takes longer. PoE helps when drops are close, while concrete walls and high ceilings slow things down. A clear audit keeps surprises to a minimum.
Commissioning with training often takes one to two days. It involves much more than switching on the power. Each door gets tested for lock and release. Egress push bars and fire interfaces get tested with the doors closed and open. Users are loaded and schedules are set. Remote lockdown from a phone and browser gets tested too.
Ask for a zone-by-zone handover. A good installer commissions one area, proves it and moves on while you keep using the rest of the site. Night and weekend work keeps doors covered during business hours, so you don’t lose a day of trade. Ask how late-night callouts are handled during the swap. You want one number to call if a door will not lock.
Your locksmith should also hand over admin logins and a wiring map. There is nothing worse than calling for help and learning that no one knows what was fitted.
Credential migration needs its own plan
The readers go up quickly. People take longer. Encoding new smart cards and moving users across must be planned before old readers come off. Mobile passes need setup too. Leave it too late and you get queues at the front desk and propped doors.
Start with a clean user list. Remove leavers and set expiry dates for temps and contractors. Decide who can approve new access. Import the audit logs you must keep for safety and incident records. Older systems store limited events locally, so pull what you need while the old software still runs.
Then run mixed credentials for a week or two if you can. Staff keep an old card while the new pass is tested. Phones get enrolled in small groups. Door behaviour gets explained in plain terms. People need to know what a denied beep means and who to call.
Training is short when it is specific. Show admins how to add and suspend users, run an audit trail for a time window and lock the site remotely from a browser.
Prop no doors.
When staff trust the new routine, pull the old readers. The site is then cleaner, with fewer cards in circulation and a log you can actually use.
Don’t wait for a failure to force your hand. If credentials can be cloned or support has ended, start with an audit and a clear migration plan. Admin time keeps climbing as systems age, so early planning pays. A planned upgrade keeps doors covered and staff working, and it costs less than a panic job.




