How long does a BSS migration take?
A BSS migration takes anywhere from two weeks to two years depending on scope. Greenfield MVNO launches on a modern cloud-native BSS complete in 2–8 weeks. Replatforming an existing ISP with active subscribers takes 3–6 months. A tier-1 operator ripping out a legacy monolith typically runs 12–24 months. The single biggest driver is data migration complexity, not software configuration.
Greenfield MVNO or ISP launch — 2 to 8 weeks
With no legacy data to migrate, the timeline is dominated by three items: contracting the host carrier or wholesale supplier, wiring in payments and identity verification, and configuring the product catalogue. On METAVSHN, first-party connectors for Swisscom BBCS, PortaONE, Bexio, Veriff, and Stripe collapse most of that to configuration. The Ticinocom × NordVPN launch closed in under two weeks end-to-end.
ISP or MVNO replatform — 3 to 6 months
Replatforming an operator with a live subscriber base adds four workstreams: data migration and reconciliation, cutover planning (parallel run vs big-bang), billing continuity across the cutover boundary, and staff retraining. Most of the calendar time is spent on data — cleaning up decades of ad-hoc customer records, mapping legacy product SKUs to a modern catalogue, and reconciling in-flight orders and invoices.
Tier-1 legacy replacement — 12 to 24 months
When the incumbent stack is a decade-old Amdocs, Oracle, Ericsson, or Netcracker deployment with millions of subscribers, migration is a program not a project. Phased cutover by customer segment, brand, or line of business is the norm. Timelines under 12 months are rare and usually signal an underscoped program. This is not the segment METAVSHN targets.
Frequently asked
- What is the fastest realistic BSS launch time?
- For a greenfield MVNO with a modern cloud-native BSS and first-party carrier connectors, under two weeks is achievable. Ticinocom launched NordVPN on METAVSHN in under two weeks from kickoff to first customer activation.
- What slows down BSS migrations?
- Data migration and reconciliation, not software configuration. Legacy customer records, ad-hoc product SKUs, and in-flight invoices at cutover consume most of the calendar time on replatform projects.
- Can we run legacy and new BSS in parallel?
- Yes, and this is usually the safest cutover pattern for operators with an active subscriber base. Route new sales to the new stack, migrate cohorts backwards, and retire the legacy once residual accounts drop below a threshold.