EV charger backend migration: plan the exit before you buy the network

1. Put exit rights in the original purchase

Before ordering chargers or signing a charging-management contract, identify who controls the charger administration account, configuration credentials, cellular subscription, certificates, firmware access and technical records. Write down what the owner receives if the platform contract ends and what assistance the outgoing provider must give.

Do the same for business data. Charger status, customer accounts, tariffs, authorization lists, transaction records, payment references, maintenance history and invoices are not one export. Define the required fields, format, ownership, retention period, lawful transfer and reconciliation method. An “OCPP compatible” statement does not answer those commercial and data questions.

The Open Charge Alliance (OCA) describes OCPP as the communication protocol between charging stations and charging-station management systems. That interoperability objective is important, but the procurement contract must still define access, implementation scope and operational handover. Source: OCA protocol overview.

2. Inventory by model and firmware—not by cabinet count

Create a migration register for every charger family. Record the model, serial range, hardware revision, firmware version, OCPP version and transport, enabled functions, connectivity method, present management-system identity and responsible service party. Grouping one hundred visually identical cabinets together is unsafe if several firmware baselines or modem configurations exist.

OCA's current migration whitepaper recommends testing each charging-station model with the new management system and notes that different software versions may expose different functions and configurations. It also describes several possible configuration routes—remote, firmware-based, scripted or manual—whose applicability depends on the station and the cooperation available. Use that as a planning framework, not as authorization to issue commands. Source: OCA, Migrating Charging Stations.

3. Test one controlled cohort before the fleet

Select a small but representative pilot: every relevant charger model, important firmware branch, connector type and connectivity arrangement. Freeze the baseline before testing. Agree the permitted change, maintenance window, success criteria, monitoring period and rollback trigger with the charger manufacturer, old platform, new platform and site operator.

A useful pilot checks more than “online.” Verify station identity and connector mapping, authorization, session start and stop, meter and transaction records, remote operations that are actually in scope, time synchronization, alarms, diagnostics, restart recovery, offline/reconnection behavior and any project-specific load-management or payment flow. Capture the result per model and firmware; do not generalize one successful charger to an untested fleet.

OCA states that OCPP 1.6 and OCPP 2.0.1 are not compatible. Buyers should specify the actual version and functions on both sides rather than treating the word OCPP as a universal plug-and-play certificate. Source: OCA FAQ.

4. Separate four migrations that can fail independently

1. Charger connectivity: the station establishes an authenticated, stable connection to the intended management system.
2. Operational configuration: connector mapping, limits, availability, authorization and any local behaviors match the approved site design.
3. Commercial and customer data: agreed user, tariff, transaction, invoice and payment references are transferred or deliberately retained, then reconciled.
4. People and process: operations, customer service, maintenance and finance teams know the new tools, escalation paths and responsibility boundaries.

Do not mark the migration complete because the dashboard shows a green status. A charger may be online while transactions reconcile incorrectly, a payment start path fails, a service team lacks access or an old cellular contract is about to expire. Each workstream needs its own acceptance owner and evidence.

5. Design rollback before the first change

Define how long the former platform, credentials and data access remain available; which party can restore the previous configuration; how failed chargers are isolated; and when an on-site visit becomes necessary. Keep a controlled copy of the approved pre-change configuration and inventory. The rollback plan must include the business records created during the pilot so that restoring connectivity does not silently lose or duplicate transactions.

For a staged rollout, set stop conditions using observed results: repeated connection loss, incorrect connector identity, missing transaction records, rejected authorizations, payment reconciliation differences or an unresolved cybersecurity event. Choose thresholds with the responsible technical and commercial teams; this article does not prescribe universal limits.

6. Require a migration evidence pack

• Approved charger inventory and model/firmware compatibility matrix.
• Roles for owner, outgoing platform, incoming platform, charger supplier, telecom provider and field-service team.
• Pilot plan, permitted changes, maintenance window, rollback and escalation contacts.
• Model-specific test results, deviations, corrective actions and retest evidence.
• Data-export specification, sample validation, transfer record and reconciliation sign-off.
• Security, credential and certificate handover approved by the responsible parties.
• Training and operating-document handover for support, maintenance and finance.
• Phased rollout record, monitoring period, open issues and final acceptance owner.

Certification can support conformance evidence, but it is version- and implementation-specific. OCA's program independently tests charging-station or management-system implementations for OCPP 1.6 or 2.0.1. Verify an actual product and certificate rather than assuming that a company name or protocol logo covers every model and firmware release. Source: OCA certification program.

Related buyer guides

• Offline operation and transaction recovery
• Factory and site acceptance evidence
• Fault reporting before intervention

Primary sources reviewed 10 September 2026. This is Xiaochong's original procurement checklist. It is not an OCA endorsement, a migration warranty, a cybersecurity procedure or evidence that any Xiaochong model holds OCPP certification. Final requirements need project-specific qualified review.