Answers
Can we migrate an existing portfolio without taking any operators offline?
Yes. Portfolio migrations are sequenced tenant by tenant — each MVNO staged and validated in parallel before cutover.
The existing platform stays live throughout. Each cutover runs overnight in a low-usage window. Operators and their subscribers experience zero downtime.
Sequenced portfolio migration
Portfolio migrations do not require a single big-bang cutover. Each MVNO in the portfolio is staged, validated, and cut over independently — allowing the migration to proceed without risk to the entire portfolio at once.
The existing platform stays live throughout. Operators continue serving subscribers normally until their individual cutover is complete.
How the migration sequence works
- Each MVNO is staged and validated independently
- Parallel running validates billing accuracy before cutover
- Cutovers run overnight in low-usage windows
- Existing platform stays live throughout
- Zero downtime for operators and subscribers
Risk management
Sequenced migration means issues discovered during one tenant's migration do not affect the rest of the portfolio. Each cutover is an isolated event with its own validation and rollback capability.
Related Pages
FAQs
Can an MVNA migrate without downtime?
Yes. Portfolio migrations are sequenced tenant by tenant. Each MVNO is staged and validated independently before overnight cutover. Zero downtime for operators and subscribers.
How long does a portfolio migration take?
The total timeline depends on portfolio size. Each tenant migrates independently — typically in sequence over several weeks, with no operator taken offline at any point.
