A 220-item netcracker migration checklist for BSS/OSS-to-Oracle Fusion downstream migration. Scope confirmation, CDR volume audit, multi-instance map, regulator notification, partner contract review, in-flight order handling, cutover orchestration — every owner, every due date, every sign-off authority.
Netcracker BSS/OSS migrations don't fail because the REST Open APIs don't work. They fail because a regulator notification was missed, a partner-settlement evidence chain broke, or an in-flight order rule was never written down — and the team discovered it during cutover weekend.
Netcracker Technology runs the BSS/OSS spine at AT&T, Verizon, T-Mobile, Vodafone, Deutsche Telekom, Telefonica, BT, Orange, NTT, KDDI and dozens of regional carriers. The migration surface is broad — CRM, Charging & Billing, Order Management, Active Inventory, Service Orchestration, Revenue Management — and the regulatory footprint is broader still: FCC CDR retention, FCC CALEA, EU ePrivacy, GDPR, BNetzA, Ofcom, ARCEP, ACMA, state PUCs, SOX, plus jurisdiction-specific lawful intercept and emergency-service routing.
A consultant-led netcracker migration typically discovers half its checklist items the hard way — in a status meeting six weeks before cutover, when somebody finally maps the partner-settlement contract addendum to the proposed cutover plan. By then the timeline has slipped and the budget has overrun.
Syntra ETL ships a pre-built netcracker migration checklist refined across multiple tier-1 and tier-2 conversions. 220 items, 14 sections, named owners, due dates relative to cutover, sign-off authorities, and per-jurisdiction overlays for the regulator-touching items. Delivered at the end of the assessment, governed through to hypercare close-out, and the single biggest reason Syntra ETL netcracker migrations cut over on the planned weekend.
Every item below has burned a telco migration when left implicit. The Syntra ETL netcracker migration checklist forces an explicit, owned decision before build starts.
What is the binding regulatory CDR retention floor across every jurisdiction this carrier operates in? FCC 18+ months is the minimum; EU ePrivacy variants and revenue assurance can push to 7+ years. The archive sizing depends on this number.
Are all Netcracker instances loading to one Fusion BU or multiple? Is enterprise-customer dedup across instances in scope? What happens to the same subscriber in two acquired tenants? Decision signed off before crosswalks begin.
Which regulators must be notified of any change to CDR custodial arrangement, archive jurisdiction, lawful-intercept handover or emergency-service routing? Notice periods (30–90 days) tracked per jurisdiction.
Which wholesale, roaming, MVNO and content partner contracts reference BSS-derived settlement evidence? Which dispute windows are open at cutover? Which require an explicit settlement-statement parallel-run?
How are orders in 'submitted', 'in-provisioning' and 'partially-billed' states handled across the cutover boundary? What does partial-month revenue recognition look like under the new GL custodian?
What load-to-Fusion vs. archive-only window is approved by finance, revenue assurance and internal audit? Current FY + prior FY is typical; deeper history routes to long-term archive.
14 sections, 220 items, mapped to project phase. Below is the high-level walk-through; the full workbook is delivered at the close of the netcracker migration assessment.
Scope confirmation, stakeholder map, named-owner roster, regulator-jurisdiction inventory and CDR-volumetrics request issued to BSS operations. Signed off by finance lead and BSS engineering lead before assessment begins.
Multi-instance map, TM Forum customisation inventory, mediation-layer profile, partner contract inventory and historical-window proposal completed. Signed off by finance, revenue assurance, BSS engineering, OSS engineering and compliance leads.
Crosswalks signed off (product/offering hierarchy, account-number unification, customer dedup rules, COA segment design, partner-master rules). Cutover orchestration plan v0.1 drafted with bill-cycle boundary.
Extractor configuration complete, FBDI emitters validated against Fusion 26x, archive pipeline validated at telecom scale, regulator notification packs drafted, partner-settlement parallel-run plan signed off.
FCC, CALEA, national-regulator and partner notifications dispatched with the binding notice period. Acknowledgements tracked per notification. Lawful-intercept handover testing scheduled.
Cutover rehearsal in production-shape lower environment, sign-off pack issued, cutover window opened on the agreed bill-cycle boundary. Hypercare team on-call rota active for 4 weeks post-cutover.
Items without named owners don't get done. The checklist forces a named owner per item drawn from a fixed roster.
Approves COA segment design, historical-window decision, ledger and BU mapping, parallel-run sign-off criteria, partner-settlement journal routing.
Approves CDR-to-bill-to-GL reconciliation chain, mediation_record_id preservation rule, partner-settlement parallel-run scope, post-cutover variance threshold.
Approves extractor scope, REST Open API governance, NCT export schedule, Oracle DB read replica access, in-flight order treatment.
Approves Active Inventory archive scope, service-activation archive scope, trouble-ticket archive scope, operational-forensics retrieval SLA.
Approves regulator notification packs per jurisdiction, archive-jurisdiction decision, GDPR/ePrivacy DPA updates, CALEA handover, lawful-intercept testing sign-off.
Approves partner contract notifications, settlement evidence retention SLA, dispute-window honour plan, partner-settlement parallel-run sign-off.
A netcracker migration checklist is the structured pre-flight workbook that captures every artefact, decision, sign-off, regulator notification and operational handover required before a Netcracker BSS/OSS-to-Oracle Fusion downstream migration can go to cutover. Tier-1 telcos need one because the risk surface is unique: Netcracker is the spine for CRM, Charging & Billing, Order Management and Active Inventory, while Fusion is downstream finance — meaning a missed checklist item doesn't just delay an FBDI load, it can stall a multi-billion-CDR daily revenue feed, breach FCC CDR retention, miss a CALEA data-call deadline, or invalidate partner-settlement evidence. Syntra ETL ships a 220-item netcracker migration checklist refined across multiple tier-1 and tier-2 carrier conversions, structured by phase (assessment, design, build, test, cutover, hypercare) and by owner (finance, revenue assurance, BSS engineering, OSS engineering, regulator-liaison, security, infra).
Scope confirmation is the foundation of any netcracker migration checklist. BSS side: which Netcracker products are in scope (Customer Experience Management, Charging & Billing, Order Management, Revenue Management), which subscriber bases (postpaid, prepaid, IoT/M2M, wholesale, MVNO host), which bill-cycle calendars, which rate plan estate, which partner-settlement streams. OSS side: which Active Inventory domains (mobile, fixed, FTTx, transport), whether Service Activation and Service Orchestration history is in scope, whether trouble-ticket history is moving. Finance side: which BUs and ledgers in Fusion become the target, which COA segments need telecom dimensions (product family, service type, region, customer segment), and which historical periods load to Fusion vs. archive only. Sign-off on this scope before any extractor work is the single biggest delay-reducer in tier-1 netcracker migration projects.
Call Detail Record volumetrics drive the archive sizing, the cutover window length and the regulator-retention guarantee, so a CDR volume audit is a mandatory section of any serious netcracker migration checklist. The audit captures: average daily CDR count per service type (voice, SMS, data, roaming, partner settlement) across the trailing 13 months, peak-day multipliers, retention windows applied (FCC 18+ months, EU ePrivacy variant, internal revenue assurance window), rated vs. unrated split, the mediation layer in front (Netcracker RAVE, Comverse, Mediation Zone), and current storage footprint in Oracle DB. The audit feeds the columnar Parquet archive sizing (typical 8–12x compression), the partition strategy (network element × day × service type), and the throttled extract schedule that avoids contention with online rating throughput.
Telecom regulators care about migrations that touch CDRs, subscriber data, lawful intercept, partner settlement and emergency-service routing — exactly the surface Netcracker covers. Your netcracker migration checklist must include: FCC notification of CDR custodial change with the new retrieval contract (CALEA-compliant), BNetzA / Ofcom / ARCEP / equivalent equivalent national-regulator notifications where the carrier is licensed, EU ePrivacy and GDPR Data Processing Addendum updates for any new cloud archive jurisdiction, state PUC / public utility commission notification for US carriers, FCC 800/900-number routing custodian update, lawful-intercept handover testing with law-enforcement liaison, and emergency-service (E911 / 112) routing custodian verification. Each item has a minimum notice period (often 30–90 days) and must be tracked in the checklist with notification date, regulator contact, response received and sign-off.
Wholesale and partner contracts at tier-1 telcos run into the hundreds — interconnect partners, MVNO host agreements, roaming partners (GSMA TADIG/TAP3 settlement), content partners (premium SMS, ringback), enterprise customer master service agreements. Every one of those contracts has SLAs around bill timing, dispute windows, settlement evidence retention and revenue assurance lookups. The netcracker migration checklist captures: which contracts reference BSS-derived evidence, which require notification of any change to settlement custodian or evidence retention, which dispute windows are still open at cutover (and how they will be honoured), and which partners need an explicit settlement-statement parallel-run to confirm bill parity. Skipping this item is the single most common cause of post-cutover commercial disputes.
Yes — and it's often overlooked. At any moment a tier-1 Netcracker estate has tens of thousands of in-flight orders (new activations, plan changes, port-ins, port-outs, suspensions, terminations) and open trouble tickets in various states. The checklist must capture the cutover-day treatment: orders in 'submitted' state continue in Netcracker (which stays operational); orders that have produced billing events but haven't fully provisioned need a specific reconciliation rule; trouble tickets remain in Netcracker Service Orchestration. Because Fusion is downstream finance, not a Netcracker replacement, the in-flight handling is mostly a finance-side question: which orders will land in which fiscal period, and how will partial-month revenue be recognised. The checklist makes the treatment explicit and signed off by revenue assurance and finance.
The default Syntra ETL netcracker migration checklist runs 220 items organised across 14 sections (Scope, CDR Volumetrics, Multi-instance Map, TM Forum Customisation Inventory, Mediation Layer Continuity, Crosswalks & Mappings, Master Data Cleansing, Open AR Treatment, Historical Window Decision, Partner Settlement Continuity, Regulator Notifications, In-flight Order & Ticket Handling, Cutover Orchestration, Hypercare). Each item carries an owner (named role), a due date relative to cutover, a sign-off authority and a current-state field. The checklist is delivered as a structured workbook at the end of the netcracker migration assessment and lives in the project's governance tool of record through to hypercare close-out.
Tier-1 telcos almost always operate across multiple regulatory jurisdictions — a single group company might be regulated by FCC, BNetzA, Ofcom, ARCEP, ACMA, TRAI and several state PUCs simultaneously, each with its own CDR retention rules, subscriber-data-residency expectations, lawful-intercept conventions and outage-reporting timetables. The Syntra ETL netcracker migration checklist carries per-jurisdiction overlays: each regulator-touching item (CDR custodian change, archive jurisdiction, lawful-intercept handover, emergency-service routing custodian) is tracked per jurisdiction with the local regulator contact, local notice period and local sign-off authority. This eliminates the common consultant-led pattern of discovering a missed jurisdictional notification three weeks before cutover.
Book a 30-minute scoping call. We'll walk through your Netcracker instance estate, CDR volumetrics, jurisdictional regulator footprint and partner-contract profile — and issue the tailored netcracker migration checklist as part of your assessment kickoff.