Overview
Approaches & Patterns
The dimensions every transformation has to settle, the core migration patterns, what greenfield and brownfield really mean in practice, and the myths that most often derail a programme.
Transformation Dimensions
Three independent dimensions define the shape of your programme. Click each to reveal the hidden preconditions.
What Looks Attractive
"Replace the entire BSS stack in one programme." Promises a clean break, single vendor, unified architecture.
What Breaks
Everything changes simultaneously — no fallback. Testing is exponential. One domain delay (e.g., billing) blocks the entire programme.
Preconditions
Multi-year executive sponsorship. Documented current-state architecture. Frozen legacy change. Budget for 18–36 months of parallel running.
What Looks Attractive
"Go best-of-breed and integrate via TMF Open APIs." Promises flexibility and no vendor lock-in.
What Breaks
You own every integration seam. TMF APIs help but are not plug-and-play. Expect 30–50% of budget on integration alone.
Preconditions
Mature integration platform (API gateway, event bus). Internal architecture team enforcing interface contracts. Clear SoR boundaries across domains.
What Looks Attractive
"Migrate all data before go-live." Clean start, single source of truth, no dual-running.
What Breaks
Legacy data is messy and incomplete. Product definitions do not map cleanly. Migration becomes the critical path — often longer than building the new system.
Preconditions
Canonical data model agreed upfront. Data quality tooling (profiling, cleansing, dedup). Multiple dry-run windows. Rollback strategy that avoids reverse-migration.
Core Transformation Patterns
Four dominant patterns for migrating from a legacy BSS/OSS stack to a modern one. None is universally “best” — the right choice depends on your product portfolio,organisational readiness, and appetite for risk.
When It Works
Diverse portfolio with natural boundaries (e.g., consumer broadband vs enterprise voice). Products can be isolated without shared fulfilment dependencies.
Hidden Complexity
Cross-product bundles break the model. Billing must handle both stacks. The "simple first product" still takes 12–18 months.
When It Works
BUs operate independently with separate channels, billing, and ops teams. Manageable product portfolio (< 50 offerings).
Hidden Complexity
BU boundaries are rarely as clean as org charts suggest. Shared infra, billing, and CRM create hidden coupling.
When It Works
New market segment, new brand, or new access tech (e.g., 5G FWA) with genuinely no existing customers.
Hidden Complexity
Breaks when new customers want legacy products or vice versa. Cross-stack orders emerge within months. Legacy never gets decommissioned.
When It Works
Well-defined API boundaries exist or can be introduced. Works well for SOM, catalog, or inventory with clear TMF API boundaries.
Hidden Complexity
The routing/facade layer becomes a critical dependency. State consistency across old and new is hard. The last 20% of legacy traffic is always the hardest.
Greenfield vs Brownfield Realities
The terms “greenfield” and “brownfield” are used loosely in transformation programmes. In practice, almost no telco transformation is truly greenfield. What matters is the degree of brownfield constraint.
A clean-sheet build of the target stack alongside legacy. New customers onboard immediately; legacy must still be migrated and retired. “Greenfield” refers to the build, not the end state.
A transformation within an existing operating environment — live customers, legacy data, incumbent systems, and established processes that must continue running throughout.
Common Transformation Myths
Transformation programmes are often justified with assumptions that sound reasonable but do not survive contact with reality.
"Transformation will reduce headcount"
The assumption is that automation and new platforms automatically mean fewer people. In practice, transformation often changes roles and creates new capabilities, while headcount benefits depend on organisational redesign and actual process simplification.
"Transformation will create synergies"
A common platform or consolidated architecture does not automatically create synergies. They only materialise when products, processes, systems and operating models are genuinely harmonised.
"Transformation will eliminate inefficiency"
Replacing old technology does not automatically fix inefficient processes, organisational silos or poor ways of working. You can modernise the technology and preserve the inefficiency.