{"id":5548,"date":"2026-11-09T14:59:37","date_gmt":"2026-11-09T06:59:37","guid":{"rendered":"https:\/\/xinya-ee.com\/blog\/switch-ev-charging-software-platforms\/"},"modified":"2026-11-09T14:59:40","modified_gmt":"2026-11-09T06:59:40","slug":"switch-ev-charging-software-platforms","status":"publish","type":"post","link":"https:\/\/xinya-ee.com\/fr\/blog\/switch-ev-charging-software-platforms\/","title":{"rendered":"Comment passer d\u2019une plateforme de gestion de la recharge des v\u00e9hicules \u00e9lectriques \u00e0 une autre sans remplacer les chargeurs"},"content":{"rendered":"<article>\n<style>.xydf-migration{min-width:0;max-width:100%;overflow-wrap:anywhere}.xydf-migration p{margin:0 0 1.2em;line-height:1.75}.xydf-migration h2{margin:1.8em 0 .8em}.xydf-migration h3{margin:1.5em 0 .6em}.xydf-migration figure{margin:2em 0}.xydf-migration figcaption{font-size:.9em;color:#555;line-height:1.5;margin-top:.65em}.xydf-migration .table-scroll{max-width:100%;overflow-x:auto;margin:1.5em 0}.xydf-migration table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:.94em}.xydf-migration th,.xydf-migration td{padding:12px;border:1px solid #dbe1e9;vertical-align:top;overflow-wrap:anywhere}.xydf-migration th{background:#f0f3f8;text-align:left}.xydf-migration li{margin-bottom:.7em}.xydf-migration .references li{margin-bottom:1em}@media(max-width:600px){.xydf-migration table{min-width:620px}}<\/style>\n<div class=\"xydf-migration\">\n<p>You can switch EV charging software platforms without replacing your chargers if the installed hardware supports the new platform, you can change its connection settings, and the functions your site needs pass testing. The change usually involves moving the chargers to a new charge point management system (CPMS), transferring operational records and rebuilding services such as access control and billing. An OCPP logo alone does not confirm that all of this will work.<\/p>\n<p>A successful <strong>EV charging software migration<\/strong> keeps usable hardware in service while preserving the driver&#8217;s ability to charge and the operator&#8217;s ability to control, monitor and reconcile sessions. Start with an asset audit, test a representative charger, then move the remaining equipment in manageable batches.<\/p>\n<h2>Can your existing EV chargers move to another platform?<\/h2>\n<p>First, ask the new provider to confirm support for the exact charger model, installed firmware and enabled OCPP version. A platform&#8217;s general compatibility statement is less useful than a tested configuration matching the units already on your site. Identify any functions delivered through a proprietary extension or a separate service, because those may need additional integration.<\/p>\n<p>OCPP is the communication protocol between an EV charger and its management system. Our <a href=\"https:\/\/xinya-ee.com\/blog\/ocpp-ev-charger-guide\/\">OCPP charger guide<\/a> explains that relationship. For migration, the practical question is whether your particular hardware and the proposed backend can perform the operations you actually use.<\/p>\n<p>The Open Charge Alliance explicitly states that OCPP 1.6 and OCPP 2.0.1 are not compatible. A new platform can support both, but a 1.6 charger needs a compatible 1.6 connection unless the manufacturer provides a supported upgrade. Switching providers does not itself upgrade the charger. Review the <a href=\"https:\/\/xinya-ee.com\/blog\/ocpp-1-6-vs-ocpp-2-0-1\/\">OCPP 1.6 and 2.0.1 differences<\/a> when deciding which functions the migration must retain.<\/p>\n<p>OCA certification provides independent evidence of conformance to a protocol specification. It does not replace a site acceptance test covering your payment provider, driver accounts, network connection and load controls. Request the applicable certificate and implementation details, then test the complete service.<\/p>\n<h2>Check ownership and access before ending your current contract<\/h2>\n<p>Hardware ownership and configuration access are separate questions. You may own the charger but still depend on the current operator or manufacturer to change its backend address. Confirm who can authorize that change, how it is performed and whether an onsite visit is required. Arrange this before terminating the service that currently provides remote access.<\/p>\n<div class=\"table-scroll\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">What to confirm<\/th>\n<th scope=\"col\">Evidence to obtain<\/th>\n<th scope=\"col\">Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Hardware and firmware support<\/td>\n<td>Model, firmware, enabled protocol and new-provider compatibility confirmation<\/td>\n<td>A similar model or different firmware may behave differently.<\/td>\n<\/tr>\n<tr>\n<td>Configuration permissions<\/td>\n<td>Authorized administrator, approved change procedure and recovery access<\/td>\n<td>You need a supported way to change and restore the backend connection.<\/td>\n<\/tr>\n<tr>\n<td>Connectivity and security<\/td>\n<td>SIM or network ownership, allowed destinations and required authentication method<\/td>\n<td>The new platform must be reachable using the charger&#8217;s supported security settings.<\/td>\n<\/tr>\n<tr>\n<td>Commercial exit terms<\/td>\n<td>Notice period, export rights, termination charges and support end date<\/td>\n<td>Contract restrictions can delay an otherwise feasible migration.<\/td>\n<\/tr>\n<tr>\n<td>Dependent services<\/td>\n<td>Payment, roaming, RFID, app and energy-management responsibilities<\/td>\n<td>These services may require separate changes beyond OCPP configuration.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Handle passwords and certificates through an approved secure handover process. Do not place private keys or administrator passwords in a shared asset spreadsheet. Where the new service requires new credentials, provision those credentials rather than assuming the previous provider&#8217;s secrets can be reused.<\/p>\n<p>For sites using <a href=\"https:\/\/xinya-ee.com\/product\/22kw-commercial-ev-charger\/\">commercial AC chargers<\/a>, check whether authorization and site load control depend on a local controller as well as the cloud service. For <a href=\"https:\/\/xinya-ee.com\/product\/240kw-all-in-one-ev-charger\/\">DC charging stations<\/a>, include each connector and any payment or power-sharing arrangement in the review. These are checks for the installed configuration, not a promise that every model supports every platform.<\/p>\n<h2>Build one asset record before changing any connection settings<\/h2>\n<p>Create an inventory that connects the physical charger to its records in both systems. Record its serial number, firmware, charger identity, connector numbering, site location, network connection and current operating limits. The incoming provider should explain how these identities will map to its own records. Preserve public-facing station identifiers where required by your roaming and payment arrangements.<\/p>\n<p>Keep a supported configuration backup and note which settings are stored in the charger, a local controller or the old platform. Document site-wide limits separately from individual charger ratings. A site with adequate capacity for one unit may still need coordinated limits when several vehicles charge together.<\/p>\n<figure data-image-role=\"inventory\"><img src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/11\/20261109-platform-migration-inventory.webp\" alt=\"Illustrative pre-migration asset review beside a real XYDF charger, with model, firmware and access checklist\" width=\"1536\" height=\"1024\" loading=\"lazy\" decoding=\"async\" style=\"width:100%;max-width:100%;height:auto;display:block;\" class=\"wp-image-5546\" \/><figcaption>Before migration, match the installed charger to its model, firmware and configuration permissions. The scene is illustrative.<\/figcaption><\/figure>\n<h2>Agree on which records and services will transfer<\/h2>\n<p><strong>CPMS migration<\/strong> includes more than reconnecting hardware. Agree with both providers on what can be exported, what the new platform can import and what must remain in a separate archive. Ask for a sample export early enough to discover missing fields before the old contract ends.<\/p>\n<p>Useful records include charging sessions, energy readings, timestamps with time zones, tariff versions, invoices, refunds and fault history. Map the old and new identifiers so a session can still be traced to the right charger and connector. Reconcile a sample of historical records against the original reports before accepting the export.<\/p>\n<p>Driver accounts, RFID permissions, subscriptions and payment credentials need separate treatment. Some may be portable; others may require account re-enrollment or action by the payment provider. Do not assume payment tokens can be transferred between processors. Confirm the lawful handling of personal data, retention responsibilities and the driver&#8217;s experience before making announcements.<\/p>\n<p>Optimo&#8217;s published migration guidance emphasizes preserving site constraints, operational identities and historical data alongside the platform connection. That distinction is useful for any operator: a charger appearing online does not prove that its business records or charging rules survived the move.<\/p>\n<h2>Run a pilot that checks a complete charging session<\/h2>\n<p>Select a pilot that represents the equipment and services you will move. If the network contains different charger models, firmware versions or connectivity arrangements, one successful unit does not validate all of them. Build a small test group covering those differences before scheduling the wider rollout.<\/p>\n<p>Start with connection and registration, then test the user&#8217;s actual journey through authorization, charging, stopping and receipt or reporting. Agree on pass criteria and a person responsible for each result. Retain logs and transaction references so a failed step can be investigated without repeating the entire test.<\/p>\n<div class=\"table-scroll\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">Pilot check<\/th>\n<th scope=\"col\">What a pass should demonstrate<\/th>\n<th scope=\"col\">Evidence to keep<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Connection and identification<\/td>\n<td>The correct station and connector appear under the intended site.<\/td>\n<td>Registration record and mapped identities<\/td>\n<\/tr>\n<tr>\n<td>Driver authorization<\/td>\n<td>Each required access method accepts valid users and handles invalid ones correctly.<\/td>\n<td>Test account or token reference and result<\/td>\n<\/tr>\n<tr>\n<td>Start, stop and session reporting<\/td>\n<td>A complete session produces consistent timestamps, energy data and an appropriate end state.<\/td>\n<td>Charger and platform records for the same session<\/td>\n<\/tr>\n<tr>\n<td>Tariff and payment handling<\/td>\n<td>The test charge follows the configured tariff and reaches the intended settlement or reporting process.<\/td>\n<td>Receipt, transaction reference and reconciliation<\/td>\n<\/tr>\n<tr>\n<td>Site limits and schedules<\/td>\n<td>Configured controls behave as intended under representative concurrent demand.<\/td>\n<td>Approved settings and observed test results<\/td>\n<\/tr>\n<tr>\n<td>Connection loss and recovery<\/td>\n<td>The documented offline behavior and record recovery work in a controlled test.<\/td>\n<td>Outage, reconnection and recovered-session logs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Include only the payment and access methods the site actually offers. A private fleet depot and an open public station have different acceptance needs. Any electrical or load-control test should follow the site&#8217;s approved procedure and involve qualified personnel where required.<\/p>\n<figure data-image-role=\"pilot\"><img src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/11\/20261109-platform-migration-pilot.webp\" alt=\"Illustrative pilot review at an outdoor XYDF charging station with authorization, session and site-limit checks\" width=\"1536\" height=\"1024\" loading=\"lazy\" decoding=\"async\" style=\"width:100%;max-width:100%;height:auto;display:block;\" class=\"wp-image-5547\" \/><figcaption>Pilot acceptance should cover authorization, session records and site controls, rather than only an online status. The scene is illustrative.<\/figcaption><\/figure>\n<h2>Move chargers in batches with a working rollback plan<\/h2>\n<p>Before the first production change, define the <strong>charger migration rollback plan<\/strong>: who can restore the old connection, which settings and credentials are needed, how long the old service remains available, and which failures trigger a return. Test the recovery procedure on the pilot where practical. A configuration backup is useful only if someone can restore it through a supported process.<\/p>\n<p>Schedule each batch during a suitable service window. Allow active sessions to end according to the agreed procedure, record the cutover time and confirm there are no unresolved transactions before changing connections. Do not assume a session will continue seamlessly across two backends.<\/p>\n<p>After the batch connects, repeat the agreed acceptance checks and review faults before releasing the next batch. Keep an explicit stop condition, such as failed authorization, incorrect charges or missing site controls. Continuing a rollout while these remain unresolved multiplies the work needed to recover.<\/p>\n<p>Retain the previous provider&#8217;s access until the agreed observation and reconciliation period is complete. If the old service has already closed, rollback may no longer be possible; an alternative recovery arrangement must be agreed in advance.<\/p>\n<h2>Budget for the handover work as well as the new subscription<\/h2>\n<p>The cost of <strong>switching EV charging platforms<\/strong> may include configuration labor, site visits, connectivity changes, data exports, integration work, driver communications and temporary overlap between subscriptions. Obtain a written scope showing who handles each item and which costs depend on the pilot result.<\/p>\n<p>There is no reliable universal migration duration. A remotely configurable charger with tested compatibility can require much less work than a mixed network with restricted access and separate payment contracts. Ask for a schedule based on your inventory and acceptance requirements rather than a fixed promise based only on charger count.<\/p>\n<p>Replacement becomes a separate decision if a charger cannot support the required connection, lacks a supported recovery path or cannot deliver essential functions with the new system. Do not replace working equipment merely because the platform changes, but do not assume software can overcome a hardware or contractual limitation.<\/p>\n<h2>Questions about changing EV charging software<\/h2>\n<h3>Can I change my EV charging software provider and keep the same chargers?<\/h3>\n<p>Often yes, provided the new provider supports your installed model, firmware and protocol, and you have authorized access to change the connection settings. Confirm data-export rights and test the services you need before ending the current contract.<\/p>\n<h3>How do I know whether my charger supports OCPP?<\/h3>\n<p>Check the manufacturer&#8217;s documentation and the installed firmware or configuration records. Ask which OCPP version is enabled and whether backend settings can be changed. Where certification is claimed, verify the relevant certificate rather than relying only on a product-family description.<\/p>\n<h3>Do I need to upgrade from OCPP 1.6 to 2.0.1 to switch platforms?<\/h3>\n<p>Not necessarily. You can retain OCPP 1.6 if the new platform supports your implementation and required functions. OCPP 1.6 and 2.0.1 are not directly compatible, so changing to 2.0.1 requires a manufacturer-supported path rather than just a new backend address.<\/p>\n<h3>Will charging history and RFID cards transfer automatically?<\/h3>\n<p>Do not assume they will. Historical records require an agreed export and import or archive process. RFID credentials need mapping and testing in the new authorization system, and subscriptions or payment accounts may need separate migration arrangements.<\/p>\n<h3>Can chargers keep working while the platform is being changed?<\/h3>\n<p>That depends on the charger&#8217;s documented offline behavior, active sessions and local controls. Plan a service window and test recovery. Do not promise uninterrupted charging unless the exact configuration and cutover procedure have demonstrated it.<\/p>\n<h2>Keep the chargers only after the new service has proved itself<\/h2>\n<p>Switching charging software can preserve useful hardware, but the decision should rest on verified compatibility, configuration access and a complete operational handover. Secure the records and recovery arrangements first, prove the required functions on a representative pilot, and expand only after sessions, payments and site controls pass their checks. This makes the migration a controlled service change rather than a gamble on an OCPP label.<\/p>\n<p>Planning to move an existing XYDF installation? <a href=\"https:\/\/xinya-ee.com\/contact-us\/\">Contact XYDF<\/a> with the charger model, firmware version, current platform and proposed provider so the hardware configuration and compatibility questions can be reviewed before you commit to a cutover date.<\/p>\n<h2>References<\/h2>\n<ol class=\"references\">\n<li><a href=\"https:\/\/openchargealliance.org\/protocols\/open-charge-point-protocol\/\" target=\"_blank\" rel=\"noopener\">Open Charge Alliance: Open Charge Point Protocol<\/a>. Protocol versions, functionality and the incompatibility between OCPP 1.6 and 2.0.1.<\/li>\n<li><a href=\"https:\/\/openchargealliance.org\/certificationocpp\/\" target=\"_blank\" rel=\"noopener\">Open Charge Alliance: OCPP certification program<\/a>. Independent conformance validation for OCPP implementations.<\/li>\n<li><a href=\"https:\/\/www.optimoenergy.io\/news-and-insights\/how-to-switch-cpms-without-replacing-ev-chargers\" target=\"_blank\" rel=\"noopener\">Optimo: How to switch CPMS without replacing EV chargers<\/a>. Practical migration considerations covering configuration access, site constraints and data continuity.<\/li>\n<\/ol>\n<\/div>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Can I change my EV charging software provider and keep the same chargers?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Often yes, provided the new provider supports your installed model, firmware and protocol, and you have authorized access to change the connection settings. Confirm data-export rights and test the services you need before ending the current contract.\"}},{\"@type\":\"Question\",\"name\":\"How do I know whether my charger supports OCPP?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Check the manufacturer's documentation and the installed firmware or configuration records. Ask which OCPP version is enabled and whether backend settings can be changed. Where certification is claimed, verify the relevant certificate rather than relying only on a product-family description.\"}},{\"@type\":\"Question\",\"name\":\"Do I need to upgrade from OCPP 1.6 to 2.0.1 to switch platforms?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Not necessarily. You can retain OCPP 1.6 if the new platform supports your implementation and required functions. OCPP 1.6 and 2.0.1 are not directly compatible, so changing to 2.0.1 requires a manufacturer-supported path rather than just a new backend address.\"}},{\"@type\":\"Question\",\"name\":\"Will charging history and RFID cards transfer automatically?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Do not assume they will. Historical records require an agreed export and import or archive process. RFID credentials need mapping and testing in the new authorization system, and subscriptions or payment accounts may need separate migration arrangements.\"}},{\"@type\":\"Question\",\"name\":\"Can chargers keep working while the platform is being changed?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"That depends on the charger's documented offline behavior, active sessions and local controls. Plan a service window and test recovery. Do not promise uninterrupted charging unless the exact configuration and cutover procedure have demonstrated it.\"}}]}<\/script><br \/>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>Configurer le logiciel de charge des v\u00e9hicules \u00e9lectriques sans remplacer les chargeurs compatibles. V\u00e9rifiez la compatibilit\u00e9 avec OCPP, l\u2019acc\u00e8s \u00e0 la configuration, la transmission des donn\u00e9es, les tests pilotes et le retour en arri\u00e8re avant de proc\u00e9der \u00e0 une migration.<\/p>","protected":false},"author":8,"featured_media":5545,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,24],"tags":[],"product-features":[],"class_list":["post-5548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-newsblog"],"_links":{"self":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts\/5548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/comments?post=5548"}],"version-history":[{"count":1,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts\/5548\/revisions"}],"predecessor-version":[{"id":5549,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts\/5548\/revisions\/5549"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/media\/5545"}],"wp:attachment":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/media?parent=5548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/categories?post=5548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/tags?post=5548"},{"taxonomy":"xinya_product_feature","embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/product-features?post=5548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}