Guide

Freelance SAP BW/4HANA architect in 2026: assessments, migration paths and market reality

As of 2026-10-05

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

A freelance SAP BW/4HANA architect in 2026 is mostly asked to decide what happens to a BW estate, rather than to extend it. The work is assessment, path selection and the first migration steps towards Business Data Cloud. The market is large in postings and thin in freelance ones: on 4 October 2026 the Analytics Legends contract corpus held 255 live postings naming BW/4HANA, 232 permanent, 14 freelance and 9 contract.

Why the work changed

Classic BW 7.5, including BW 7.5 on SAP HANA, reaches the end of mainstream maintenance on 31 December 2027, with optional paid extended maintenance to 2030. BW/4HANA is maintained until at least 2040, aligned with S/4HANA (SAP maintenance announcement, 23 April 2020). SAP product management put the classic BW 7.5 base at 20,000 to 30,000 customers worldwide at Sapphire 2025, as reported by SAPinsider.

Two consequences follow. Customers on classic BW face a dated decision. Customers already on BW/4HANA face a different one: whether to move again so soon, given that their platform is supported far longer. A generic message that BW is ending speaks to the wrong customer in three cases out of four, and the first job of an architect is to establish which cohort the client is in. Always check the date against the client's own product release and contract, because the schedule for your exact version is the only authoritative answer.

The four paths an assessment chooses between

Migration to Business Data Cloud is not one motion. An assessment recommends one of four.

Lift-and-shift rehosts the existing model. It fits when infrastructure or licensing is the driver, and it buys time without buying capability, so every modelling debt comes along. Selective migration moves what earns its keep and retires the rest; it is usually the honest answer and the one that needs political cover, because retiring means a report disappears. Rebuild redoes the semantic layer in Datasphere; it has the highest cost and ceiling and is defensible only when the current model is the problem. Stay and federate keeps BW in place and exposes it through BDC Connect, which suits an estate that works and needs reach, not replacement.

The architect's value is arguing the choice on trade-offs for this estate, rather than defaulting to the path they know best.

The tools that change the arithmetic

Two SAP mechanisms matter in an assessment. The BW Data Product Generator turns existing BW objects, advanced DataStore Objects and CompositeProviders in particular, into data products that Business Data Cloud can consume, while BW stays the system of record. It makes the first two paths cheaper because the move can be incremental.

BW bridge runs BW/4HANA-style objects inside the Datasphere tenant. The objects it covers are advanced DataStore Objects, CompositeProviders, transformations and process chains, not InfoCubes and not BEx queries. It suits a large estate where a rip-and-replace would break daily reporting, and it loses against a direct move when the estate is small or the customer has no BW at all.

An honest assessment states which objects fall outside each tool. That list, not the tool itself, is where the effort hides.

What a freelance architect delivers

On an assessment the deliverables are an inventory of queries, InfoProviders and process chains with usage evidence, a cohort and path recommendation, a wave plan and a list of reports proposed for retirement with a named business owner for each. On a migration, the work shifts to a quarterly rhythm: a small batch of objects moved or retired, reconciled to the legacy output, with differences explained.

The reconciliation is the part to test. A model that reproduces a BW query to the cent, or explains each gap, is evidence. A migration described as finished because the system was switched off is not.

Decision table: engagement shapes

Assessment of one BW estate — Fit: independent architect · Output: Inventory, path choice, wave plan · Watch for: Recommending the path the consultant knows.

Large estate, several BW systems — Fit: firm or team with an independent lead · Output: Waves and staffing · Watch for: One person asked to carry every stream.

Hybrid BW and BW/4HANA, S/4HANA programme in the background — Fit: independent as a dependency owner · Output: BW decisions aligned to the programme timeline · Watch for: BW treated as a standalone project.

Federate-and-stay decision — Fit: short independent engagement · Output: BDC Connect design and access rules · Watch for: Federation chosen to avoid a decision.

Rebuild in Datasphere — Fit: firm, with an independent as reviewer · Output: Semantic layer redesign · Watch for: Rebuild justified by taste.

Market reality

Of the 255 BW/4HANA postings, 99 are in Germany, 39 in the United States, 23 in India, 10 in Poland and 8 each in Belgium and Romania. By seniority, 153 are senior and 57 mid-level. Co-skills are telling: 232 also name BW, 182 SAP Analytics Cloud, 153 Datasphere, 86 Business Data Cloud and 49 Databricks. Nineteen titles contain architect, one of them freelance. Source: Analytics Legends live contract corpus, public/api/contracts-lean.json, 1,610 live postings, generated 4 October 2026.

Only a minority is explicitly freelance, so independents should expect direct and intermediary channels. For rates, the published figures are for BW in general. In France, SAP BW/4HANA is quoted at EUR 570 to 740 per day, median 660, and the combined BW/4HANA and SAC profile at 590 to 770, median 680 (LinkQuest, 26 March 2026, sample of 420 profiles). Our rate calculator gives a modelled EUR 850 per day for BW/4HANA migration at France and 6 to 10 years of seniority, gross to the consultant (8 May 2026, editorial band model). No source publishes a line for the title architect.

What we cannot assert

No source publishes a day rate for the title architect on BW/4HANA, so the rates above are module-level or modelled. The extended maintenance terms for a given client depend on that client's agreement. The corpus cannot show how many BW postings are assessments versus run support.

Frequently asked

Is BW/4HANA still worth specialising in?

Its maintenance runs to at least 2040 per SAP's 2020 announcement, and 255 live postings named it on 4 October 2026. The growth is in migration and Business Data Cloud work around it, so pair it with Datasphere.

When does classic BW 7.5 maintenance end?

Mainstream maintenance ends on 31 December 2027, with optional paid extended maintenance to 2030 (SAP maintenance announcement, 23 April 2020). Confirm against the client's own product release and contract.

What are the four BW migration paths?

Lift-and-shift, selective migration, rebuild in Datasphere, and stay and federate through BDC Connect. The BW Data Product Generator and BW bridge change the cost of the first two.

Do freelance BW/4HANA architects get hired?

Advertised roles are mostly permanent: 14 of 255 postings on 4 October 2026 are freelance. Independent work more often arrives through direct or intermediary contacts.

What this page is built on

SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths
BW Data Product Generator
BW Bridge: The Migration Arbitration
Brownfield vs Greenfield Migration
Live contract corpus, 4 October 2026