6 Best Practices For EV Charger Network Migration

---

1. Design for Portability: Choose OCPP-Compliant Hardware

“The ability to migrate charging stations with minimal disruption depends heavily on OCPP compliance.”

– Nick Millar, EV Connect’s Director of Product Strategy

• Use certified chargers and CSMS. Certification ensures interoperability.
• Avoid vendor lock-in. Choose the right hardware and software combo for your needs.
• Standardization saves time and cost when switching CSMS or scaling your network.

2. Establish a Dedicated Planning Phase

• Allocate 2–4 weeks for stakeholder alignment before any on-site activity.
• Create a migration pre-requisite checklist to avoid preventable delays around common items like firmware version and OCPP compliance, SIM card transferability or eSIM provisioning, or connectivity tests to the new backend.
• Develop a shared understanding of:
  • Hardware and firmware readiness
  • SIM card provisioning
  • User account/data transfer
  • Physical signage and QR/NFC update needs

3. Involve All Vendors Upfront

• Include the hardware OEM early to confirm firmware compatibility and update paths.
• Align with both the old and new CSMS teams to validate protocol support.
• For OCPP chargers, confirm:
  • Firmware supports OCPP 1.6 or 2.0.1
  • Necessary configuration keys are exposed
  • Remote commands are accepted and executed correctly

4. Use Remote Configuration Where Possible

OCPP enables remote migration methods, such as:

• SetNetworkProfile (OCPP 2.x)
• ChangeConfiguration (OCPP 1.6)
• InstallCertificate and SetVariablesRequest for secure transitions

Pro Tip: With OCPP 2.0.1, you can pre-load new network settings in a secondary slot (e.g., profile 2), test the connection, and reset the charger remotely—reducing site visits, overall project duration and cost.

5. Plan for Edge Cases and Manual Interventions

Even with OCPP, you may encounter:

• Chargers with hard-coded settings (older firmware)
• SIM cards tied to the old CPO’s cellular contract
• Configuration keys named differently per manufacturer

Prepare your team with fallback strategies and manual override procedures. For particularly difficult chargers, site visits may still be required.

6. Conduct Controlled Batch Migrations

• Group chargers by model and firmware version
• Migrate in manageable waves during off hours to limit disruption
• Monitor real-time logs for errors or timeouts
• Ensure rollback capability where firmware updates are risky

 Are you planning an EV charger network migration? Download our Best Practices for CSMS Migration Checklist

From Case Study to Industry Standard

This project demonstrates how open standards like OCPP, and the right hardware and CSMS partners can ensure seamless and pain free network migrations. EV networks face inevitable change: new CSMS platforms, new vendors, and evolving user expectations.

This example, with EV Connect as the CSMS, ChargerHelp! as the field execution partner and BTC POWER as the hardware, serves as a model for how to execute migrations quickly, securely, and without major disruption.

By aligning around OCPP, clear governance, and phased execution, any network can position itself to adapt and scale—without re-inventing the wheel.

“This transition project proves that when you combine OCPP-compliant hardware with collaborative project execution and an open software platform like EV Connect, even urgent migrations can be fast, affordable, and scalable.”

-Kameale C. Terry Chief Executive Officer, ChargerHelp!

About EV Connect

EV Connect is the comprehensive EV charging platform for companies of all sizes to build, run, and scale their EV charging business. Trusted by CPOs, OEMs, fleets, utilities, and more.

With our industry leading EV charging software and white label EV charging solutions, integrate EV charging into your app and create custom charging solutions that fit your brand perfectly.

Request a Quote today and find out why EV Connect is the leading EV charging platform to run your business!

FAQs about EV Charging Station Network Migration

Why is OCPP compliance so important for EV charger network migrations?

OCPP ensures interoperability between chargers and CSMS platforms, which means migrations can use standardized, well-documented commands instead of proprietary methods. In this project, OCPP support from both BTC POWER hardware and EV Connect meant no hardware replacement, simpler troubleshooting, the ability to reconfigure most chargers remotely, and reduced custom development. It also helps avoid vendor lock-in and makes future transitions faster, cheaper, and more scalable.

How do you technically repoint chargers from an old CSMS to a new one using OCPP?

Use OCPP-standard commands to update network and security settings. With OCPP 1.6, apply ChangeConfiguration to set the new backend endpoint. With OCPP 2.x (including 2.0.1), use SetNetworkProfile to load new connection details—often into a secondary profile—then test and switch over. For secure transitions, install or update certificates (InstallCertificate) and adjust variables (SetVariablesRequest). Execute changes in batches, verify connectivity, and leverage fallback behavior (e.g., last-known good settings) to minimize disruption.

What should the dedicated planning phase include, and how long should it take?

Plan for 2–4 weeks of stakeholder alignment before any site work. Build a prerequisite checklist covering firmware readiness and OCPP version compliance, SIM transferability or eSIM provisioning, connectivity tests to the new backend, and clear ownership of user account/data transfer. Don’t overlook physical updates like signage and QR/NFC codes. Involve the hardware OEM early to confirm firmware paths, and align old and new CSMS teams to validate protocol support and required configuration keys.

How do you handle edge cases that can’t be solved remotely?

Expect a subset of chargers to require manual intervention, especially those with older firmware, hard-coded settings, SIMs tied to the previous operator, or manufacturer-specific configuration key names. Prepare fallback strategies, manual override procedures, and, when necessary, site visits. Mitigate risk by migrating during off-hours, monitoring real-time logs for errors/timeouts, and ensuring rollback options if firmware updates or config changes misbehave.