Chargekeeper
en
Switch platforms

Switch CPMS without stopping your network.

A migration is more than reconnecting chargers. It affects configurations, data, users, payment, roaming and your operations teams. We map every dependency before the cutover.

The signals

When should you reassess your platform?

The network is scaling

Volume, organisations or operating constraints exceed the original scope.

Integrations are blocking

APIs, ERP, payment, roaming or business tools require a more open platform.

Data is out of reach

Exports, history or retention responsibilities are not clear enough.

New markets are emerging

Public, fleet, bus or heavy-duty charging brings new operating requirements.

Phased cutover

A pilot, then batches validated one by one

Chargers move to Chargekeeper in batches. Each batch is checked — configurations, tokens, tariffs, partner flows — before the next one starts. The network keeps running throughout.

The method

Five stages, from the first inventory to the last charger

The actual schedule depends on the network, equipment and partners. We build it after the assessment — there is no one-size-fits-all cutover promise.

  1. Stage 01

    Inventory

    Chargers, firmware, connectivity, sites, users, tariffs, contracts, data and external flows.

  2. Stage 02

    Qualification

    Compatibility tests, required OCPP functions, dependencies and gaps to resolve before migrating.

  3. Stage 03

    Transition plan

    Data to retain, rules to rebuild, responsibilities and acceptance criteria.

  4. Stage 04

    Pilot

    Validation on a representative scope before extending to further batches.

  5. Stage 05

    Batch cutover

    Successive batches, controls, team guidance and closer monitoring after each stage.

The assessment

What the assessment covers

Hardware

Models, firmware versions, connectivity, certificates, commands and required configurations.

Data

Sessions, users, tokens, tariffs, invoices, technical history and retention obligations.

Ecosystem

GIREVE, Hubject, OCPI and OICP, payment, ERP, applications and partner interfaces.

Operations

Support, alerts, field procedures, responsibilities, service levels and rollback plan.

FAQ

CPMS migration questions

Can every charger be migrated?

Compatibility is checked model by model, including firmware, OCPP functions and available connectivity.

Can all historical data be kept?

The scope depends on exports from the source platform, data quality and retention obligations. It is defined during the assessment.

Can the migration happen in one go?

Sometimes, but a phased approach is often preferable: it lets you test the flows and limits operational risk.

Who coordinates roaming and payment partners?

Responsibilities are written into the migration plan. Chargekeeper coordinates the flows included in the contracted scope.

Do drivers need new badges?

Not necessarily: RFID badges and user accounts can be imported into Chargekeeper from a CSV file, so existing identifiers can be kept. The exact scope is confirmed during the assessment.

Does every charger need an intervention?

Each charger must be configured to point to Chargekeeper's OCPP address. Depending on the model, this is done remotely or requires a site visit: the inventory specifies it charger by charger.

How long does a migration take?

It depends on the size of the network, the variety of models and the partners to connect. The schedule is built after the assessment, with a pilot followed by successive batches.

Base your CPMS switch on facts

Inventory, dependencies, risks, pilot and acceptance criteria: let us start by scoping the project.

Request a migration assessment