SAP's analytics migration narrative is straightforward: BW 7.5 on HANA enters mainstream maintenance end in 2027, BW/4HANA is the modern successor, and the path forward is clear. What SAP does not emphasise: BW/4HANA is not an upgrade. It is a re-implementation of your entire analytics estate — new data models, new transformation logic, new reporting layer, full regression testing across every business area that touches BW. For organisations with complex BW estates, migration costs run £3M–£15M with implementation timelines of 2–4 years.
Third-party support for BW 7.5 on HANA gives analytics teams a different option: maintain the existing investment at 60–65% lower cost, continue receiving the support quality SAP delivers under Premier Support, and defer or bypass the BW/4HANA migration entirely on business terms rather than vendor timeline.
This article explains the commercial reality of SAP's BW/4HANA push, what TPS covers across the BW stack, and a cost model for four common analytics deployment profiles.
Running SAP? See how much you can save before your next renewal. Free analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Running BW 7.5 on HANA under SAP Premier or Extended Support? See what TPS costs.
Free BW AssessmentThe BW/4HANA Migration Trap
SAP positioned BW/4HANA as a "simplified" analytics platform. That framing is accurate in one narrow sense: BW/4HANA removes legacy DataStore Objects (DSOs), InfoCubes, MultiProviders, and the transformation routines built on top of them — replacing them with HANA-native composite providers, advanced DSOs, and a simplified data flow model. The simplification is real. So is the cost of getting there.
BW 7.5 on HANA estates typically contain:
- Thousands of InfoObjects, InfoCubes, and DSOs built over 10–20 years of incremental analytics investment
- Complex transformation routines — start routines, end routines, field-level transformations written in ABAP — that encode business calculation logic developed by analytics teams across multiple ERP releases
- SAP Business Content customised far beyond the original configuration, making a "reactivate" approach to BW/4HANA infeasible
- Reporting layers in SAP BEx, SAP Analysis for Office, or third-party BI tools (Tableau, Power BI, MicroStrategy) connected to BW InfoProviders via OLAP connections that do not survive a data model migration without rework
The BW/4HANA migration path for estates with this complexity is not a technology upgrade. It is an analytics redesign programme. SAP's official migration tools (MIGRATE objects, shell conversion) handle structural transformations but do not migrate business logic or resolve semantic changes in data models. System integrators routinely scope 3–5 years for large BW migrations, with the first 12–18 months dedicated entirely to assessment and detailed design.
Third-party support does not resolve the migration question — it removes the vendor timeline from the equation and lets organisations make the decision on their own terms.
What TPS Covers on SAP BW and BW on HANA
| Component | TPS Coverage |
|---|---|
| BW Application Server (ABAP stack) | Full — basis stack, kernel, ABAP runtime, work process management |
| BW metadata objects (InfoObjects, InfoProviders, transformations) | Full — error resolution, performance issues, metadata inconsistencies |
| HANA database layer (HANA 1.0 SPS06, HANA 2.0 all SPS) | Full — HANA DB engine, HSR, backup/recovery, SDI connections |
| ABAP transformation routines (start, end, field) | Full — custom code debugging, logic preservation across HotPackage levels |
| Process Chains and scheduling infrastructure | Full — PC debugging, DTP error analysis, data load incident response |
| BEx Query Designer and BEx Analyzer | Full — query design issues, restricted key figures, calculated key figures, navigational attributes |
| Analysis for Office (AfO) connectivity | Full — SAP OLAP BAPI connectivity, Excel integration issues |
| SAP BusinessObjects (BI 4.x) integration | Full — Universe connectivity, Web Intelligence over BW, IDT |
| Third-party BI tool connectivity (Tableau, Power BI, etc.) | Full — BICS, ODBO, MDX interface issues; certified connector versions |
| Security patches (ABAP stack and HANA) | Yes — custom patch engineering for critical CVEs |
| Tax and regulatory content updates | Yes — country-specific compliance reporting |
| BW/4HANA migration consulting | Not included in TPS — separate commercial engagement |
BW Version Matrix and TPS Availability
| BW Version | SAP Status | TPS Available | Notes |
|---|---|---|---|
| BW 7.5 on HANA (all SPS) | Mainstream Maintenance ends 2027; Extended to 2030 with fee | Yes | Primary TPS target; largest installed base |
| BW 7.4 on HANA | Mainstream ended 2020 | Yes | Many still running 7.4 with heavy ABAP investment |
| BW 7.3 on any DB | Mainstream ended 2018 | Yes | Older estates with long-running analytics programmes |
| BW/4HANA 1.0 / 2.0 | Active SAP maintenance | Available but less common | TPS available; fewer customers on BW/4HANA currently |
| SAP BW on Oracle DB / SQL Server | Mainstream ended | Yes | Non-HANA BW estates — TPS covers both BW layer and non-HANA DB |
SAP BW TPS Cost Model — Four Profiles
SAP's BW support fees are calculated as a percentage of the BW application licence value, typically 22% per year. The following profiles reflect common BW on HANA deployment sizes in manufacturing, pharmaceutical, and financial services environments.
Mid-Market Manufacturing BW on HANA — 512GB
TPS equivalent: £136,800/yr
Annual saving: £223,200
Scope: BW 7.5, HANA 2.0, ECC source, BEx reporting
Pharma Analytics — 1TB HANA, Multi-Source
TPS equivalent: £192,400/yr
Annual saving: £327,600
Scope: BW 7.5, HANA 2.0 SPS06+, SAP BusinessObjects BI 4.3
Financial Services BW — 2TB HANA, Regulatory Reporting
TPS equivalent: £302,400/yr
Annual saving: £537,600
Scope: BW 7.5 on HANA 2.0, FSDP regulatory cubes, AfO, third-party BI
Large Enterprise Group BW — 4TB HANA Cluster
TPS equivalent: £518,000/yr
Annual saving: £962,000
Scope: BW 7.5, HANA Scale-Out, 8 source systems, SAP Lumira, Tableau
What does your BW support spend look like compared to TPS? Get a model in 15 minutes.
Run My BW NumbersThe BW/4HANA Migration Economics
SAP's BW/4HANA migration tools and methodologies have matured since the product launched in 2016. The shell conversion approach — converting BW objects to BW/4HANA equivalents while retaining data — works well for organisations with relatively clean, Business Content-aligned BW estates. For organisations with significant custom development, it does not.
A realistic BW/4HANA migration programme for a complex estate looks like this:
| Cost Category | Typical Range | Notes |
|---|---|---|
| System integrator fees (design, build, test) | £2M–£10M | Highly dependent on InfoProvider count and transformation complexity |
| ABAP transformation logic re-engineering | £400K–£2.5M | Start routines and field logic do not migrate — must be re-written in BW/4HANA transformation model |
| Reporting layer rework (BEx → Fiori/AfO) | £300K–£1.5M | BEx queries cannot be directly used in BW/4HANA; AfO connections must be rebuilt |
| Data migration and historical load | £200K–£800K | Historical data migration requires a defined retention strategy and delta initialisation |
| Testing (functional, regression, UAT) | £300K–£1.2M | Full regression across all BW-connected business processes; multiple test cycles |
| Business change and training | £150K–£600K | Analytics users require retraining on new query and reporting tools |
| Total (mid-market) | £3.4M–£16.6M | TPS for 5 years: £1.0M–£2.6M for equivalent estate |
TPS for five years on a typical BW estate costs a fraction of a BW/4HANA migration. For organisations without a compelling functional reason to migrate — and most do not have one — TPS is the economically rational choice.
Sector Angles
Manufacturing and Supply Chain
Manufacturing BW estates are typically SAP-only source systems: ECC (or S/4HANA in hybrid architectures), SRM, APO/IBP, and occasionally SAP PM. The inter-system data flows and delta queue management across these source systems represent years of tuning. TPS maintains the existing data flow architecture and delta queue health with the same level of active support as SAP Premier Support. See our manufacturing industry page for related context.
Pharmaceutical and Life Sciences
Pharma BW environments carry GxP validation obligations. Any change to the BW analytics platform — including a BW/4HANA migration — triggers revalidation of all analytical reports used in regulatory submissions, batch release decisions, and pharmacovigilance. The validation overhead alone can add £500K–£2M to a BW/4HANA migration programme. TPS avoids change events that trigger revalidation. For pharma-specific context, see our Pharma & Life Sciences industry page.
Financial Services
FS BW estates frequently carry regulatory reporting cubes — EBA stress testing, ICAAP capital calculations, FINREP, COREP. These cubes are deeply customised and reviewed annually by internal model validation teams. Migrating them to BW/4HANA is not a technical exercise; it is a model re-approval exercise. TPS maintains existing regulatory reporting infrastructure without triggering a model review cycle. See our financial services industry page.