One Oil & Gas client had a tight migration window from a legacy SAP system. They had an emergency due to an upcoming deadline for shifting to a new data center in UT.

Jacob, the SAP global director, was in a bind. His team was up against a tight deadline for migrating to a new data center, and they were struggling to get everything in order. He knew he needed help, but he didn’t have time to get a full-fledged consulting firm involved. That’s when he discovered he could hire an SAP management consultant for a small, just two-week consultation to create a big-picture strategy.

He was ecstatic. This would be the perfect way to get his team on the same page and moving in the right direction. He called Thinking Minds and set up a meeting with the consultant for the following week.

After the meeting, Jacob was impressed with the consultant’s knowledge and expertise within the vertical. He quickly engaged her for two weeks of strategy/planning project. She studied the SAP landscape and provided a tentative plan to the stakeholders within the short engagement. She was also able to help him develop a detailed plan, which would allow his team to work more efficiently and effectively. The consultant’s fees were very reasonable, and Jacob was happy with the consultation results. He was so pleased with the level of details of her plans that he hired her for additional consultations until the migration was completed.

Thanks to the consultant’s help, his team could achieve their goals and exceeded their timeline targets by completing the migration almost one month earlier. Plus, it was a win-win for the consultant to work remotely on a project of this scale and get a longer-term global client project reference. He would highly recommend Thinking Mind’s short-term consulting services to others in a similar situation.

Environment: SAP ECC 6.0, New GL, AP, AR, SD, Joint Venture Accounting (JVA), Record To Report (RTR), RAR, Fixed Assets (FA), Asset Management(AM), Controlling (CO), Order To Cash (OTC), P2P, Fiori, FSCM, VIM, RICEFW, Winshuttle, iDoc, and LSMW.

#sapconsultant #sapcommunity #datamigration #oilandgas #sapconsultants

Related reading

• Messy S4 Migration
• The Complexity of Conversion to SAP S/4 HANA and Why Experts Need to Be Involved From Start

Why this story still matters: the ECC clock is running out

When Jacob’s team raced their migration, the deadline was a data center move. Today, most ECC 6.0 customers face a bigger one: mainstream maintenance for SAP ECC 6.0 ends on December 31, 2027. After that date, staying put means extended maintenance at a premium, historically around 2 percent of license value per year and rising, with 2030 as the hard stop.

That changes the math on every legacy migration. A move that used to be a “someday” modernization project is now a scheduled event with a fixed date. Companies that start strategy work in 2026 have room to choose their path. Companies that wait until 2027 will choose from whatever is left, usually the fastest and most expensive option.

Brownfield, greenfield, or selective: the three paths

Every ECC migration eventually faces the same fork in the road. The right choice depends on the health of your current system, not on what your vendor prefers to sell.

Brownfield (system conversion). You convert the existing ECC system to S/4HANA in place, carrying configuration, master data, and history with it. This is the fastest route and the least disruptive to users, which is why most ECC customers choose it. The catch: you also carry your custom code, your workarounds, and your fifteen years of “we will clean that up later.” Brownfield only works if your processes are fundamentally sound and someone has honestly inventoried the Z-code.

Greenfield (new implementation). You build S/4HANA fresh and migrate master data and open items, leaving the legacy system behind. This is the right call when business processes need redesigning, when mergers stitched incompatible processes together, or when the ECC system has become a museum of abandoned enhancements. It takes longer and costs more, but you do not drag technical debt into your new system.

Selective data transition. A middle path: convert a copy of the system, then migrate only the company codes, plants, or data you want. This is the standard approach for carve-outs, divestitures, and consolidating multiple ECC systems into one S/4 landscape. It is also the most technically demanding, which is exactly why it benefits most from specialist help.

Notice what Jacob did not do: he did not let a vendor pick the path by default. A short, focused strategy engagement gave his stakeholders an honest assessment of which route fit their landscape. Most migration pain in the market comes from skipping that step.

The skills nobody talks about: ECC knowledge is getting scarce

Here is a staffing reality that rarely makes the project plan. The consultants who know ECC 6.0 deeply, the ones who understand New GL quirks, Joint Venture Accounting, classic FI/CO/MM behavior, and the RICEFW objects that grew around them, are retiring or moving into S/4-only work. The market is training the next generation on S/4HANA, not on the system you are migrating away from.

That matters most for brownfield conversions, where success depends on people who understand both worlds: how the old process behaved in ECC and how it should behave in S/4. If your conversion is scheduled for late 2027, you are competing for a shrinking pool of dual-skilled consultants against every other company on the same deadline. Locking in that expertise early, even for a short strategy engagement like Jacob’s, is cheaper than hunting for it under time pressure.

What made the two-week engagement work

The pattern in Jacob’s story is worth copying, because it is the opposite of how most companies start. He did not sign a twelve-month consulting contract. He bought two weeks of senior expertise aimed at one question: what is our landscape, and what is the plan?

• It was scoped to strategy, not staffing. The deliverable was a plan stakeholders could align on, not bodies in seats.
• The consultant studied the actual landscape. Generic migration templates fail because every ECC system has its own history. Her plan reflected their RICEFW inventory, their iDoc flows, and their LSMW and Winshuttle tooling, not a slide deck.
• The plan was detailed enough to execute. A phased plan with dependencies, owners, and a timeline is something a team can actually run with, which is why his team finished a month early.
• It extended naturally. Because the strategy was sound, the follow-on work was execution, not rescue. That is the cheapest consulting you will ever buy.

If your ECC migration is still in the “we know we have to do something” phase, that is exactly when a short strategy engagement pays for itself. The 2027 deadline is fixed. The only variable is whether you spend the remaining time planning or panicking.