Netcracker Migration Assessment — Sized Plan in 2–4 Weeks

A netcracker migration assessment is the structured pre-project readiness exercise that produces a sized, risk-registered, regulator-aware plan for moving a Netcracker BSS/OSS estate either downstream (revenue and AR to Fusion), to a long-term compliance archive (post-cloud-upgrade or post-vendor-swap), or both. The Syntra ETL netcracker migration assessment runs in 2–4 weeks against the production Netcracker estate (read-only — no operational impact) and produces a complete inventory of BSS/OSS scope, CDR volumetrics, customisation footprint, TM Forum SID conformance gap, mediation layer dependency, regulator retention overlay and revenue-assurance reconciliation profile, plus a fixed-scope statement of work and budget.

Seven inventory dimensions. (1) BSS/OSS scope — which Netcracker products are in play (CRM, Charging & Billing, Order Management, Active Inventory, Service Activation, Service Orchestration, Revenue Management), per-instance footprint. (2) CDR volumetrics — rated CDR rows per day per network element, retention window, mediation-layer flow (RAVE, Comverse, Mediation Zone). (3) Customisation footprint — bespoke product-catalogue extensions, Order Management workflow customisations, Charging & Billing rating scripts, integration handlers. (4) TM Forum SID and Open API conformance gap. (5) Multi-instance estate map (M&A consolidation usually 3–7 instances). (6) Vendor product mix — what else integrates (mediation, fraud, CRM analytics, partner-settlement, regulator-reporting tools). (7) Complexity scoring per dimension.

A typical netcracker migration assessment runs 2–4 weeks. Single-instance, single-jurisdiction, tight scope: 2 weeks. Multi-instance estate (3–5 acquired-carrier Netcracker estates), multi-jurisdiction, full BSS+OSS scope with deep CDR volumetrics analysis: 4 weeks. The assessment is run by Syntra ETL's netcracker-experienced team against read-only access to the production estate (REST Open APIs, NCT exports, Oracle DB Data Guard standby) — no operational impact, no admin-team load beyond initial access provisioning. Output is a sized statement of work, risk register, regulator overlay map, and a fixed-scope budget that the carrier can take to procurement immediately.

Five deliverables. (1) BSS/OSS scope inventory — every Netcracker product surface in scope, with API/NCT/DB extraction strategy per surface. (2) Volumetrics report — rated CDR rows, BSS finance rows, customer and account counts, network-inventory counts per Netcracker instance, with growth projection. (3) Customisation inventory — bespoke catalogue extensions, workflow customisations, rating scripts, integration handlers, classified by reporting materiality and Fusion-equivalent recommendation. (4) Regulator overlay map — FCC, CALEA, EU ePrivacy (per member state), GDPR, MNO licensing, state PUC, SOX, ACMA, CRTC and other applicable regimes per jurisdiction with retention windows and CALEA warrant-SLA requirements. (5) Sized SOW with timeline, milestones, risk register and budget.

CDR volumetrics dominate the archive sizing exercise. The netcracker migration assessment profiles rated CDR rows per day per network element, growth rate, retention regime per jurisdiction (FCC 18+ months, EU ePrivacy member-state-specific, CALEA warrant-readiness window), and compression ratio target (typically 8–12x in columnar Parquet versus row-oriented Oracle DB). Output is a sized archive plan: storage tier (active queryable vs cold), partition design (network element + day + service type), compression codec, retention regime tagging strategy and CALEA warrant SLA design. Total petabyte estimate produced with confidence bounds.

Yes — multi-instance estates from M&A growth are the norm for tier-1 telcos. The netcracker migration assessment maps each Netcracker instance separately (product catalogue, account numbering, mediation feed, historical depth, customisation footprint, regulator overlay), then identifies consolidation patterns: customer master de-duplication potential, product-hierarchy unification challenges, partner-settlement model reconciliation, CALEA scoping across acquired and acquirer jurisdictions. Output is a per-instance archive and migration sequence plus a group-level consolidation map. Multi-instance assessments take the upper end of the 2–4 week window.

Eight factors scored low/medium/high. (1) Instance count — single vs multi-instance vs M&A wave. (2) CDR volumetrics — millions, hundreds of millions or billions per day. (3) Customisation depth — vanilla deployment vs heavily customised (catalogue extensions, workflow customisations, rating script overrides). (4) TM Forum SID conformance gap — well-aligned vs significant divergence. (5) Mediation-layer complexity — single mediation system vs multi-vendor mediation feeding the same Netcracker estate. (6) Multi-jurisdiction regulator overlay — single vs multi-jurisdiction with conflicting retention regimes. (7) Integration footprint — how many downstream systems consume Netcracker data. (8) Concurrent BSS programme — is the Netcracker estate also undergoing Cloud upgrade or competitor swap. Scoring drives timeline, budget and risk register.

Fixed-scope fixed-price wherever possible. The Syntra ETL netcracker migration assessment produces a sized statement of work with milestone-based pricing, not time-and-materials. Volumetrics (CDR rows, BSS finance rows, customer counts), instance count, customisation footprint, regulator-jurisdiction overlay and concurrent-programme complexity all feed the pricing model. Carriers see the budget before signing the SOW. Where genuine uncertainty exists (typically around customisation footprint at first assessment), a small T&M envelope is scoped explicitly with clear exit criteria. The aim is no surprises in execution — fixed-scope pricing builds the carrier's confidence and protects Syntra ETL's delivery margin.