Migration handled end to end
Seshnova manages the full transition from a legacy prepaid platform: the cutover process, the data migration and normalisation, and the analytics and reporting operators need once they are live.
Three parts of one engagement
Platform, data, and reporting are not separate workstreams. They are handled together so the new platform is operational, clean, and visible from day one.
Managed migration
We run the cutover, not just supply the platform. Discovery, dry runs, reconciliation, cutover execution, and post-cutover intensive care are all part of the engagement.
Data migration
Rate tables, PIN databases, account records, balances, and CDR history all move across with cleaning and normalisation built into the transform, so the new platform starts in a better state than the one it replaced.
Analytics and reporting
Once live, Seshnova provides traffic, revenue, fraud, and carrier reporting so operators can see their business clearly — by corridor, brand, reseller, or carrier — without rebuilding reporting from scratch.
A rehearsed cutover, not a first attempt
Migration is treated as an operational control process. Each stage is completed and verified before the next begins. The final cutover executes steps that have already been proven — not steps being tried for the first time under pressure.
Discovery
Map the current platform: rate tables, PIN and account structures, IVR flows, carrier integrations, CDR delivery, and operational dependencies. Identify where the data is clean and where it has drifted.
Data extraction and profiling
Extract source data and profile it in detail: format variations, identifier inconsistencies, balance anomalies, stale rate entries, overlapping prefixes, and business logic embedded in code or scripts rather than configuration.
Dry runs and reconciliation
Run repeatable transforms against source data, load into the target platform, and reconcile counts, balances, and rating output. Run again. The goal is a transform that produces the same result every time, so the final cutover is a rehearsed step, not a first attempt.
Data normalisation
Resolve inconsistencies on the way in: standardise number formats, PIN structures, lifecycle states, rate prefixes, and zone definitions. Document accepted exceptions. Arrive at a canonical product model rather than a copy of the old one.
Cutover
Execute against a tested runbook: reroute access numbers, activate rate tables, confirm carrier integrations, run balance reconciliation, and verify live calls are rating correctly. Rollback criteria are agreed in advance.
Intensive care
Close monitoring through the first weeks of live traffic: call volume, fraud indicators, balance behaviour, CDR delivery, and support ticket patterns. Anomalies are caught and resolved before they become incidents.
Clean data in, from day one
Data is not copied across unchanged. Every major data type goes through extraction, profiling, normalisation, and verified reconciliation before it is loaded. The goal is a product that is easier to operate than the one it replaced, not a faithful reproduction of its inconsistencies.
Rate tables and A-Z destinations
- Full A-Z rate deck extraction and prefix deduplication
- Zone and destination normalisation
- Time-of-day, promotional, and customer group rules
- Longest-prefix matching validation before go-live
PIN and account data
- Bulk PIN migration with format standardisation
- Account lifecycle state mapping and exception handling
- Balance carry-over with verified reconciliation
- Reseller, dealer, and multi-brand structure preservation
CDR history and audit records
- Historical CDR migration for billing and dispute resolution
- Retention period compliance and format mapping
- Account event history: top-ups, adjustments, reversals
- Queryable format for finance and support on day one
Integrations and configuration
- SIP trunk and carrier routing configuration
- IVR call flow recreation and access number mapping
- CDR delivery and downstream reporting connections
- API integration with existing back-office and provisioning
Operational visibility from day one
A migration that moves data without addressing reporting leaves operators flying blind on the new platform. Seshnova includes reporting across the dimensions that matter: traffic, revenue, fraud, carrier performance, and the audit trail finance and support teams depend on.
Traffic and revenue reporting
Call volumes, successful completions, revenue by destination, carrier, reseller, brand, and time window. See where the business is and where the margin is.
Fraud and anomaly monitoring
Velocity spikes, PIN sharing indicators, concurrent call anomalies, and unusual balance draw-down patterns. Surface fraud signals before they become incidents.
Carrier performance
Answer seizure ratio, average call duration, cost versus revenue by route and carrier. Identify underperforming routes and renegotiate from a position of data.
Multi-brand and reseller visibility
Consolidated reporting across brands, resellers, and callshop channels with margin separation. One platform, one reporting layer, however many product lines.
Finance and support tooling
CDR queries, balance dispute resolution, top-up and adjustment history, and account lifecycle events — the audit trail finance and support teams need every day.
Post-migration health tracking
Compare traffic, revenue, and fraud indicators before and after cutover. Confirm the new platform is performing as expected and surface any gaps early.
Ready to plan a migration?
Every migration starts with understanding what is there. Seshnova can help you scope the rate tables, account data, CDR history, IVR logic, and integration work involved before committing to a cutover date.