SAP Enable Now Is Being Replaced by WalkMe - Here's What That Means for Your Organisation

If your organisation has been using SAP Enable Now, you've likely already heard the news: SAP acquired WalkMe in 2023 and has positioned it as the strategic digital adoption platform (DAP) going forward. Enable Now will continue to be supported for now, but the direction of travel is clear WalkMe is where SAP's investment is going, and Enable Now is not.

For many organisations, this raises a question. You've spent time, budget and internal resource building Enable Now content. Simulations, guided tours, process documentation, context-sensitive help potentially years of accumulated work.

What happens to all of that?

The good news is that this transition, handled correctly, is not just a technical migration. It is an opportunity to move to a more capable, more modern platform and to build a digital adoption programme that delivers measurably better outcomes than Enable Now ever could. This post explains what the shift from Enable Now to WalkMe means in practice, what you stand to gain, and how to approach the migration without losing what you've already built.

Why SAP Is replacing Enable Now?

SAP Enable Now has served its purpose well. For organisations running SAP GUI and early Fiori environments, it provided a workable way to create in-application guidance and process simulations. But the product has limitations that were always difficult to ignore.

The authoring tooling is dated. The Windows-based Desktop Assistant feels out of step with modern content creation expectations. Analytics capabilities are basic. And critically, Enable Now was built for SAP meaning it offered little practical value for any application outside the SAP ecosystem, even as enterprise technology landscapes became increasingly complex.

WalkMe, by contrast, was built from the ground up as a platform-agnostic digital adoption layer something that works across any web-based application, not just SAP. When SAP acquired WalkMe, it wasn't simply buying a competitor to Enable Now. It was acquiring a platform that could deliver what Enable Now never could: real-time, analytics-driven adoption guidance across the full enterprise technology estate.

The strategic logic is sound. SAP customers increasingly run mixed environments, SAP S/4HANA alongside Salesforce, ServiceNow, Workday, custom portals. A digital adoption platform that only works inside SAP was never going to be sufficient. WalkMe is.

What WalkMe Gives You That Enable Now Doesn't

Before addressing the migration itself, it's worth being clear about what your organisation actually gains by moving to WalkMe. This isn't a like-for-like swap. WalkMe is a fundamentally more capable platform.

Real-Time In-App Guidance on Any Application

Enable Now guidance is published as a separate overlay and often requires users to actively launch it. WalkMe guidance appears contextually, in the flow of work, triggered automatically by where the user is and what they're doing. The experience for end users is significantly more natural and usage rates reflect that.

Advanced Adoption Analytics

This is one of the most significant step-changes. Enable Now tells you who accessed your content. WalkMe tells you what users actually do which steps they complete, where they drop off, which processes are generating friction, and which guidance is changing behaviour. This data is transformative for optimisation and for demonstrating adoption ROI to the business.

Role-Based, Personalised Guidance

WalkMe allows you to show different guidance to different user groups automatically based on role, system, location, or behaviour. Enable Now requires separate content builds for different audiences. WalkMe handles this dynamically, reducing content maintenance overhead significantly.

Multi-Application Coverage from a Single Platform

A single WalkMe deployment can cover every application your users touch. Where organisations previously needed separate tools or separate Enable Now implementations for different systems, WalkMe consolidates adoption support into one governed, manageable platform.

A Platform with Active Investment Behind It

Enable Now's development roadmap has been static for some time. WalkMe is receiving ongoing investment as SAP's strategic DAP. Capability releases, AI-powered features, and deeper SAP integration are all in active development. Moving to WalkMe means moving to a platform that will continue to evolve.

The Migration: What's Actually Involved

The most common concern we hear from organisations at this stage is straightforward: we have a lot of Enable Now content. How much of it can we save?

The honest answer is: it depends but a well-structured migration approach protects far more than most organisations expect.

Step 1: Content Audit

Before any migration work begins, it's essential to understand what you actually have. Many Enable Now libraries accumulate content over years of SAP implementations and system updates. Not all of it will be current, accurate, or worth migrating. A structured audit identifies which content reflects live processes, which is outdated, and which is duplicated giving you a clear picture of what genuinely needs to be rebuilt in WalkMe versus what can be retired.

In our experience, a significant proportion of Enable Now content libraries contain material that hasn't been accessed in months or years. The migration becomes an opportunity to rationalise to start your WalkMe programme with a leaner, higher-quality content set rather than carrying legacy debt forward.

Step 2: Content Rationalisation and Prioritisation

Not everything needs to be migrated at once. Based on the audit, content should be prioritised by usage, business criticality, and process stability. High-frequency, high-impact processes payroll, purchase orders, key HR workflows move first. Rarely-used, low-impact content can be assessed or retired.

This phased approach means you're delivering WalkMe value quickly while managing the migration workload sensibly.

Step 3: Rebuild in WalkMe

Enable Now and WalkMe use different content models, so content cannot simply be exported and imported. Smart Walk-Thrus, SmartTips, ShoutOuts, and other WalkMe content types need to be built natively in the WalkMe editor but this is also where the quality uplift happens. Content rebuilt for WalkMe is built to WalkMe's interaction model, which means it behaves more naturally for users and is easier to maintain going forward.

This step also includes configuring role-based delivery so the right guidance reaches the right users automatically.

Step 4: Analytics Configuration and Baseline Setting

One of the first things to configure in WalkMe is the analytics layer defining the key workflows you want to track, setting baseline completion rates, and establishing the KPIs that will demonstrate adoption performance over time.

This step is often skipped in rushed migrations, and organisations later find themselves unable to evidence the ROI of the programme.

Step 5: Governance and Ongoing Optimisation

WalkMe content requires ongoing governance updating guidance when processes change, reviewing analytics to identify new friction points, and expanding coverage as the programme matures.

Establishing a clear ownership model and review cadence at the outset prevents the same content debt that affected many Enable Now libraries from building up again.

Common Concerns and Honest Answers

"We've invested heavily in Enable Now content. Will we lose it all?"

No but you won't be able to import it directly. The value of your Enable Now investment is the process knowledge embedded in that content: the understanding of your workflows, your user needs, your edge cases. That knowledge transfers. The content itself needs to be rebuilt, but a structured migration approach means you're rebuilding with expertise rather than starting from scratch.

"We're mid-way through an SAP implementation. Should we pause and switch now?"

This depends on your timeline and the maturity of your Enable Now content. In many cases, the most practical approach is to complete the immediate go-live with whatever is in place, then migrate to WalkMe in a planned phase shortly after. What we'd caution against is continuing to invest heavily in new Enable Now content when that investment will need to be repeated during migration.

"How long does a migration take?"

For a focused scope a single SAP module, a defined set of priority processes a migration can be completed in six to eight weeks. Larger estates with extensive content libraries will take longer, but a phased approach means you can have WalkMe live and delivering value well before the full migration is complete.

"Do we need internal WalkMe resource, or can we outsource the whole thing?"

Most organisations benefit from a blend: a delivery partner to lead the migration and build the initial content, combined with internal resource who are trained and certified to own WalkMe ongoing. Building internal capability from day one means the platform doesn't become permanently dependent on external support.

Starting the Transition

The most important step is the one most organisations delay: getting a clear picture of what you currently have in Enable Now and what a migration would realistically involve for your specific environment.

At Novitas, we provide a structured Enable Now to WalkMe migration service that covers every stage from content audit and rationalisation through to WalkMe build, deployment, and ongoing optimisation. As certified WalkMe builders with deep SAP training expertise, we understand both platforms in detail, which means migrations we run are more efficient and the WalkMe content we produce is built to reflect how your users actually work.

If you're at the stage of assessing what a migration would mean for your organisation, get in touch we're happy to talk through your current Enable Now landscape and what a practical transition plan would look like.

Explore our WalkMe services to learn more about how we support organisations at every stage of their digital adoption journey.