Switching your CPMS How to move your EV chargers to a new back office
You can move existing EV chargers to a different Charge Point Management System (CPMS) without necessarily replacing the hardware. For OCPP compliant chargers, the process typically involves checking compatibility, configuring the new platform, repointing chargers to the new back office, transferring available data and testing the network before full cutover. The exact timescale and downtime depend on the size and configuration of your estate, so these should be agreed before migration begins.
- Dual OCPP 1.6 & 2.0.1 certified
- Supports existing OCPP compliant hardware
- Phased, controlled cutovers
- 100% UK-based support
Why do EV charging operators switch CPMS?
Changing your EV charging back office is a significant decision. In most cases, operators are not looking to change because they want another piece of software. They are looking for a better way to manage an existing network.
Common reasons for switching include:
Reliability and uptime
Persistent faults, limited visibility or slow responses can make it difficult to keep chargers available.
Hardware lock-in
A platform may work well with one manufacturer's hardware but become restrictive as the network grows.
Reporting
Operators may need more detailed data on usage, revenue, faults, energy consumption and individual charging sessions.
Driver support
Poor app experiences or slow support can quickly become an operational problem when drivers cannot start or complete a charging session.
Cost
Platform fees, transaction charges and other costs can become increasingly difficult to justify as a network scales.
Roaming and integrations
Growing networks may need access to eMobility Service Providers, roaming partners, payment services or other systems that their existing platform cannot support.
For operators who started with a charger manufacturer's software, the issue can simply be that the network has outgrown the original system.
The important point is that switching a CPMS does not automatically mean replacing your chargers. Fuuse supports existing OCPP compliant charge points and is dual OCPP 1.6 and 2.0.1 certified.
What does a CPMS migration actually involve?
A successful EV charging platform migration is planned before the first charger is moved. The Open Charge Alliance has published guidance specifically on migrating OCPP compliant charging stations, recognising that moving hundreds or thousands of chargers between back ends can be complex.
- 1
Compatibility assessment
First, every charger model in the estate needs to be assessed. This means confirming the OCPP version, configuration, firmware and any manufacturer-specific requirements.
This is where potential issues should be identified, rather than during go-live. Some older or proprietary chargers may require firmware updates, configuration changes or additional testing before they can communicate correctly with the new CPMS.
- 2
Platform setup
Your new platform is configured before chargers are repointed. Sites, chargers, tariffs, user groups, access rules, payment arrangements and other operational settings can be prepared in advance.
The aim is to make the new environment ready before the first live charger moves across.
- 3
Repointing the chargers
The charger is then directed towards the new back office.
For hardware that supports remote configuration, this can normally be completed without sending an engineer to site. Some chargers, particularly older equipment or hardware with restricted configuration access, may require an engineer or installer to make changes locally.
The exact requirements should be established during the compatibility assessment. There is no benefit in discovering that a charger needs a site visit on migration day.
- 4
Data migration
Not every piece of information necessarily moves automatically between CPMS platforms.
Historical charging sessions, driver information, RFID records, tariffs, configuration data and other records depend on what the outgoing provider can export and what the new platform can import.
This is an important part of migration planning. Your outgoing provider controls access to much of the existing data, so the export format, scope and cost should be confirmed before you give notice.
- 5
Driver and account transition
Drivers need to know what is changing and when.
Depending on the migration, this can include moving driver accounts, configuring RFID access, communicating new app requirements and explaining any changes to payment or authentication.
For public networks, the driver experience matters just as much as the technical migration. The objective is to make the transition as invisible as possible to someone arriving at a charger.
- 6
Phased cutover
A large network does not need to be switched in one go.
A phased approach allows a small group of chargers to be migrated first, tested and monitored before the remaining estate is moved. This provides an opportunity to identify configuration or connectivity issues while the scope is still controlled.
For larger estates, migration can therefore be treated as a series of controlled cutovers rather than one high-risk event.
- 7
Post-migration verification and handover
Once chargers are connected to the new CPMS, they need to be checked.
This includes confirming charger connectivity, starting and stopping sessions, RFID or app authentication, tariff application, payments, reporting and fault visibility.
Only once the network is operating as expected should the migration be considered complete.
How much downtime should you expect when switching CPMS?
Downtime is one of the most important questions to ask before changing your EV charging platform.
There is no single downtime figure that applies to every migration. It depends on the charger hardware, configuration, connectivity and migration approach.
The important distinction is between the overall migration project and the period when an individual charger is unavailable. A migration can take place over an extended project window while the actual interruption to a charger is much shorter.
For example, Fuuse states that migrations can involve downtime of only a few minutes in some circumstances, although the actual duration depends on the site and situation.
For a live network, the objective should be to minimise disruption by preparing the new platform in advance, testing compatibility and moving chargers in controlled batches.
Illustrative only. Actual timescales depend on your hardware, configuration and sites.
What happens to your data, drivers and tariffs?
This is one area where migration providers should be completely transparent.
Some information can be transferred or recreated in the new CPMS, but not everything is guaranteed to move automatically. The outgoing provider controls much of the data and configuration held within the existing system.
You should establish what can be exported, in which format and whether there is a charge for doing so. This can include:
- ✓Historical charging session data
- ✓Driver accounts
- ✓RFID cards and permissions
- ✓Tariffs and user groups
- ✓Charger configurations
- ✓Payment and invoicing information
- ✓Open support cases and complaints
Recreated, not transferred
Some information may need to be recreated rather than transferred. Payment information, for example, may require drivers or customers to enter their details again. Existing charger control settings may also need to be evaluated and replicated rather than directly imported.
Tariffs
Tariffs should be treated as part of the migration plan too. A new CPMS may give you the opportunity to maintain existing tariffs or introduce new pricing structures.
Open support tickets
Open support tickets also need a clear owner. Agree whether the outgoing provider will resolve existing cases before cutover or whether responsibility transfers after migration.
Timing
The key is to identify these issues before the first charger moves.
What should you ask your current CPMS provider before switching?
Before giving notice, ask your existing provider:
- 01What notice period applies to the contract?
- 02What is the exact contract end date?
- 03Can you export all historical charging data?
- 04What format will the data be supplied in?
- 05Is there a charge for data export?
- 06Will they provide charger configuration information?
- 07Can they release the credentials or access required to repoint your chargers?
- 08Which driver and RFID records can be exported?
- 09What happens to existing driver accounts?
- 10What happens to open support tickets?
- 11Which tariffs, access rules and charger settings can be exported?
- 12Are there any restrictions on moving your existing hardware to another CPMS?
Do this before the migration date is agreed.
The Open Charge Alliance's guidance on migrating charging stations is also useful when planning the technical and operational requirements of a move.
What does Fuuse handle, and what do you need to handle?
Fuuse handles
- Compatibility and migration planning
- Fuuse platform configuration
- Charger onboarding and repointing support
- Migration coordination
- Testing and verification
- Driver and operational support through the transition
You handle
- Confirming your contract and notice requirements
- Agreeing data access and export with your existing provider
- Providing charger and site information
- Approving tariffs, users and access rules
- Communicating changes to your drivers where required
The aim is to keep the amount of internal resource required from your team to a minimum, while making sure you remain in control of the decisions that affect your network.
Be.EV: migrating 754 connectors across 176 sites
Be.EV is a useful example of what a real CPMS migration can involve.
Fuuse migrated 754 connectors across 176 charging sites, including the import of 70,000 RFID tokens. Be.EV described the migration as a complex process, with Fuuse working closely with its team throughout the transition.
The move allowed Be.EV to transition its existing network to Fuuse while retaining its charging infrastructure. Following the migration, Be.EV also introduced a new branded driver app.
The project demonstrates why CPMS migration should be treated as an operational project rather than simply changing a software setting. Hardware compatibility, data, RFID access, driver experience, platform configuration and testing all form part of the move.
Read the Be.EV case study →Ready to switch your CPMS?
Changing your EV charging back office does not need to mean starting again with new hardware.
The right migration plan can allow you to move an existing network while protecting charger availability, driver access and operational continuity.
If you are considering a change, talk to Fuuse about migrating your network. We can assess your existing charger estate, discuss compatibility and explain what the transition would involve before you commit to the move.
Talk to us about migrating your network →Frequently asked questions
Can I move my existing chargers to a new CPMS without replacing them?
Yes, provided the chargers are compatible with the new platform. OCPP compliant hardware is designed to communicate with different back office systems, although compatibility still needs to be assessed at charger model and configuration level. Some legacy or proprietary hardware may require firmware changes, local configuration or an alternative approach.
How long does a CPMS migration take?
There is no reliable single timescale for every network. The duration depends on the number and type of chargers, configuration complexity, data requirements and whether any sites need engineering work. Fuuse should confirm a project specific migration schedule following an assessment of your estate.
Will my chargers go offline during migration?
There may be a short interruption when an individual charger moves between back office systems. Fuuse says some migrations can involve only a few minutes of downtime, although the exact duration depends on the charger and site. A phased cutover can help minimise disruption across a larger network.
Can you transfer our existing driver accounts and charging history?
Some driver and charging data can be transferred, but this depends on what your existing provider can export and what the new CPMS can import. Data should therefore be assessed before migration. Payment information and certain historical or configuration data may need to be recreated rather than transferred directly.
Do we need to be out of contract with our current provider first?
You need to understand your existing contract and notice requirements before setting a migration date. You may be able to plan the technical migration while your current agreement remains active, but the commercial terms of your existing contract determine when services can formally end.
What happens to our RFID cards?
Existing RFID cards may continue to work if their identifiers and permissions can be replicated in the new CPMS. This needs to be checked as part of migration planning. For large estates, the RFID database should be reviewed early so that driver access is not unnecessarily disrupted when chargers move.
Can you migrate a mixed estate with chargers from several manufacturers?
Yes, provided the individual chargers are compatible with the new CPMS. Mixed estates are common as networks grow and operators add different hardware over time. Each charger model should be assessed for OCPP version, firmware, configuration and any manufacturer specific requirements before migration.
Want to know more?
Complete this form, and a member of our specialist team will be in touch.
Something Powerful
Tell The Reader More
The headline and subheader tells us what you're offering, and the form header closes the deal. Over here you can explain why your offer is so great it's worth filling out a form for.
Remember:
- Bullets are great
- For spelling out benefits and
- Turning visitors into leads.