For systems integrators running S/4HANA conversions

S4 RetrofitBox turns the open dual-maintenance allowance in your conversion bid into a licence line plus review effort, with a unit, a size and a one-day install target.

Dual maintenance is the cost you cannot scope

On a fixed-price conversion, the BAU stream is a risk you carry. The box turns it into a known line.

ECC stays in production for two to three years of the programme. Every transport the BAU team releases there has to be re-applied to code the conversion has already rewritten. Conversion tools fix the new system once. The BAU stream that follows is left to the programme, and it is usually absorbed into the fixed price or the application management contract as an allowance.

The work is unplanned, so it lands on whoever is free rather than whoever knows the object. It arrives during the build, so it competes with the critical path. And a fix re-keyed under time pressure is a common source of regressions in S/4.

With the box, each released transport is carried onto the converted code, adapted for S/4 and queued for a person to approve. Your team reviews, it does not re-code. What you bid is one licence line per landscape, sized on the transports the legacy system released in the last twelve months, plus the review effort.

It runs for exactly the window where dual maintenance exists

The box starts the day the converted copy exists and stops the day ECC is switched off. The licence term follows the same window.

Where S4 RetrofitBox sits in a conversion programme Conversion project starts Assessment and scoping Converted copy exists Box installed, target under a day Cutover The business moves to S/4HANA ECC decommissioned Box stops, licence ends S4 RetrofitBox runs One licence line per landscape, for the programme Dual maintenance: two to three years of BAU transports released on ECC ECC in production

Conversion tools do the one-time conversion and leave the BAU retrofit problem behind. The box takes over from there, so the vendors of those tools are partners, not rivals.

The two sit side by side in the bill of materials: one for the conversion, one for the stream of fixes that follows it.

After ECC is switched off

The conversion licence ends with the legacy system. Parallel code lines do not: release upgrades, clean core refactoring and rollouts to further target lines each put two lines in motion again, and the same box carries those changes. That is a reason for the customer to keep the box after the programme closes.

These scenarios are built and shown in the live demo, but are not in the pilot release yet Roadmap Licence terms beyond the conversion are not set. What the box does after cutover.

What each person needs, and what we provide

Four people decide whether the line goes into the bid. Each gets an answer. Anything not yet built is marked as roadmap.

Who needs what
WhoWhat they needWhat we provide
SI solution architect A line item with a unit, what it includes and excludes, where it sits in the programme, sizing and prerequisites, and a one-day install. The unit and four sizes on the pricing page. The timeline above. A self-hosted box on one Linux VM, installed by the customer's Basis team from a runbook, with a target of under one working day. An installer and support bundle are on the roadmap Roadmap
SI bid manager The argument that dual maintenance is the unscoped cost on a fixed-price conversion, and that it can become a licence line plus review effort. The argument on this page. A fixed fee for the size, never per transport. An estimator you fill with your own bid data. A pilot at a fixed fee, credited against year one on adoption.
Customer architect No SAP writes, code kept in their network, their own model key, an offline licence, an exportable audit record, their own roles. All of these are in the pilot release, described on the security page. With a hosted model provider, the code in each model call leaves the network. The independent security review and penetration test have not been carried out yet Roadmap
Partner programme Terms for delivering and reselling the line, and a way to start. A white-label embedded accelerator, or resale with co-selling, with margin on the licence line agreed per partner, and joint delivery on the first engagements. Formal programme tiers, certification and partner training are not defined yet.

What the partner gets

Six things we can describe today.

  • A BOM line with a unit and a size

    One line per landscape per year, sized S to XL on the transports the legacy development system released in the last twelve months. Fixed for the size, never per transport.

  • A prerequisites checklist

    One Linux VM with Docker Compose, a DNS name both SAP development systems can reach over HTTPS, an ABAP add-on on the ECC and converted development systems, a one-time baseline load, and the customer's model key if they want AI.

  • An install runbook with a one-day target

    The customer's Basis team installs from the runbook. One of the five pilot acceptance criteria is install to first Retrofit in under one working day.

  • Pilot terms you can bid

    Four weeks, the first 20 released BAU transports, a final report, and a fixed fee credited against the first year's licence on adoption.

  • Partner margin on the licence line

    You set the client price against a wholesale price, or resell with co-selling. The margin is agreed per partner and per programme, so we do not print it here.

  • Joint pilot delivery

    You run the conversion and the S/4 side of onboarding. We deliver the pilot and the first engagements with you.

How a partnership starts

It starts with a pilot on one live landscape, not a framework agreement.

  1. Check the case against a current bid

    Put your own numbers into the estimator: transports a year, hours per transport, your rate. Replace our defaults with your bid data.

  2. Choose the partnership model

    White-label under your own accelerator name, resale with co-selling, or either with named roadmap items you co-fund. Margin is agreed with the model.

  3. Select a pilot landscape and sponsor

    One BAU system and one project system, with a sponsor who owns margin on the conversion bid or the application management practice.

  4. Run the four-week pilot

    The first 20 released BAU transports, measured against the acceptance plan. If it works, the pilot fee is credited against year one, and a letter of intent covering resale can follow.

See it work on your own changes

A four-week pilot on your first 20 released BAU transports, with five acceptance criteria and a written report. The pilot fee is credited against the first year's licence on adoption, and you keep your code and every record.