Analytics Legends The knowledge platform for SAP Analytics
Guide

SAP BW4HANA migration partner — the questions that separate benches from logos

As of 2026-08-14

Choosing a BW/4HANA migration partner is mostly an exercise in detecting one conflict of interest and one absence. The conflict is recommending a bigger programme than the estate needs. The absence is a delivery bench that has actually finished one of these. Everything else on a partner scorecard is easier to verify and matters less.

The conflict of interest to screen for explicitly

Rebuild engagements are larger and more lucrative than selective ones, which creates a standing incentive to recommend a rebuild when the underlying model is salvageable. Experienced buyers have started screening for this behaviour deliberately, and firms seen doing it lose exactly the long-term relationship the migration was supposed to create.

The mirror-image failure is quieter and just as expensive: recommending a lift-and-shift because it is easy to sell and fast to staff, without naming the debt that travels across. A lift-and-shift buys time without buying capability, and a customer told otherwise discovers the difference on the first invoice from the new platform.

Both failures leave the same fingerprint on the proposal — a recommendation with no path visibly rejected. Ask which path was ruled out and on what evidence. A partner who cannot answer has not diagnosed the estate.

Four questions that reveal the bench

What share of the last estate you migrated landed in the auto-eligible complexity band, and what did the remainder cost? A partner who has finished one of these knows the distribution; a partner who has sold one quotes an object count.

Who owned report retirement on your last programme, and what happened when they said no? Retirement is political rather than technical, and it is the long pole of any selective migration. The answer reveals whether the firm has ever managed the part that stalls.

How did you prove reporting parity? Auditor-grade reconciliation, budgeted per object, is not a phase that absorbs leftover time.

What debt did you carry across on your last lift-and-shift, and was it written down? A partner that keeps a debt register is a partner that has been asked about it before.

Where the delivery capacity actually is

Read the live market rather than the credentials deck. On our own opportunity radar, BW appears in roughly a quarter of live SAP analytics engagements at the time of writing, and Germany alone accounts for close to half of the BW-mentioning briefs — ahead of India, Poland, the United States, Spain, Austria, France and the United Kingdom.

That concentration is a useful cross-check on any partner claim. A firm whose BW references cluster in one country is not disqualified, but a Tier-1 migration is delivered by the bench and not by the logo, and benches are local before they are global.

It is also a warning about scarcity. The migration cycle SAP triggered is the largest in this ecosystem since BW moved onto HANA, with consulting demand measured in billions through 2028, and the maintenance extension of SAP BW 7.5 to 31 December 2030 did not create additional consultants. A partner selected late is selected from what remains.

What the first engagement should be

Buy the decision before you buy the programme. A bounded discovery engagement — €50-150k in our engagement data — exists to close the path decision so an execution phase of €500k and upwards can be scoped honestly.

Make the deliverables explicit at contract time: a complexity distribution rather than an object count, a cohort assignment with its consequence, a shortlist of paths with one ruled out, and the customer's own maintenance terms quoted from their own documents.

And keep discovery separable from execution. A discovery whose only possible conclusion is the seller's largest offer is a proposal with a report attached.

What we cannot assert

We do not rank migration partners and we publish no partner scores for this work. Our firm directory records what is verifiable about each firm; whether a given bench has finished an estate of your shape is answered by references you check yourself. The radar shares describe the live opportunity feed on the date this page was generated.

Frequently asked

How do we compare BW/4HANA migration partners?

On the questions that only a finished programme can answer: complexity distribution of the last estate, who owned retirement, how parity was proven, and what debt was carried on the last lift-and-shift. Certifications and release numbers are easy to verify and predict little.

Should we choose a large firm or a specialist?

Choose the bench, not the entity. What matters is whether the people who will be on your programme have finished one, in your country, on an estate of your shape — and both categories can pass or fail that test.

What is the biggest risk in partner selection?

Being sold a bigger programme than the estate needs. Rebuilds are defensible only when the existing model is genuinely the problem; screening for the incentive is now standard practice among experienced buyers.

Is there still time to select carefully?

The deadline pressure eased when the SAP BW 7.5 extended-maintenance window moved to 31 December 2030, but delivery capacity did not increase. Selection late in the cycle is selection from what is left.

What this page is built on

Read next