Skip to content
acharge by acemo

Changing provider

Switch backend, keep your charge points

When a backend is discontinued or stops fitting, the charge point is rarely the problem. Charge points that speak OCPP can be re-pointed at another system — as a rule without new hardware and without a technician on site.

Have compatibility checked Why backends disappear

First step

Five data points settle the question

Whether your estate can be connected is not a matter for negotiation but a technical question with a definite answer. These five data points are enough to settle it — no site visit, and nobody offering you a new wallbox first.

  1. 1

    Manufacturer and model

    The model designation from the rating plate, not the product family from the brochure.

  2. 2

    Firmware version

    Shown in the station's web interface. It decides which OCPP is actually spoken — not the datasheet.

  3. 3

    Access to the configuration

    Do you have the credentials for the web interface? That is the real hurdle in a switch, not the protocol.

  4. 4

    Number of charge points

    And whether they sit at one site or several. That governs sequencing, not feasibility.

  5. 5

    Type of connection

    LAN, Wi-Fi or cellular. On cellular the SIM often belongs to the old provider and is deactivated with the contract.

  6. Got all five? Then the answer usually comes back the same day.

    Send them over

Starting point

Where you are coming from

The starting point does not decide whether a switch is possible — the firmware does. It decides where the check begins.

Previous system Typically installed Where the check starts
EVBox / Everon EVBox Elvi, BusinessLine Everon was switched off on 1 December 2025. The charge points are undamaged by that — what gets checked is the firmware level and whether the configuration interface is reachable.
reev usually ABL Hardware-and-software bundles. The installed station normally speaks OCPP; the thing to settle is who holds the station's credentials.
E.ON Drive often Alfen, Compleo Also sold as a package. Alfen and Compleo speak OCPP; the questions are the firmware level and whether a provider-owned SIM sits in the device.
Manufacturer portal Wallbox makers with their own cloud Fine while the portal exists and you run only that one manufacturer. The moment a second make arrives you need a vendor-independent backend anyway.
No backend Standalone operation, RFID list on the device Not a switch but a first connection — technically the easier case. What gets checked is whether the station has OCPP enabled at all.

Statements about third parties follow publicly available sources. Which hardware is actually installed in your case, and at which firmware level, can only be established at the device — hence the check.

How it runs

Six steps, in this order

The order is not arbitrary. Steps two and three are the ones that cannot be made up once the old system is gone.

  1. 1

    Take stock

    Manufacturer, model, firmware and connectivity per charge point. A spreadsheet is enough, and it doubles as the cutover plan later.

  2. 2

    Secure access

    Obtain and document credentials for every station's web interface. The step with the longest lead time — and the only one nobody can accelerate for you.

  3. 3

    Export the data

    Sessions, records, user and card list, tariffs, master data. While the old account is still open. Afterwards the history is gone; the retention obligation is not.

  4. 4

    Migrate one charge point as a test

    Enter the endpoint URL, restart the station, approve it in the portal, run one complete session with meter values and a record. Only when that one is clean does the rest follow.

  5. 5

    Migrate the remaining charge points

    Site by site, in a window without operations. The interruption per charge point is essentially one restart.

  6. 6

    Go live with users, tariffs and billing

    Map the cards, set the prices, enable the billing run and roaming where relevant. Do not put the cutover on a billing date.

Why a backend disappears at all, what a switch involves at protocol level, and which 2028 deadline applies to older cellular charge points: the full article.

Afterwards

What you have once you have moved

aCharge Cloud is not merely a spare part for the system that went away — it is the occasion to pick up what was missing before.

From €2 per charge point per month. Compliant billing, access control and tariffs are included — there is no separate fee for being allowed to take money. All prices.

Across manufacturers

OCPP 1.6, 1.6 Security and 2.0.1 over WebSocket, AC and DC, mixed makes in one installation.

Metrology-compliant billing

Signed datasets, OCMF, automatic billing run with SEPA or card collection.

Access and tariffs

RFID cards, user groups, prices per site and time window, vouchers, ad-hoc charging by QR code without registration.

Roaming

Hubject (OICP 2.3) and OCPI 2.2.1 with automated payouts, so other providers' cards work at your sites.

Under your brand

Portal, app and invoices in your own name. Your end customers do not notice a change behind the scenes.

Operated in Germany

Developed in Aachen, operated in German data centres, German-language support.

Next

Depending on what you are working out

Technical

What connects

Versions, transport, and the five faults connections trip over.
Hardware

Tested charge points

Which manufacturers aCharge runs with in the field.
Product

aCharge Cloud

The feature set in detail, including price per charge point.

Frequently asked

About the switch itself

What does the compatibility check cost?
Nothing. You tell us manufacturer, model, firmware version, number of charge points and whether you can reach the configuration interface; you get an assessment of whether and how the estate can be connected. A quote follows only after that.
We do not have the credentials for the charge point. What now?
The most common stumbling block, and a solvable one. The credentials usually sit with the installer or the previous provider and can be requested. Failing that, many manufacturers document a reset procedure on the device. Settle it early — it has the longest lead time of any step.
Does a technician have to be on site?
Usually not. Reconfiguration happens through the charge point's web interface, after which the station registers itself with the new backend. A site visit becomes necessary if the station is only reachable locally, if firmware has to be applied over USB, or if connectivity moves from cellular to LAN.
Can we keep charging during the cutover?
The interruption per charge point is essentially one restart. A session running at that moment is either terminated or continued locally depending on the manufacturer, so the cutover goes in a window without operations. Across several sites you migrate in sequence, not all in one evening.
What happens to our users' charging cards?
The cards themselves stay usable — what is read is the UID, and that does not change. What has to be rebuilt is the mapping: which UID belongs to which person, vehicle or cost centre. Export that list before the old account closes; without it, every card has to be enrolled again.
Is this worth it for a single wallbox?
Technically the process is the same for one charge point or two hundred. Economically it depends on what you need: if you only want to charge, a single wallbox often needs no backend at all. As soon as billing, attribution or multiple users are involved, the arithmetic changes.