The network is scaling
Volume, organisations or operating constraints exceed the original scope.
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.
Volume, organisations or operating constraints exceed the original scope.
APIs, ERP, payment, roaming or business tools require a more open platform.
Exports, history or retention responsibilities are not clear enough.
Public, fleet, bus or heavy-duty charging brings new operating requirements.
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 actual schedule depends on the network, equipment and partners. We build it after the assessment — there is no one-size-fits-all cutover promise.
Chargers, firmware, connectivity, sites, users, tariffs, contracts, data and external flows.
Compatibility tests, required OCPP functions, dependencies and gaps to resolve before migrating.
Data to retain, rules to rebuild, responsibilities and acceptance criteria.
Validation on a representative scope before extending to further batches.
Successive batches, controls, team guidance and closer monitoring after each stage.
Models, firmware versions, connectivity, certificates, commands and required configurations.
Sessions, users, tokens, tariffs, invoices, technical history and retention obligations.
GIREVE, Hubject, OCPI and OICP, payment, ERP, applications and partner interfaces.
Support, alerts, field procedures, responsibilities, service levels and rollback plan.
Compatibility is checked model by model, including firmware, OCPP functions and available connectivity.
The scope depends on exports from the source platform, data quality and retention obligations. It is defined during the assessment.
Sometimes, but a phased approach is often preferable: it lets you test the flows and limits operational risk.
Responsibilities are written into the migration plan. Chargekeeper coordinates the flows included in the contracted scope.
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.
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.
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.
Inventory, dependencies, risks, pilot and acceptance criteria: let us start by scoping the project.
Request a migration assessment