Hard deadlines have a way of forcing decisions that were easier to put off when they felt comfortably distant. SAP Solution Manager’s end of mainstream maintenance isn’t new information, but the conversations happening right now in boardrooms and steering committees suggest that, for many enterprises, the transition from ChaRM is suddenly feeling very real. 

As a result, a clear divide is beginning to emerge. 

On one side are the organizations treating this as a migration exercise. They are mapping features, replicating processes, and looking for the closest possible replacement. 

On the other are teams who have looked at their ChaRM environment with the accumulated workarounds, approval gates, and tribal logic baked in over a decade, and are asking a more strategic question: what should actually exist in its place? 

We put that question to two leaders who have spent years driving transformation at scale in highly complex SAP environments, and sourced a wider industry perspective on how new systems can create the conditions for better processes to take hold. 

Their perspectives are direct and perhaps a little uncomfortable, but they come back to one specific point: the 2027 deadline is a moment to build a change model designed for what your business really demands.

The Clock Is Already Running, But Not Everyone Knows It

David Lees has spent over two decades leading SAP transformation programs in some of the world’s most complex global enterprises. As CDIO at Basis Technologies, he’s now on the other side of the table, and what he’s hearing in conversations tells a revealing story: 

ChaRM was built for a specific era of SAP change and, for many organizations, it served that era well. The reality is that demands have changed fundamentally since most first deployed it. What surprises me when talking to enterprise leaders is that a few still aren’t aware they need to be planning their strategy around migrating away from Solution Manager in the coming years, and that Cloud ALM isn’t a like-for-like replacement for ChaRM. 

There’s an assumption that this will be a straightforward migration. Cloud ALM is the strategic destination for most enterprises, but SAP has itself designated a specific set of capabilities — things like template protection and complex retrofit — as out of its native scope and handled by partner solutions instead.

My advice is to start by mapping out your current ChaRM processes and understanding where the gaps will land for your specific landscape, and where you will need additional capabilities. The teams who are in the best shape are the ones who started that conversation 12 months ago. 

David’s advice applies at any stage of the transition – but the earlier, the better. SAP’s Cloud ALM team has already drawn a clear line between the capabilities that Cloud ALM covers and those that have been formally designated to partner solutions, including template protection, GxP requirements, and more. Complex enterprises need to know where their requirements land and make a plan before pressure shapes the roadmap for them.

If you’re running a parallel S/4HANA migration, the same planning gap applies. Getting ahead of it early is what separates the teams that realize value sooner. Here’s the proof.

The Blank Page SAP Teams Shouldn’t Waste

If David Lees has mapped the technical terrain, Sana Asher focuses on the opportunity it creates.  

After more than 30 years in the SAP ecosystem, Sana has built a reputation as a human-first SAP advisor and the creator of MasterclasswithSAP. She views the transition away from ChaRM as a chance to ask whether the way change moves through SAP today is still the way it should tomorrow: 

Moving on from ChaRM is a reset. Most SAP teams are going to get this wrong. They’ll replicate everything they had: same approval gates, same change types, same transport-centric thinking, just in a shinier tool. Here’s the truth: ChaRM didn’t give you a process. It became your process, and nobody questioned it because it was baked into Solution Manager and it worked well enough. 

Now you have a blank page, so use it. Rethink your change categories by business risk, not system architecture. Kill every approval gate that exists because of a ChaRM workaround instead of genuine governance need. Build fast lanes for low-risk changes. Reserve the hard stops for where the blast radius actually warrants it. 

My number-one piece of advice? Do a process autopsy before you touch a single new tool. Map what actually happens in your change process today, not what the documents say. Then ask at every step: is this governance, or is this a ChaRM workaround? I’d bet 30–50% of what you’re doing exists because of how ChaRM worked, not because anyone designed it that way. Strip that out first, then configure your new tool. Otherwise, you’re just building an expensive replica of an old problem.

Part of what that audit often reveals is how much of the process lives in specific people’s heads rather than in the system itself – a risk that goes well beyond ChaRM.

New Software Sets New Defaults

Beneath what David and Sana are describing sits a broader principle, and it applies every time an organization adopts new technology at scale. New systems can reset defaults, reshape habits, and either embed more intelligent ways of working or carry the old ones forward in a new environment.

Oliver Dorsner, consulting director and executive board member at Corporate Business Solutions, made this point on the Transformation Every Day podcast. Speaking about enterprise technology adoption more broadly, his framing captures exactly the mindset SAP teams are now confronting as they plan the ChaRM transition: 

Responsible organizations really see [adoption of new technology] as a chance to change. This is supported if the changes are embedded in a kind of software or process that you are using. SAP software or other applications give guardrails to new processes, new ways of managing. Software applications are enablers to change companies, to change processes, probably also to change some cultural aspects. They only enable us. 

The key word here is enable. The transition from ChaRM to Cloud ALM creates an opportunity to embed the change behaviors enterprises actually want and need, instead of carrying old habits forward under a different interface. 

That model exists. It’s called Intelligent Change Management, and it’s built for SAP teams that need to drive the right changes at the speed the enterprise expects, with the control complex organizations require.

The moment to embed better is available right now. The question is whether you use it deliberately or allow it to pass.

The Conversation Worth Having Now

The 2027 deadline is real, but the more important deadline is the one you set internally. This is the point at which you map your current state, understand where Cloud ALM covers your needs and whether you require partner capabilities, and decide what you actually want your change model to look like on the other side. 

If that conversation hasn’t started yet, it’s worth having it with people who have been inside this picture at scale. 

Let one of our SAP experts guide your move from ChaRM to Cloud ALM and support you in building an Intelligent Change Management model that keeps pace with your business.