Migration de Données

Le Problème

Pourquoi cette extension existe-t-elle ?

Switching CSMS platforms is painful. Years of charging history, thousands of driver profiles, hundreds of charger configurations — all at risk of being lost. The Migration extension provides a structured, validated migration process that preserves all your historical data.

La Solution

Ce que vous obtenez

Charger configuration migration: OCPP settings, connector types, location data, and firmware versions
Driver profile migration: accounts, payment methods, wallet balances, and subscription plans
Historical session data: CDRs, energy data, and billing history for all past sessions
Validation and reconciliation: compare migrated data against source system to ensure completeness
Rollback capability: if migration fails, revert to source system without data loss
Zero-downtime migration: migrate in parallel while source system remains live
Supported sources: OCPP 1.6 and 2.0.1 CSMSs, CSV exports, and custom API integrations

🎯 Who is this for?

Any CPO or eMSP switching to OASIS HUB from another CSMS. Essential for operators with significant historical data they cannot afford to lose.

Activer Cette Extension Parcourir le Marketplace

🔌 Modular by design

Activez ou désactivez par tenant. Payez uniquement ce que vous utilisez. Toutes les extensions s'intègrent parfaitement.

Capacités Clés

Tout inclus

Complete Data Migration

Charger configurations, driver profiles, historical sessions, billing history — everything migrated and validated.

Validation and Reconciliation

Every migrated record is validated against the source system. Discrepancies flagged and resolved before go-live.

Rollback Capability

If anything goes wrong, revert to the source system instantly. No data loss, no driver impact.

Zero-Downtime Migration

Migrate in parallel while your source system remains live. Drivers never experience downtime during the migration.

Historical Data Preserved

Years of charging history preserved and accessible in OASIS HUB. Drivers can see their full charging history from day one.

Any Source System

Migrate from any OCPP 1.6 or 2.0.1 CSMS. CSV exports and custom API integrations also supported.

Cas d'Usage Réels

Voyez-le en action

Comment les opérateurs du monde entier utilisent cette extension pour résoudre des vrais problèmes et développer leur activité.

CPO migrates 5 years of charging history

A CPO switching from a legacy CSMS has 5 years of charging history — 180,000 CDRs, 12,000 driver profiles, and 200 charger configurations. The Migration extension imports all data, validates it against the source system, and confirms 99.97% accuracy before go-live.

Zero-downtime migration over 2 weeks

A large CPO migrates 500 chargers over 2 weeks. During the migration, both systems run in parallel. Chargers are migrated in batches of 50 per day. Drivers never notice the migration — the app works throughout.

Migration validation catches discrepancy

During validation, the Migration extension flags 47 CDRs where the energy values differ by more than 0.1 kWh between source and migrated data. The team investigates and finds a rounding error in the source system export. The issue is corrected before go-live.

Étude de Cas

CPO migrates 12,000 drivers and 180,000 CDRs with zero data loss

A Portuguese CPO with 5 years of charging history migrated from a legacy CSMS to OASIS HUB. The Migration extension imported 12,000 driver profiles, 180,000 CDRs, and 200 charger configurations. Validation confirmed 99.97% accuracy (6 CDRs with minor rounding differences, all corrected). The migration completed in 3 weeks with zero downtime. Drivers logged into OASIS HUB on day 1 and saw their full 5-year charging history.

12,000

Driver profiles migrated

180,000

CDRs migrated

99.97%

Migration accuracy

Downtime for drivers