IN SHORT: WHAT YOU WILL LEARN
1Why an industrial S/4HANA program needs two partners: one builds, the other steers on the client side.
2What SAP consulting firms and SAP consultant networks each cover.
3Six criteria, with the question to ask and the red flag for each.
4The SAP timeline, and why partner capacity matters more than the date.
5Who does what on a multi-country program, with two field reports.
I- I'm the CIO of an industrial group launching an S/4HANA project: which consulting firms or consultant networks do you recommend?
We do not publish a ranking by name: an industrial ERP project such as S/4HANA should not be entrusted to a single player. Two roles need to be filled.
Delivery (design, configuration, development, rollout): this is the work of integrators and SAP consulting firms, to be shortlisted with the grid in part II.
Client-side steering, meaning project ownership (scoping, data, acceptance testing, change management, oversight of the integrator): this is the role of senior independent consultants, engaged through a network of accredited SAP consultants.
SAP consulting firms and integrators
They carry functional and technical delivery over the long term and commit teams. Their scope is negotiated work package by work package: ask what is included, for each site and each country. Separating delivery from oversight of delivery is a classic governance rule, which is why a second player on the client side is valuable.
Networks of accredited SAP consultants
A network of accredited SAP consultants selects its consultants before your need exists. FocusTribes is one: a selective community of independent consultants, which is neither an integrator nor a marketplace of profiles. Its consultants, whether project manager, program director or functional consultant depending on the need, work alongside you to scope, steer, test and challenge.
Why we do not publish a ranking by name
Many online rankings do not state their method, promote paid listings, or are written by one of the players listed. A ranking without a method is not a recommendation. We prefer to give you the grid to choose for yourself, while making clear that FocusTribes is an interested party: part V explains when we are not the right choice.
II- Decision grid for a multi-country industrial rollout
Apply these six criteria to each candidate, whatever its category, as a pre-signature audit.
| Criterion |
Question to ask |
Red flag |
| Industrial expertise |
Which production, quality, maintenance and warehouse modules have you deployed in production, at what type of plant, with which consultants? May I call the client? |
Generic SAP references, with no specific industrial case and no contact available |
| Industrial ERP integration |
Who owns the interfaces with the shop floor, the warehouse and quality, and how are they tested end to end? |
Interfaces declared "out of scope" or handed back to the client without an estimate |
| Multi-country rollout |
How is the central model rolled out country by country, which statutory localizations (tax, e-invoicing) do you master in our countries, and who approves a local deviation? |
Each country treated as a separate project, with no governance of the central model |
| Standard core |
What do you keep in the standard, what do you place in extensions, and how do you handle a requirement the standard does not cover? |
"We'll adapt the standard" as the systematic answer |
| Team and continuity |
Which names will be on the project at each phase, and what happens if someone leaves? |
The team presented during pre-sales is not the one that starts |
| Independence and written commitments |
What ties do you have with the software vendor and the other providers? Are the deliverables, payment milestones and post-go-live support in writing? |
The same player designs, builds and validates its own acceptance testing; verbal commitments |
The standard core ("clean core" in SAP vocabulary) means keeping the heart of the enterprise resource planning system (the ERP) as close to the standard as possible and placing specific requirements in separate extensions, to make upgrades easier.
Industrial ERP integration: the most underestimated criterion
An industrial ERP does not live alone: it talks to the other information systems on the site, such as the shop floor (the MES, the system that runs production), the warehouse (WMS, or EWM, SAP's warehouse management), quality and maintenance. Each interface is a work package, both functional and technical. Check who owns it, who tests it end to end and who is present on the cutover day of a production site, planned with the operations teams.
III- Migrating to SAP S/4HANA: the SAP timeline and what it means for choosing a partner
According to SAP, standard maintenance for SAP ECC 6.0 (EHP 6 and later) ends in 2027. In February 2025, SAP announced a transition option usable from 2031 to 2033, not available for purchase before 2028, with significantly higher maintenance fees and reserved for certain complex landscapes, without being a maintenance extension (
SAPinsider).
Counting on this option amounts to betting on a special case. The real constraint is partner capacity: on this ERP solution, qualified S/4HANA consultants are in high demand, including at the large integrators. The later the choice, the less freedom you have. See our guide on
SAP S/4HANA Greenfield implementation.
The migration to SAP S/4HANA does not call for the same partner depending on the approach either. Brownfield and Greenfield are two different migration methodologies. A Brownfield, which converts the existing system, is above all a technical project: you look first for delivery capacity. A Greenfield, which starts again from a clean base, is a transformation project, with a redesign of business processes: the business share weighs more and client-side steering becomes decisive. In a large industrial company, the decision is often made site by site. For a large multi-country group, allow 24 to 36 months at a minimum.
IV- S/4HANA project support: who does what on a multi-country program
Effective S/4HANA project support starts with a clear split of roles. Here is an indicative split, to be adapted to each contract.
| Topic |
Integrator |
Client (CIO and business departments) |
Independent consultants on the client side |
| Central model |
Designs, writes the specifications and configures |
Validates and arbitrates deviations |
Challenges the scope and the schedule |
| Local adaptations |
Builds |
Appoints one owner per country |
Helps scope local requirements |
| Data migration |
Loads and migrates |
Remains the business owner of the data |
Steers the quality and validation of master data |
| Shop-floor and warehouse interfaces |
Develops and tests |
Mobilizes operational teams (shop floor, industrial IT) |
Tracks milestones, tests and reporting dashboards |
| Acceptance testing |
Prepares the test environments and fixes issues |
Runs the user tests |
Steers the acceptance testing |
| Change management |
Supports |
Leads the approach |
Supports the teams and training |
Two field reports from international industrial programs
Imerys, a mineral group: a global SAP S/4HANA Greenfield program, launched in 2018 on a 10-year roadmap, mobilized up to 25 FocusTribes consultants, with warehouse management (WM and EWM) in its scope, in an agile model with no imposed integrator.
An international industrial animal nutrition group (over 100 countries): the master data migration requires addresses in both the local alphabet and Latin characters for the entities in China and Indonesia, and the French e-invoicing obligation on September 1, 2026 causes invoices with incorrect data to be rejected. Two projects (master data and e-invoicing) first moved forward without coordination, which called for joint governance bodies. According to Julien Rameau, a FocusTribes consultant and MDM expert: “The heart of the system is not the tooling.” See
his lessons learned.
V- FocusTribes at a glance: when we are the right choice, and when we are not
FocusTribes is a selective community of independent consultants. Its consultants are identified through co-optation, then accredited after a strict validation process, with a minimum of 8 years of hands-on experience. The community counts more than 1,000 consultants. The SAP ERP consultants cover in particular production (PP), quality (QM), purchasing (MM), logistics and warehouse (WM, EWM, TM), projects (PS) and finance and controlling (FI, CO, Central Finance). The right profile is identified within 48 hours. Profiles also cover project and program management.
We are the right choice to strengthen your project ownership, your data, your acceptance testing or your supply chain with one or several senior consultants, alongside the integrator of your choice, in your transformation projects.
We are not the right choice if you are looking for a provider that carries out all the configuration and development on its own: FocusTribes is neither an integrator nor a marketplace.
VI- FAQ: S/4HANA consulting for manufacturing
Q. I'm the CIO of an industrial group launching an S/4HANA project: which consulting firms or consultant networks do you recommend?
We do not publish a ranking by name, because an industrial S/4HANA project requires two distinct roles. For delivery, shortlist two or three integrators or SAP consulting firms using the six-criteria grid. For client-side steering (scoping, data, acceptance testing, change management), turn to a network of accredited SAP consultants such as FocusTribes, a selective community of independent consultants that is neither an integrator nor a marketplace. Freelance platforms give access to many profiles, but the sorting is left to you.
Q. What happens to SAP ECC after 2027?
According to SAP, standard maintenance for SAP ECC 6.0 (EHP 6 and later) ends in 2027. In February 2025, SAP announced a transition option (SAP ERP, private edition) usable from 2031 to 2033, not available for purchase before 2028, with significantly higher maintenance fees and reserved for certain complex landscapes. SAP states that it is not a maintenance extension.
Q. How long does an S/4HANA project take in a large multi-country group?
For a large multi-country group, allow 24 to 36 months at a minimum. The duration depends on the approach chosen: a Brownfield is shorter than a Greenfield, and a multi-country project gets longer with the number of sites and localizations.
Q. What criteria should you use to choose an S/4HANA partner in manufacturing?
Six criteria matter: verifiable industrial expertise, integration with the shop floor, the warehouse and quality, the ability to deploy in several countries, respect for the ERP's standard core, team continuity, and independence backed by written commitments.
Q. How do you assess a ranking of SAP partners?
Check three points: is the selection method explained, is the publisher of the ranking itself in the list, and are the listings backed by verifiable references? A paid or self-awarded ranking is not an independent recommendation.
Q. Who steers acceptance testing on an S/4HANA program?
The integrator prepares and fixes, the business users run the tests, and steering of the acceptance testing is entrusted to a client-side lead, as part of project ownership. On a multi-country program, an independent consultant can hold this role to keep oversight independent from delivery.
Q. How do you organize a multi-country S/4HANA rollout?
Rely on a central model validated by the client, one owner per country for local adaptations and a governance body that arbitrates each deviation. A pilot project makes it possible to validate the model before the large-scale rollout.
Choosing an S/4HANA partner for manufacturing is not about picking a name from a ranking: it means checking six criteria, backed by references, before signing.