There’s a pattern in how most CPO migration conversations start. The technical questions come first, because those feel concrete and answerable. How long will this take? Will my chargers go offline? What data can we bring over?
But underneath those questions are bigger ones that tend to stay unasked: Are we doing this for the right reasons? Do we have the right people for this? What if we get halfway through and regret the whole thing?
In a recent webinar, AMPECO’s Charlie O’Donoghue and Mariana Mota sat down to answer both types of questions — the surface-level ones and the ones below the surface. Here’s what they covered.
Migration as a business project first, tech project second
The session opened with an analogy worth holding on to. Watch a flock of birds moving across the sky, and you’re watching distributed coordination in action. No central controller, no master plan. Just three rules operating at the local level: avoid collisions, align with your neighbors, stay connected to the group.
EV charging network migrations work the same way. You have chargers, roaming platforms, payment systems, apps, operations teams, finance teams, B2B partners. They all need to move together. The best migrations are the ones that feel almost invisible from the outside.
What makes that possible isn’t the technology. Migrating the technical infrastructure, the charge point connections over OCPP, is the relatively straightforward part. What takes time and requires serious attention is the business and commercial logic: your tariff structures, your contract terms with B2B partners, your integrations with ERPs and CRMs, your pricing and billing logic. These don’t translate one-to-one between platforms. Getting them right is where migrations succeed or fall apart.
This leads to an important reframing of the common definition: a migration is not a technology project. It’s a business redesign, and the technology is what makes it possible. If you go into one trying to recreate today’s processes in tomorrow’s platform, you capture cost but miss the value. The move is an opportunity to challenge old assumptions, drop things that aren’t working, and set up for growth rather than just continuity.
Mariana’s phrase for it: repotting a growing tree. You’re not moving the tree to the same-sized pot. You’re creating space for what comes next.
Why migrations happen — and why the reasons have changed
CPO migrations tend to arrive through one of two routes.
The first is a strategic decision made at the board level: running a proprietary platform is no longer a fit with the company’s direction, and resources need to go elsewhere. Teams are organized to make that happen. The second is operational pain: sales teams can’t serve certain markets, customer-facing features are missing, and operations are held back by platform limitations. Teams push for change because the current state is a ceiling.
Both scenarios have become more common, but their character has shifted over the past decade. Mariana’s first migration, nine years ago, was squarely in the “only option” category. A generic IoT platform managing EV chargers alongside snow blowers, coffee machines, and vending machines eventually collapsed under that weight. Moving wasn’t a strategic choice; it was the only sensible exit.
What’s different now is the question driving the conversation. It used to be “what’s broken?” Today it’s “what’s possible?” Operators are migrating because they see what they want to build and their current platform can’t get them there. That shift in motive, from necessity to ambition, changes everything about how a migration is scoped, resourced, and run.
The questions that come up every time
How long does it take?
The honest answer is that it depends on complexity, and complexity in a migration is about the business model more than the charger count. A CPO running thousands of charge points with a simple, direct commercial model may have a faster migration than a network with a few hundred charge points spread across multiple countries, multiple customer types, and complex contractual arrangements.
That said, six months is a reasonable floor for a complex migration. Factors that extend it include heavy integration requirements (ERP, CRM, data warehouse), large amounts of custom business logic, and the organizational equivalent of attic cleanup: configurations and processes that have accumulated over the years and need to be sorted before anything can move.
The renovation analogy holds here, too. If you’ve been spring-cleaning every year, you’re ready to move. If you’ve been throwing things in the attic since 2010, you have more decisions to make before the boxes start packing.
Will the chargers go offline?
This question used to carry real weight. Today, the industry has solved this. The switch itself, typically done with AMPECO clients in the early hours of the morning when foot traffic is low or EV cars are already charged, usually comes down to changing a forwarding address and watching everything continue as normal. It’s uneventful by design.
What makes it uneventful is the work that precedes it. Firmware standardization, hardware testing, testing to exhaustion before any switch date arrives. If you’ve tested enough, you know exactly what will happen.
The more useful question to ask a prospective vendor is not whether they have an OCPP proxy or a migration tool. It’s how they plan to run the preparation. The tooling matters less than the process built around it.
How do you communicate the transition to customers?
The approach varies significantly by customer type.
For B2C customers, drivers charging at public stations, the key insight is realistic: most will not read emails, notifications, or banners in advance. No matter how much you communicate, a large share of drivers will encounter the change at the charge point, without prior context. That’s the moment to optimize for. Can a driver, possibly in a hurry, in bad weather, figure out what’s different and what to do next in a few seconds? The communication at the point of use matters more than everything sent before it.
For B2B customers, the logic flips completely. These are businesses whose operations depend on your service. They need advance notice, structured onboarding, training, and supported access to your team before go-live. By the time the switch happens, they should already know where to click and what changed. The goal is that they arrive at the migration date feeling prepared, not surprised. Mariana’s framing: B2C is about optimizing for the moment of use; B2B is about the journey to adoption.
What internal resources do we need?
This is the answer Mariana said to take home from the webinar above everything else: you need a very diligent project manager you can find.
What that means in practice: someone technical enough to have real conversations with engineers, commercially grounded enough to work across finance, accounting, sales, and marketing, and persistent enough to keep the project moving when energy flags. This person needs to be in place from day one, not brought in mid-project to catch up on three months of decisions.
Whether they’re internal or external matters less than whether they exist and own the migration end to end. For simpler projects, an internal lead with the right profile is often enough. For more complex ones, some operators bring in specialists who’ve managed similar migrations before and can shorten the scoping phase significantly.
Cut over at once or migrate in phases?
Both approaches work, and both have real trade-offs.
A cutover migration is like ripping off a bandage: decisive, short, and over before the uncertainty can accumulate. The switch happens once; teams don’t have to run parallel processes. The preparation has to be thorough, because the moment of transition is concentrated. But with rollback capabilities and proper testing, the risk is manageable.
A phased/iterative option migrates your network gradually over several weeks or months, moving charging stations and users in small groups while maintaining full operations. Both old and new systems work together during the transition, ensuring zero downtime but requiring more coordination between technical teams.
Whichever approach you choose, our proprietary OCPP Migration Proxy works across the entire transition to minimize risk and disruption. As preparation begins, charging points are gradually reconfigured to connect to the proxy rather than directly to the legacy system. The proxy then routes all communication transparently to the existing platform, so operations continue uninterrupted while the switch is prepared.
What this looks like in practice
AMPECO has migrated over 120,000 charge points across in-house platforms and all the major commercial CPMS providers. In-house migrations are more complex, because each one carries its own accumulated custom logic; they require deep collaboration with the operator to surface and translate every detail of how the business actually works.
The migration framework AMPECO uses puts the most time and energy at the front: the solution design and preparation phase. This is where the two systems need to be genuinely mapped against each other. What AMPECO calls a user is probably different from what the legacy platform calls a user. How tariffs are structured and applied won’t match. Integrations need to be scoped carefully, not assumed to carry over. The build and test phases that follow go faster when that foundation work is done well.
AMPECO employs proven migration templates and checklists refined through extensive real-world applications across hundreds of successful migrations. These standardized frameworks eliminate guesswork and ensure comprehensive coverage of all migration aspects, from initial scoping through post-migration validation.
The migration toolkit includes:
- Detailed business analysis questionnaires that map every aspect of your current operations, from revenue models and user authentication methods to payment processing and roaming connections.
- Migration scoping templates that translate business requirements into technical execution plans.
- Technical validation checklists for data imports, charger communication, integrations, mobile apps, and switch-day readiness
- Specialized tools for complex scenarios, including phased migrations, proxy-based hardware transitions, and rollback procedures
Why large-scale and ambitious Charge Point Operators are migrating to AMPECO
Scaling a charging network exposes a hard truth fast: legacy platforms tend to fall behind operator needs the moment ambitions grow. The triggers vary — tightening regulation, outages that chip away at customer confidence, inflexible systems that stall expansion, or the messy task of consolidating after an acquisition — but large-scale CPOs keep landing on the same realization. A constrained software platform eventually becomes a ceiling on how far and how fast an EV charging business can grow.
That’s why AMPECO treats migration as a discipline in its own right, not an afterthought: purpose-built teams, battle-tested playbooks, and a track record that stands apart in the market. As of May 2026, we’ve moved more than 120,000 charge points off legacy, rigid CPMS platforms, and a wide range of in-house builds. That figure represents dozens of enterprise-scale projects — each one backed by a dedicated engineering team, tailored data mapping, and close collaboration with CPO teams who trusted us with one of the most critical transitions their business would ever make.
What really makes the case, though, is what comes after the switch. Across pan-European network consolidations, multi-acquisition integrations, and cross-border CPO transitions, AMPECO has proven a simple point: a migration can happen at scale without the disruption that usually comes with it.
If you want to talk through your specific situation, book a migration consultation with the AMPECO solutions team. Alternatively, if you want to dive deeper into the topic of migrations, download The EV Charging Platform Migration Playbook.
