Switching fleet charging providers: Migrate data, cards and billing cleanly

When switching fleet charging providers, you must manage charging access, master data and billing as separate tasks. New cards should only become the primary access method once they work and the first sessions are correctly assigned. Old invoices and supporting records must remain available. With a defined cutover date, controlled parallel operation and clear completion criteria, you can carry out the switch transparently.

First define exactly what the provider switch covers

Changing cards for public charging does not automatically mean changing the software for your company charge points. Home charging reimbursement may also have its own contract and data connection. List every affected service: cards, app accounts, billing, home charging, workplace operations and support.

If charge points are also moving to a new backend, a technical migration plan is required. The Mobility House describes charging infrastructure migration as replacing the management software while continuing to use the hardware. This is a separate workstream involving compatibility, access and configuration. The following steps focus on switching fleet charging access and its billing.

For each service, record the contracting party, term, notice period and responsible person. Check whether services are bundled or must be terminated separately. A new card does not end an old contract.

Secure the starting position before making changes

Export the master data and supporting records you need while the existing access is still fully available. This includes card inventory, driver and vehicle references, assignment periods, invoices, transaction reports and open correction cases. Check files for readability and completeness; successfully clicking download is not the same as verifying a backup.

Define a storage location with appropriate access rights and a person responsible for maintaining it. Your business determines which documents must be retained and for how long under the applicable requirements. Do not automatically transfer all historical personal data to the new provider. Active master data may be enough to start; old supporting records can remain in your own archive.

Create a mapping table between old and new references. For example, it links the old card ID, internal vehicle ID and new card ID. The internal vehicle reference should remain stable. This makes it possible to understand later why the same vehicle has different identifiers in two providers' reports.

Check card transferability instead of assuming it

An existing physical card cannot generally be taken to every new provider. It depends on the card and contract model and the technical capabilities. Request specific confirmation for your card inventory. A statement about reusing local RFID access is not automatically a commitment for public roaming.

If new cards are needed, maintain an issue log. Each card should have a recipient, an intended purpose and an activation status. Do not wait until the first long-distance trip to discover whether the card is assigned to the correct corporate account.

App access and stored payment profiles also need attention. An employee may have a new card but still charge in the app using the old or a personal profile. Explain the intended future process and test it in practice.

Plan the cutover with finance

Switching at month-end can make oversight easier, but it does not guarantee a clean separation of all records. Charging sessions may be reported later, credit notes may arrive afterwards and invoice periods may differ from the service date. Define the rule used to allocate new and old sessions.

The existing guide to consolidated invoices for EV fleets describes the normal month-end process. During the switch, add a second register for late-arriving items. Record expected amounts, provider, status and responsible person.

Run the systems in parallel for a limited period

Parallel operation makes sense when the old access method is temporarily needed as a reliable fallback. Define in advance who may use it, in which cases and for how long. Otherwise, two cards may continue to be used equally and the intended simplification will not materialise.

Calculate possible duplicate fees during this transition. They are part of the switching costs. Parallel operation ends not merely on a calendar date, but once the specified criteria are met: active new access accounts, successful use of critical routes, resolved billing and available support.

Document every fallback to the old provider. Distinguish a technical fault from a forgotten profile selection or a charging location that has not yet been checked. This determines whether a brief explanation is enough or the rollout should be paused.

Define a fallback plan with clear decision rules

Set out which problems stop the next migration group. Examples include unusable access on business-critical routes, systematically incorrect invoice recipients or unresolved vehicle assignments. Individual convenience issues can be treated differently from an inability to charge.

Falling back to the old system is only possible while the contract, cards and access accounts are actually active. Confirm this status and the associated costs. Access that has already been terminated and blocked is not a reliable contingency plan.

Name a person authorised to continue, limit or temporarily suspend the switch. Drivers need a clear contact during the transition. Procurement, fleet management and finance should not issue separate instructions for the same card.

Close down the old operation in a controlled way

Block or terminate old cards using the agreed procedure and document confirmation. Maintain a list of outstanding invoices and credit notes. The date a card is returned is not automatically the date its contractual use ends.

Finally, check that all necessary data is in the designated archive and whether access is needed for remaining late-arriving items. If required and available, agree restricted read-only access or a final complete export. These conditions belong in the switching plan, not merely in the last support request.

Then produce a brief completion note: migrated users, terminated contracts, outstanding residual cases and transition costs. Operationally, a provider switch is complete when the fleet works in the new process and the old arrangements have been closed out apart from explicitly documented late-arriving items.

Prepare the switch using your existing setup

StromNow Business offers driver access, central billing and exportable cost reports. Which existing data can be transferred, which cards are needed and how your switch will be organised must be clarified against the specific offer. This is not a promise of automatic migration from a particular third-party system.

For a provider-switch discussion with StromNow, bring a contract overview, card inventory, an anonymised data export and your preferred migration period. These provide the basis for a verifiable transition plan with responsibilities and clear completion criteria.