V E L M O R

Loading

Monday – Friday 09:00 – 18:30
img

Velmor Teknoloji

13 August 2026

How to Change CPO Software: A Safe EV Charging Network Migration Guide

Why Does Changing CPO Software Seem So Difficult?

For a Charge Point Operator, the central charging management platform is one of the most critical layers of the entire operation. Station availability, charging sessions, tariffs, users, payments, reporting, remote commands and third-party integrations all depend on the central system.

Therefore, when a CPO becomes dissatisfied with its existing software, the main question is not simply "Is there a better charging management platform?"

"How can we change our CPO software without putting our live charging network at risk?"

Limited reporting, high licensing costs, insufficient technical support, performance issues, difficult integrations and slow feature development can all lead an operator to consider a new CSMS.

When Should a CPO Consider Changing Its Software?

  • Technical support no longer meets operational requirements
  • Station problems cannot be monitored effectively
  • Reporting and analytics capabilities are insufficient
  • New payment, billing or roaming integrations are difficult to implement
  • Multi-vendor charger compatibility creates recurring problems
  • Required features cannot be developed within reasonable timeframes
  • Software costs increase disproportionately as the network grows
  • The mobile application no longer meets brand or customer expectations
  • The operator has limited access to its own operational data

A CPO Software Migration Is More Than Changing Charger Backend URLs

1. Chargers and OCPP Connections

Connections between physical charging stations and the current backend must be migrated. Different manufacturers, models and firmware versions may require different migration methods.

2. Operational Configuration

Locations, stations, connectors, tariffs, organizational structures, permissions and business rules need to be prepared in the new platform.

3. Users and RFID

Customer accounts, RFID cards, user groups, subscriptions and wallet structures may need to be transferred separately.

4. Payments, Billing and Integrations

Payment providers, invoicing systems, roaming connections, APIs and other external services must be validated in the new environment.

5. Mobile App and Driver Experience

A successful backend migration can still become an operational problem if drivers cannot log in, find stations, pay or start charging. Mobile application processes therefore need to be included in the migration plan.

The Biggest Migration Mistake: Changing Everything at Once

Moving an entire charging network to a new CSMS in a single cutover can introduce unnecessary operational risk.

For this reason, CPO software replacement should be treated as a controlled migration project, not as a single technical switch.

How Should a CPO Software Migration Be Planned?

1. Build a Complete Charger Inventory

  • Charger manufacturers
  • Models
  • Firmware versions
  • OCPP versions
  • Current backend endpoints
  • SIM and network configurations
  • Locations and connectors

2. Prepare the New CPO Platform Before Cutover

When migrating to a platform such as ChargenOS, station definitions, organizational structures, permissions, tariffs, payment systems, reporting and integrations can be prepared before the live transition begins.

3. Start with a Pilot Group

A small group representing different charger manufacturers and models can be migrated first. Charging operations, status notifications, meter values, payments and authorization flows should be verified during this stage.

4. Separate Charger Connectivity from the Final CSMS Cutover

The ChargenOS OCPP Proxy approach can help separate charger connectivity from the final backend migration.

Chargers can first be connected to a controlled OCPP routing layer while traffic continues to be routed to the existing CPO platform. Once the new ChargenOS environment is ready, backend routing can be changed centrally.

For a detailed technical explanation, read OCPP Proxy for CPO Software Migration.

5. Treat Business Data Migration as a Separate Workstream

Charging history, users, RFID cards, tariffs, financial records, payment information and reporting datasets should be evaluated separately.

6. Define the Rollback Plan Before Migration

A strong migration plan describes not only how to move forward, but also how to return to the previous environment if an unexpected issue occurs.

Do Not Select a New CSMS Based Only on Its Feature List

  • How will our existing chargers be migrated?
  • Are our charger manufacturers and models supported?
  • Can migration be performed in controlled groups?
  • How will users and operational data be transferred?
  • How will payment and billing integrations be migrated?
  • How quickly can we reach technical support?
  • How are new feature and integration requirements handled?
  • Will we retain access to our data if we decide to migrate again?

CPO Software Migration with Velmor Technology and ChargenOS

ChargenOS, developed by Velmor Technology, is a centralized charging network management platform designed for CPO operations.

The objective is not simply to replace one dashboard with another. The existing charging infrastructure, integrations and operational requirements should first be evaluated and migrated through a controlled transition plan.

Frequently Asked Questions

Can a CPO change its charging management software?

Yes. Charging networks can migrate between central management systems, particularly where open standards such as OCPP are used.

Will charging stations go offline during a software migration?

It depends on the migration architecture. With a staged migration model, the entire network does not necessarily need to be taken offline at the same time.

Can every OCPP charger easily move to another CSMS?

OCPP provides an important interoperability layer, but implementations may vary between manufacturers, models and firmware versions.

Can customer accounts and charging history be transferred?

This depends on the data available from the existing platform and the migration capabilities of the new system.

What is an OCPP Proxy?

An OCPP Proxy is a communication and routing layer between charging stations and a central charging management system.

Do all chargers need to migrate at the same time?

No. Large networks can be migrated by manufacturer, model, location or operational group.

Turn CPO Software Replacement into a Manageable Migration Project

With a complete infrastructure inventory, compatibility testing, pilot migration, data planning, integration preparation and technologies such as OCPP Proxy, the transition to a new CPO platform can become significantly more manageable.

If you are considering changing your current CPO software, the first step should not be switching servers. It should be designing the right migration plan for your charging network.