Migration & Onboarding
Move charging operations in controlled stages
Start with representative hardware and real operational journeys, validate each stage, then expand with clear evidence and a planned fallback.
Controlled transition
Prove the operating model before expanding the estate
Charging migrations involve hardware, protocol behaviour, identity, integrations and support workflows. AmpNexus uses staged validation to make those dependencies visible before more chargers are moved.
Estate discovery
Document charger models, OCPP versions, connectivity, firmware, customer journeys and integrations that affect the move.
Representative validation
Connect a representative hardware cohort and verify protocol behaviour before assuming the rest of the estate behaves the same way.
Operational acceptance
Validate status, sessions, meter data, remote commands, alerts and support workflows against agreed acceptance checks.
Planned fallback
Define the decision points and recovery path for each migration stage before changing a wider cohort.
Team handover
Bring operations, support, engineering and delivery teams into the acceptance process with the access they need.
Evidence and audit
Keep connection, action and rollout history available for troubleshooting and transition review.
What we work through
The exact plan depends on the estate and the systems around it. These are the areas we establish before agreeing the transition sequence.
- Hardware models, OCPP versions and vendor-specific behaviour
- Current firmware, security profiles and connectivity paths
- Tenant, organisation, site and user structure
- Session, meter, reporting and operational data requirements
- Remote commands, alerting and support workflows
- API, webhook and event-stream integrations
- Representative pilot and cohort acceptance criteria
- Training, handover, fallback and completion responsibilities
For estates that cannot stop operating
Existing charge point operators
Move away from a constrained backend while making charger behaviour and business continuity part of the plan.
Hardware manufacturers
Validate models, firmware and customer journeys before moving an installed base to a new operating layer.
Growing charging services
Establish repeatable onboarding and acceptance controls before the next stage of estate growth.
Migration path
Discovery, proof, cohorts, handover
A transition moves forward when the previous stage has produced enough evidence to support the next decision.
- 01
Discover
Map hardware, data, integrations, customer journeys and operational dependencies.
- 02
Prove
Connect representative chargers and validate agreed end-to-end journeys.
- 03
Move cohorts
Expand in controlled groups while monitoring behaviour and acceptance results.
- 04
Hand over
Confirm controls, access, support context and completion evidence with operating teams.
Transition principles
No big-bang assumptions
Mixed charging estates contain real differences between models, firmware versions and connectivity. The migration approach is designed to expose those differences early.
Representative before comprehensive
Test the combinations that matter before applying a plan to the whole estate.
Evidence before expansion
Use operational acceptance results to decide when a cohort is ready to grow.
Fallback before change
Agree how to pause or recover a stage before it begins, not after an issue appears.
Start with your real estate
Bring your hardware mix, current operating model and integration requirements to a migration discovery session.