AMPECO

When Swisscharge migrated 20,000 charge points to AMPECO, the cutover took a few hours. The months before it involved three organizations coordinating business mapping, partner testing, and dry runs in parallel. The network saw no drop in operational metrics and a 20% year-over-year rise in charging sessions and active drivers. The technical switch is rarely where a migration is won or lost. Read what actually decides the outcome, written for the people accountable for it.

Most operators who have seriously evaluated a platform switch have run the same calculation: headcount and infrastructure against a licensing fee. That comparison has a blind spot. The largest costs of running an in-house CPMS don't appear in any budget line. They accumulate in the work that didn't get built, the roadmap deferred for the third cycle, and the cross-network perspective your team structurally cannot access. This post works through what those costs look like — and why the gap compounds.

A platform migration isn't just about changing systems. Done well, it's a chance to revisit the business, purge what isn't working, and optimize what is. Done badly, it's the most expensive project an operator will ever scope. Mariana Mota and Charlie O'Donoghue walk through what migration projects actually involve, the signals that your CPMS has hit its ceiling, the preparatory work required before signing a contract, and the internal readiness that ultimately determines whether the project runs smoothly.

There's a pattern in how CPO migration conversations start. Technical questions come first because they feel safe. How long? Will chargers go offline? What data transfers? But the questions that actually determine outcomes tend to stay unasked: Are we doing this for the right reasons? Do we have the right people? What does success look like? Mariana Mota and Charlie O'Donoghue answered both layers. AMPECO: 120,000+ charge points migrated.

You have probably postponed a CPMS migration at least once, and the reason usually sounds like risk: downtime, lost customization, a project that drags for a year, drivers who revolt. Each of those describes a migration run badly, not migration as it works today. Handled well, downtime is measured in minutes, your business logic carries over, and the people using your network never feel the change. We wrote the playbook for leaders weighing exactly this decision. Download it.

Look at your sprint board from last quarter. OCPP compliance. Payment terminal recertification. OCPI credential refresh. ISO 15118-20. Every item is necessary. None of it is unique to your network — every operator with a deployed fleet ran the same sprint this year. Networks that have accounted for this honestly report 43% of engineering headcount on platform essentials. This framework sorts the workload into two columns and shows what shifts when one column is handled elsewhere.