Keep Revenue Rolling: Phased EV Charger Replacement for UK Sites
Treat every commercial EV charger replacement as a staged project, not a like‑for‑like swap. Start with a site survey and compliance check, then decide between a targeted firmware or backend migration and a cohorted hardware replacement. This can be delivered end to end, from feasibility through OZEV‑aware installation, with OZEV approval, BS 7671 and the Smart Charge Point Regulations setting the compliance floor you cannot skip.
TL;DR:
Most failed chargepoints are caused by firmware or backend issues, not hardware faults, making updates or onboarding to open standards a cost-effective fix.
Accurate site power assessment, demand forecasting, and early DNO engagement can prevent costly grid reinforcement delays and overspending.
A phased migration approach with pilots, configuration validation, and rollback plans reduces risks and avoids widespread disruptions during system upgrades.
Compliance with OZEV specifications, using approved installers, and proper disposal of old units are essential to maintain eligibility for grants and meet safety standards.
Compatibility post-replacement depends on matching connector types, power classes, and backend protocols, requiring careful validation of hardware and management systems.
Table of Contents
When do you need full hardware replacement versus migration?
What compliance and grant rules apply to commercial replacements?
Safety considerations and precautions during EV charger replacement
Will my existing EVs and chargers still work after replacement?
How do you choose the right replacement charger for your site?
How Swiftcharging supports commercial EV charger replacement
Quick checklist: replace, upgrade or migrate?
Before you commit budget, run a short triage. Most “failed” chargepoints turn out to be firmware or backend problems, not dead hardware, and confusing the two wastes capital.
Work through these questions with your installer and IT contact before scoping any works:
Is the fault hardware, firmware or process? A unit that boots but won’t authorise sessions is usually a backend or communications issue, not a hardware fault.
Is the charger OCPP‑capable, and who owns the communications? Confirm SIM, VPN and APN ownership before assuming you need new hardware.
Is site power adequate, or do you need a demand forecast? If you’re adding load, this decides whether a DNO enquiry is required before anything else moves.
Who needs to be in the room now? Bring in your OZEV‑approved installer, your DNO contact, finance, and fleet operations together, not sequentially.
Getting this triage right at the start often saves weeks later.
When do you need full hardware replacement versus migration?
Genuine hardware failure has clear signs: cracked or water‑ingressed enclosures, a power class the site has outgrown, or units that trip out repeatedly despite electrical checks. These justify capital replacement. What doesn’t automatically justify it is a charger that’s simply “acting up” or running an old management platform.
A surprising number of “faulty” units are fixed by an over‑the‑air update or by re‑onboarding the charger to an open standard like OCPP, which can restore functionality and push a hardware decision back a year or more. Firmware and backend issues are frequently mistaken for terminal hardware faults, and an early firmware audit can avoid capital spend you didn’t need to commit.
Before deciding, audit each unit:
Record model, serial number and current firmware version for every charger on site.
Check who owns the communications contract (SIM, APN, roaming) and whether the warranty is still live.
Run a pilot OTA update on one or two units before committing the whole site to a firmware path.
Pro Tip: Confirm SIM and APN ownership, and who controls roaming access, before you start any migration. Losing API access mid‑project because a third party owns the connection is one of the most common and avoidable delays we see.
How do you assess site power before replacing chargers?
Power availability, not chargepoint choice, is usually what determines your timeline. Before ordering hardware, build a pragmatic demand forecast covering peak power draw, how many vehicles charge simultaneously, and typical dwell times across your fleet or visitor mix. Get this wrong and you’ll either overspend on a grid connection you don’t need or under‑provision and throttle your own operation.
Model realistic simultaneous demand, not nameplate capacity. Ten 22kW chargers rarely need 220kW if vehicles arrive and leave in a spread pattern rather than all at once.
Consider alternatives to grid reinforcement first. Load management and smart charging can often keep you within your existing supply capacity, and combining this with on‑site battery storage or solar generation can remove the need for immediate reinforcement altogether.
Engage your DNO early if reinforcement looks unavoidable. The process typically runs from a budget estimate through to a formal quotation and then works, and early engagement is what shortens the timescale, rather than leaving the DNO conversation until hardware is already ordered.
Ask about timed profile connection offers. Some DNOs will grant capacity with time‑of‑use restrictions attached, which can unlock a connection faster than a full unrestricted upgrade.
Run a simple simulation against your actual usage data before you commit to any of this. If load management or storage keeps peak demand comfortably inside your agreed supply capacity, you may not need to touch the grid connection at all. For larger destination or multi‑bay sites, the same demand‑forecasting discipline used in the truckstop charging guidance for eHGV infrastructure applies just as usefully to smaller commercial car parks.
What does a safe migration and cutover plan look like?
A backend or platform migration is a business continuity project, not an IT task, and it should be planned that way. Start with a full audit: hardware inventory, tariff structures, user lists and any roaming agreements with third‑party networks. Skipping this step is the single biggest cause of migration failures, because a single “big bang” cutover across a whole network tends to expose problems all at once, rather than in a controlled sequence you can manage.
Run a pilot cohort first. Moving a small group of chargers before the rest of the estate lets you validate configuration without risking the whole site’s revenue.
Roll out in phases, expanding from the pilot to small cohorts and only then to full migration, keeping the old system in read‑only mode until each phase is validated.
Freeze configuration changes during cutover windows, back up tariff and user data, and confirm credentials and communications access before flipping any switch.
Perform dry runs on a non‑live subset of chargers, and keep rollback readiness in place until the new platform has proven itself under real usage.
Once each cohort goes live, validate in this order: tariffs and pricing first (get this wrong and drivers are charged incorrectly from day one), then access controls, payment settlement, incident routing, and finally confirm historical usage data is still accessible for reporting and billing reconciliation. Migration checklists that map hardware, communications, tariffs and user lists in advance consistently reduce the risk of commercial disruption during backend switches.
Pro Tip: Treat commercial rules, tariffs, access groups and billing logic with the same priority as technical connectivity. A migration that nails the network handshake but scrambles the pricing table will generate complaints faster than any downtime will.
What compliance and grant rules apply to commercial replacements?
Every commercial chargepoint you install must meet the OZEV minimum technical specification, which sets required standards including BS EN 61851, mandatory connector modes and a minimum three‑year parts and installation warranty. Installation itself must follow BS 7671 and the IET Code of Practice for Electric Vehicle Charging Equipment Installation, and any new charger must comply with the Smart Charge Point Regulations 2021.
Installer credentials matter here as much as the hardware itself:
Use an OZEV‑approved installer, not just a general electrical contractor.
Ask for NICEIC or NAPIT evidence of the specific electrical work carried out, or ECA membership where relevant.
Confirm the warranty documentation meets the three‑year minimum before signing off the project.
Grant eligibility for workplace and commercial landlord schemes is tied directly to this specification, so non‑compliant hardware or an uncertified installer can disqualify an otherwise strong application. Before applying, gather your site electrical survey, installer certification, chargepoint technical datasheets and proof of business premises ownership or long lease, since these are the documents most schemes ask for first. Our guide to public charge point regulations covers the operator obligations that sit alongside these installation standards.
What do costs and timelines actually look like?
Budget across five distinct buckets: hardware, civils (groundworks, ducting, cabling), any DNO connection charges, software and commissioning, and ongoing maintenance. Skipping the DNO contingency line is the most common budgeting mistake we see, because it’s the one cost that can swing wildly depending on your existing supply capacity.
Simple AC replacements on adequate existing power typically run days to a few weeks from survey to commissioning.
DC rapid replacements needing DNO works can extend to several months once reinforcement or a new connection is involved.
Contract terms worth pinning down: data portability clauses, uptime SLAs, warranty terms covering spare parts, and an explicit API or data export clause so you’re never locked out of your own usage history.
Build in time for dry runs and commercial validation, not just physical installation, when setting your go‑live date.
Our EV charger installation cost guide breaks these buckets down in more granular detail if you’re preparing a procurement budget.
Safety considerations and precautions during EV charger replacement
Isolation comes first. Every replacement must begin with the supply safely isolated and proven dead before any cabling is disturbed, following BS 7671 procedures rather than assumptions based on the old installation’s paperwork. Legacy chargepoints, particularly anything installed more than five or six years ago, may not match current wiring diagrams, so treat every isolation as if the circuit has never been documented.
Physical hazards multiply on live commercial sites. Replacement work often happens while a car park, depot or forecourt remains partially operational, which means trailing cables, open excavations for civils work, and vehicle movement all need managing simultaneously. Barrier off the working area properly rather than relying on cones, and brief site staff so nobody attempts to use a chargepoint mid‑replacement.
Check the condition of the underlying infrastructure, not just the charger itself. Ducting, earthing arrangements and any shared distribution boards can degrade over years of outdoor exposure, and reusing a compromised earth connection under a shiny new charger creates a hidden risk rather than solving one. Only a qualified electrician working to BS 7671 should sign off the final connection, and this sign‑off should be treated as separate from the chargepoint manufacturer’s own commissioning checklist. Battery storage or on‑site generation added alongside a replacement introduces its own isolation and labelling requirements, so factor that into the same safety plan rather than treating it as a bolt‑on afterthought.
What happens to old chargers at end of life?
Removed chargepoints count as waste electrical and electronic equipment, and disposing of them through general waste or an unregistered scrap contractor is both environmentally poor practice and a compliance risk for the business removing them. Most units contain circuit boards, connectors and sometimes small amounts of battery backup circuitry that need proper WEEE handling rather than landfill.
Work with your installer or a licensed WEEE recycler to arrange collection as part of the replacement project itself, rather than leaving decommissioned units in a yard indefinitely. Many commercial installers can fold removal and responsible disposal into the same project scope as the new installation, which avoids a second procurement exercise for something that should have been handled at the outset.
There’s a commercial upside worth flagging too: components in older chargepoints, particularly copper cabling and certain metal enclosures, have scrap value that a responsible recycler will often offset against removal costs. Ask for this explicitly in your removal quote rather than assuming disposal is a pure cost line. Keep a disposal record for each unit removed, noting serial numbers and the recycling contractor used, since this becomes useful evidence if a grant body or auditor later asks how end‑of‑life equipment was handled.
Will my existing EVs and chargers still work after replacement?
Compatibility problems after a replacement almost always trace back to one of three things: connector mismatch, power class mismatch, or a protocol gap between old and new backend systems. A fleet that has standardised on CCS connectors will have no trouble with a new DC unit specifying the same standard, but mixed fleets with older CHAdeMO vehicles alongside newer CCS models need chargers that genuinely support both, not just one badge that looks compatible on a spec sheet.
Power class matters just as much. Replacing a 7kW AC unit with a 22kW unit sounds like a straightforward upgrade, but if the vehicles using that bay only accept single‑phase AC charging, the extra capacity is wasted and the connection cost may not be justified. Check your actual fleet or visitor vehicle mix before specifying power class, rather than defaulting to the highest available.
The less visible risk sits in the backend. If your new chargepoints run on a different management platform to your old ones, RFID cards, driver app logins and payment credentials issued under the old system may not transfer automatically. This is where the migration audit covered earlier pays for itself: mapping user lists and access credentials before cutover prevents a wave of “my card doesn’t work” calls in the first week after go‑live. Where sites mix chargepoints from different manufacturers, confirm OCPP version compatibility explicitly rather than assuming any two OCPP‑labelled units will talk to the same management platform without issues.
Common troubleshooting issues after replacement (and fixes)
Authorisation failures top the list. A charger that powers up but won’t start a session for a valid RFID card or app user is usually a backend configuration issue, specifically incomplete user list migration, rather than a hardware fault. Check that the new platform has received the full access group data before assuming the unit itself is broken.
Connectivity drop‑outs are the second most common complaint, and they trace back almost every time to the SIM, APN or VPN ownership questions flagged earlier in the migration process. If communications access wasn’t transferred cleanly during cutover, chargers can appear offline on the management dashboard even while physically functioning fine for anyone plugged in.
Tariff and billing discrepancies show up quickly once real sessions start running. Drivers get charged the wrong rate, or free workplace sessions suddenly show a charge, when the tariff table wasn’t fully validated during the phased rollout. This is exactly why the earlier validation checklist puts tariffs first after cutover, not last.
Intermittent charging or unexpected session termination, once hardware faults are ruled out, is often a load management setting carried over incorrectly from the old system, throttling or cutting sessions based on outdated demand thresholds. Reviewing load management configuration against your current site setup, rather than assuming old settings still apply, resolves most of these cases without any hardware intervention at all.
How do you choose the right replacement charger for your site?
Usage patterns should drive the spec, not the other way round. A workplace car park with vehicles dwelling for six to eight hours needs nowhere near the power output of a fleet depot turning vehicles around in under an hour, and specifying DC rapid chargers for a slow‑dwell site wastes capital on power you’ll rarely use at full capacity.
Start by mapping actual dwell time and turnover against your fleet or visitor profile. Workplace and destination sites with long dwell times are usually well served by 7 to 22kW AC units, which cost less to install and place lighter demand on your electrical supply. Fleet and depot operations with tight turnaround windows justify the higher cost and power demand of DC rapid or ultra‑rapid units, particularly where vehicles must return to service quickly.
Connector standards and future‑proofing matter more than raw power figures. Choose units supporting current CCS standards as a baseline, and check that whatever backend platform you select supports OCPP so you’re not locked into a single manufacturer’s ecosystem for future hardware decisions. Load management and smart charging capability is worth specifying as standard now rather than retrofitting later, since it gives you headroom to add chargers without automatically triggering a fresh DNO conversation. Finally, weigh the warranty and support terms as heavily as the sticker price. A cheaper unit with a bare minimum three‑year warranty and thin spare parts availability often costs more over its operational life than a slightly pricier model backed by a proper maintenance contract.
How Swiftcharging supports commercial EV charger replacement
Commercial replacement and migration projects can be run end to end, starting with a feasibility survey and site assessment that answers exactly the questions raised throughout this guide: power capacity, compliance gaps, and whether you need hardware replacement or a backend migration. From there, we handle OZEV‑aware installation, phased cutover for multi‑site estates, and long‑term management once the new system is live.
Where a DNO conversation or demand forecast is needed, engagement can be managed directly, and where it makes commercial sense, battery storage or solar PV can be integrated alongside the charging upgrade to reduce grid dependency rather than simply adding load to an already stretched connection. Assistance with identifying and preparing grant applications against the OZEV minimum technical specification is also available, so compliance and funding eligibility are handled together rather than as separate, disconnected steps.
If you’re weighing up whether your existing chargepoints need replacing, migrating, or simply a firmware audit, book a feasibility survey with our commercial EV charging team in Chichester or explore our project work in Dover to see how a phased replacement runs in practice. Getting the survey booked is the fastest way to turn this guide into an actual project timeline for your site.
What we’ve learned from replacement projects that go wrong
Most of the pain we see on replacement projects doesn’t come from the hardware. It comes from decisions made too late: a DNO conversation started after chargers were already ordered, or data ownership questions raised only once a migration was already underway. Fixing either after the fact costs far more time than addressing them upfront.
The mitigation that consistently earns its keep is the small pilot cohort. Moving a handful of chargers first, before touching the rest of the estate, exposes tariff or access problems while the stakes are still low.
— Swift Charging
Sources
Recommended