Reporting
The retained Azure instance can provide ongoing reporting, extending its value beyond the transition itself.
Case study · Backend migration
Backend migration. At the pace of your sites.
Changing backends involves technology, operations and often electricity supply. We bring these requirements together in a migration plan and support the transition site by site.
An anonymous customer project
8,000 AC and 300 DC charging stations. A shared path to the new backend.
We helped a customer migrate 8,000 AC and 300 DC charging stations from two existing backends to one new backend. Electricity supply arrangements were also changing at some sites, so the technical transition needed to align with the respective supply dates.
All charging stations were first connected to the OCPP Broker, which continued to forward traffic to their existing backends. This established a shared connection layer while operations continued on the existing systems.
The sites then moved to the new backend one at a time. Where electricity supply was changing, the transition was aligned accordingly. This kept the schedule manageable and under control. In this project, the migration was completed without interrupting operations.
How the transition worked
Establish the connection. Then migrate the sites.
The broker provided the shared connection layer, allowing the subsequent transition to be organised site by site.
- 01 · Connect the existing stationsAll charging stations were first connected to the OCPP Broker. The broker continued to forward their messages to the respective existing backend.
- 02 · Coordinate site datesAt affected sites, migration dates were aligned with changes in electricity supply arrangements, allowing technical and operational transitions to be planned together.
- 03 · Move to the new backendSites were switched to the new backend in sequence. This phased approach kept the project’s migration schedule manageable.
- 04 · Keep using the brokerAfter the migration, the broker remained in place as an Azure instance for the customer, providing a lasting basis for reporting, monitoring and additional integrations.
After the migration
The connection keeps its value in daily operations.
The retained Azure instance enables reporting and monitoring for the customer. Additional integrations address the requirements of individual sites.
Monitoring
The broker provides a basis for observing the charging infrastructure after the backend change.
Payment methods by site
Further integrations were implemented through the broker for site-specific payment methods alongside the new backend.
Software and implementation
Plan the migration path together.
What transition are you planning?
We discuss your existing backends, sites and the dates that shape the transition, then develop a migration path that fits your operations.