Skill requirements for brownfield versus RISE teams.

The decision between a brownfield S/4HANA estate and a RISE with SAP estate is presented to the board as a commercial and architectural choice. Inside the IT organisation, it is also a workforce choice. The two operating models call for distinct skill profiles, distinct hiring markets, and distinct career paths. A buyer that commits to one path without a clear view of the team it will need to run that path for the next seven years often discovers, two years in, that the skills it has are not the skills the estate requires. The hiring market for SAP technical talent is tight enough that the gap takes eighteen months to close, and the operating cost during the gap shows up as either delayed releases or contractor premium that the original business case did not include. This article walks the brownfield skill profile, the RISE skill profile, the genuine overlaps and differences between them, and the reskilling pathway that buyers usually need to plan in parallel with the architectural decision itself.

The brownfield skill profile

A brownfield S/4HANA estate that the buyer operates in its own data centre, or on a hyperscaler under a buyer managed contract, requires the full classical SAP technical team. The Basis administrator remains a central role, responsible for HANA database administration, system landscape directory management, transport routes, kernel upgrades, support package application, and the daily health of the production, quality, and development environments. The Basis function in a brownfield estate is rarely a single person. A mid sized enterprise typically runs three to five Basis administrators, with on call rotation for the production environments and named owners for the quality and development tiers.

The brownfield estate also requires SAP infrastructure engineers. These engineers own the operating system, the storage, the backup and recovery procedures, the disaster recovery site, and the high availability configuration. In a hyperscaler hosted brownfield estate, the infrastructure engineer operates the SAP certified instance shapes, the dedicated storage tiers, and the cloud network constructs that the SAP workload requires. In a buyer data centre brownfield estate, the infrastructure engineer operates the physical hosts, the storage arrays, and the network fabric. Either way, the infrastructure engineering function carries deep platform knowledge that does not appear in a generic cloud engineering role.

The brownfield estate requires SAP security and authorisation specialists. These specialists own the role design, the segregation of duties matrix, the authorisation object configuration, the user provisioning workflow, and the audit support function. The role design is rarely static. New business processes, new acquisitions, new regulatory requirements, and new integration points all produce role design work that the security specialist owns.

The brownfield estate requires ABAP development capability. Even in a clean core S/4HANA brownfield deployment, the ABAP function is present for custom enhancements, for integration mappings, for reporting extensions, and for the maintenance of the legacy custom code that the brownfield path preserves. The ABAP team usually carries between five and twenty developers depending on the scale of the customisation footprint, with at least one senior developer who owns the technical architecture of the custom layer.

The brownfield estate finally requires functional configuration specialists across the modules in scope. Finance, controlling, materials management, sales and distribution, production planning, warehouse management, and any industry specific modules each carry their own functional team. The functional specialists own the configuration in the IMG, the master data structures, the business process mapping, and the user acceptance testing cycles.

The RISE skill profile

The RISE with SAP estate transfers a significant portion of the brownfield technical team responsibilities to SAP under the hyperscaler. The Basis function does not disappear, but its scope narrows substantially. SAP under RISE owns the HANA database administration, the kernel upgrades, the support package application, the operating system patching, and the underlying infrastructure operations. The buyer side Basis function reduces to interface configuration, custom code transport management within the RISE policy, batch job scheduling, integration with the SAP managed service operations team, and the buyer side incident routing for issues that originate inside the SAP managed perimeter.

The RISE estate eliminates the SAP dedicated infrastructure engineering role. The hyperscaler infrastructure that runs the RISE workload is operated by SAP under its hyperscaler reserved capacity contract. The buyer no longer needs SAP certified instance sizing engineers, storage engineers, or backup engineers for the SAP workload itself. The hyperscaler engineering capability the buyer needs shifts toward the integration boundary, where the RISE estate connects to the buyer cloud, the buyer identity provider, the buyer network, and the buyer data lake.

The RISE estate retains a strong security and authorisation requirement on the buyer side. SAP under RISE does not own the buyer role design, the segregation of duties matrix, or the user lifecycle. These remain buyer responsibilities. The security specialist on the RISE side often takes on additional work around the boundary controls between the RISE perimeter and the buyer environment, including the identity federation, the network segmentation, and the data exfiltration monitoring.

The RISE estate changes the shape of the ABAP function. The clean core policy that RISE enforces pushes custom development away from the core S/4HANA Cloud Private Edition workload and onto the SAP Business Technology Platform. The team that historically wrote ABAP enhancements increasingly writes Cloud Application Programming Model services in Java or Node, Cloud Application Studio extensions, BTP Workflow flows, and integration suite scenarios. The ABAP skill is not obsolete, since the in stack extensions and the side by side extensions both retain ABAP under the cover, but the centre of gravity shifts toward the BTP polyglot stack.

The RISE estate elevates the integration and platform engineering function. The buyer that runs RISE alongside a broader cloud estate, a multi system landscape, and a portfolio of non SAP applications needs strong integration suite, event mesh, API management, and BTP service consumption capability. The integration engineer becomes a primary technical role rather than a supporting one.

The overlap and the genuine differences

The overlap between the two skill profiles is wider than the marketing on either side suggests. Functional configuration, security and authorisation, master data governance, business process design, and end user training are common across both paths. The functional consultant who configured the finance module under brownfield ECC configures the same finance module under S/4HANA Cloud Private Edition in RISE. The skill required to design a chart of accounts, a controlling area, or a profit centre hierarchy does not change with the operating model.

The genuine differences sit in the technical infrastructure layer and in the development model. The Basis function shrinks under RISE but does not disappear. The infrastructure engineering function reorients from SAP specific to integration boundary specific. The ABAP function rebalances toward BTP polyglot extension development. The platform and integration function grows. The cloud engineering function on the buyer side grows for the integration boundary even though the SAP workload itself is no longer the buyer's operational responsibility.

The mistake that buyers make in scoping the workforce transition is to assume that RISE eliminates the technical team. The team does not vanish. It reshapes. The headcount reduction from a brownfield to a RISE operating model typically lands in the range of twenty to thirty five percent, with the variability driven by the customisation footprint, the integration complexity, and the maturity of the cloud platform engineering function that the buyer already has in place. A buyer that builds the RISE business case on a headcount reduction of fifty percent or more usually finds the actual reduction smaller and the BTP and integration capability shortfall larger than projected.

Hiring and retention implications

The hiring market reflects the architectural shift. The classical SAP technical roles, Basis administrator, ABAP developer, infrastructure engineer for SAP, retain steady demand inside organisations that operate brownfield estates and inside the partner network that supports those estates. The salary levels for these roles remain stable and the career path remains visible. The retention risk on these roles inside a buyer that has committed to RISE is real. The Basis administrator who joined a brownfield shop for the depth of the work does not necessarily want to operate the narrowed Basis function inside a RISE estate. The retention conversation needs to happen before the conversion announcement, not after.

The hiring market for BTP polyglot extension developers, integration suite engineers, and SAP cloud platform engineers is tighter than the market for classical SAP roles. The skill is newer, the talent pool is smaller, and the competition between buyers, partners, and SAP itself is intense. The buyer that needs to build BTP capability in parallel with a RISE conversion usually plans an eighteen to twenty four month hiring window, with a blend of external hires, partner augmentation, and internal reskilling.

The reskilling path for an experienced Basis administrator into a BTP integration engineer is realistic but demanding. The Basis administrator brings the depth of SAP knowledge that a generalist cloud engineer lacks. The reskilling investment is the addition of cloud platform engineering, polyglot development, and integration suite tooling. The investment is typically twelve to eighteen months of structured learning plus active project exposure, with the most successful reskilling programmes pairing the reskilling engineer with an experienced BTP architect on real delivery work.

Reskilling and the multi year transition

The reskilling pathway that the buyer designs in parallel with a RISE conversion shapes whether the operating model meets the business case. A buyer that announces the RISE decision and then immediately reduces the technical team usually loses the deep SAP knowledge that the new operating model still needs, even though it needs less of it. A buyer that announces the RISE decision and then maintains the full technical team unchanged for three years carries operating cost that the business case does not support.

The disciplined reskilling plan runs over a thirty six month horizon. In the first twelve months, the existing technical team operates the brownfield estate while the buyer stands up the BTP and integration capability through hires and structured reskilling. In months thirteen through twenty four, the conversion to RISE is executed, with the existing team supporting the cutover and the new capability operating the BTP and integration layer. In months twenty five through thirty six, the team reshapes to the steady state RISE operating model, with named individuals from the original team moved into BTP, integration, security boundary, or business analyst roles, and with the remaining capacity reduction managed through attrition, partner offload, and selective separations.

Conclusion: the workforce decision is the architecture decision

The skill profile required to run a brownfield S/4HANA estate is not the skill profile required to run a RISE with SAP estate. The shift is not in functional configuration, which remains constant, but in technical infrastructure, development model, and integration capability. The buyer that treats the workforce transition as a downstream consequence of the architectural decision usually misses the eighteen to twenty four month reskilling and hiring window and ends up running both operating models in parallel for longer than the business case anticipated. The buyer that treats the workforce transition as part of the architectural decision, planned and budgeted from day one, captures the operating cost reduction that the RISE path is supposed to deliver. The decision between brownfield and RISE is a decision about the team as much as it is a decision about the contract.