01
Inventory
Build a source-of-truth list for sites, chargers, connectors, firmware, credentials, users, tariffs, and integrations.
Move without losing operational context
EV charging network migration with a controlled cutover plan
Sock8 migrations separate charger cutover, business-data transfer, driver transition, and integration change into workstreams that can be tested and sequenced before production day.
The objective is continuity, not a blind endpoint swap. Charger firmware and configuration, OCPP parity, tariffs, users, sessions, payment dependencies, roaming, reporting, and rollback conditions are reviewed before batches move.
Who it is for
Built for teams accountable for live charging.
- CPOs leaving a legacy CSMS
- Networks consolidating regional platforms
- Operators acquiring an existing charger estate
- Hardware vendors replacing a bundled backend
Problems it solves
Replace operational blind spots with one system.
- Unknown charger configuration at field sites
- Data locked in legacy exports
- Driver and payment disruption during cutover
- No rollback or reconciliation plan
How it works
A clear path from connection to daily operation.
02
Map
Translate source data and operating rules into Sock8 records and identify gaps or transformations.
03
Pilot
Move representative charger models and one operational slice, then reconcile sessions and downstream data.
04
Cut over
Move approved batches with monitoring, exception handling, stakeholder communication, and rollback criteria.
Product view
See the operating detail behind the promise.
Migration monitoring keeps onboarded connectors, live status, sessions, and exceptions visible during each rollout wave.
Representative Sock8 product interface
Features
Capabilities included in the product scope.
- Charger and firmware inventory
- OCPP behaviour comparison
- Data mapping and import planning
- Pilot and batch migration
- Live cutover monitoring
- Post-cutover reconciliation
Protocols and interfaces
Designed to connect the charging stack.
OCPP 1.6JOCPP 2.0.1OCPI 2.2.1OICP integrationsSource exportsREST APIs
Implementation or migration
Move from technical discovery to a controlled launch.
- 1
Discovery
Confirm migration scope, system access, contractual constraints, data availability, and business deadlines.
- 2
Parity and mapping
Compare protocol, operational, commercial, integration, and reporting requirements against the target platform.
- 3
Pilot migration
Move a controlled sample, test full transactions and support flows, and resolve exceptions.
- 4
Wave rollout
Execute approved batches, reconcile results, retire source dependencies, and close the transition.
Customer evidence
400+ connectors moved in six weeks
6 wks to migrate · 400+ connectors
Echarge Moldova · Moldova
The network replaced a legacy CSMS and unified multiple charger brands under one branded operation.
Evidence shown is limited to the named deployment facts currently approved for this site.
Deployment
Choose the operating boundary.
Migrations can target Sock8-managed white-label cloud or an approved customer-hosted environment.
Pricing information
Scope the commercial model.
Migration is scoped separately from recurring platform pricing. Cost depends on charger volume and diversity, source exports, integrations, environments, and cutover support.
View platform pricingBuyer FAQs
Questions technical and commercial teams ask.
Can a network migrate without visiting every charger?+
Sometimes, if the current platform or charger-management method supports a secure remote endpoint change. Field access is planned where remote change is unavailable.
What data can be migrated?+
Available exports are assessed for sites, chargers, users, RFID records, tariffs, transactions, and other required records; not every source exposes every dataset.
How is downtime reduced?+
Representative pilots, small rollout waves, monitoring, predefined rollback conditions, and reconciliation reduce cutover risk.
Can mixed charger brands move together?+
They can be part of one programme, but model and firmware groups are validated separately before their rollout wave.
What happens to historical sessions?+
The team agrees whether history is imported, archived for reporting, or retained in the source system based on data quality and access.
Next step