Schedule a friendly call

No sales reps, no pitch — just a relaxed chat with our ServiceNow specialists to see whether we can help with your Moveworks or ServiceNow move. Worst case, you leave with a clear next step.

Schedule a friendly call →

Short version: ServiceNow completed its acquisition of Moveworks on December 15, 2025 — its largest deal ever (~$2.85B). Moveworks now powers ServiceNow’s EmployeeWorks “front door” and feeds into Otto, ServiceNow’s unified enterprise AI layer. If you run Moveworks, your contract is being honored, but the roadmap now points to ServiceNow. If you run ServiceNow, EmployeeWorks/Otto is the Moveworks-powered path in. Either way, the decision in front of you is less about the tool and more about whether your data is ready for the agentic AI now sitting on top of it.

What actually happened

ServiceNow announced its intent to acquire Moveworks in March 2025 and closed the deal on December 15, 2025 for roughly $2.85 billion — the largest acquisition in ServiceNow’s history. Since then ServiceNow has moved fast: it launched EmployeeWorks, a Moveworks-powered conversational “front door” that combines Moveworks’ AI assistant and enterprise search with ServiceNow’s workflows and governance, and Autonomous Workforce, a set of AI specialists on the Now Platform. In May 2026 ServiceNow folded EmployeeWorks together with Now Assist and its AI Experience layer into Otto, a single unified AI experience for the enterprise.

Moveworks is still available standalone and existing contracts are being honored — but new investment and the product roadmap are clearly shifting toward the combined ServiceNow offering, with migration guidance expected to roll out over the next 12–24 months.

If you’re a Moveworks customer

Nothing breaks tomorrow. Your contract continues and the assistant keeps working. But it would be a mistake to treat this as business as usual:

  • Standalone investment is slowing. The innovation is moving to the ServiceNow-integrated products (EmployeeWorks, Otto). Plan on that trajectory, not the standalone one.
  • Support is transitioning. Moveworks support is moving to ServiceNow’s Now Support — a signal of where the platform is heading.
  • Your renewal is a decision point. Use it to evaluate the ServiceNow path deliberately rather than defaulting into a bundle.

If you’re a ServiceNow customer

EmployeeWorks and Otto give you a Moveworks-grade conversational front door natively on the Now Platform. That’s genuinely powerful — but it’s also newly bundled, and the temptation is to buy the whole thing before you know what you need. Evaluate against your actual use cases (IT, HR, employee service) and scope to what you’ll use.

Watch the “ServiceNow tax”

A recurring concern with ServiceNow acquisitions is that formerly standalone products become premium add-ons bundled into ITSM/ESM licensing — higher overall cost, less flexibility. The Moveworks integration is worth having, but it’s worth buying deliberately: right-size the license, avoid paying for capability you won’t deploy, and reconcile it against what you already own. This is the same asset-management discipline we apply to software audit defense and license optimization.

The real question: is your data ready for the agent?

Here’s what most of the coverage misses. EmployeeWorks, Otto, Autonomous Workforce — these are agents, and an agent is only as good as the data it reasons over. Point a capable AI assistant at a messy CMDB, inconsistent records, and un-owned data and it will be confidently wrong on real cases. We’ve watched more than one enterprise AI pilot dazzle in the demo and then quietly stall in production, and the cause is almost never the model — it’s the data underneath it. That’s a skills gap, not technical debt: the platform is fine and the license is paid; what’s missing is the discipline to run the data well.

So before you migrate onto EmployeeWorks or turn Otto loose, the highest-leverage move is to get the data foundation right — a trustworthy CMDB and clean, governed records the agent can reason over. Do that and the Moveworks technology delivers. Skip it and you scale bad decisions faster.

The bigger picture: the employee-AI landscape

The Moveworks deal is one move in a much bigger land-grab. Every major vendor is racing to own the conversational “front door” — the single place an employee types “I need a new laptop” or “how much PTO do I have left?” and the system actually does the work instead of pointing at a knowledge article. Knowing who really does what — and what you already pay for — is the difference between a smart consolidation and buying the same capability three times.

Here is how the main systems in this space actually stack up:

SystemWhat it really isBest fitWatch-outs
ServiceNow EmployeeWorks / OttoMoveworks’ assistant and enterprise search fused into ServiceNow’s workflow engine and governance (AI Control Tower), surfaced through Otto — the unified conversational layer announced May 2026.Orgs already standardized on ServiceNow for ITSM/HRSD that want one governed platform, end to end.Bundling and the “ServiceNow tax.” You pay for platform depth whether you use it or not, and data/CMDB readiness becomes a hard dependency.
Moveworks (standalone)The original best-of-breed employee copilot: conversational AI plus enterprise search across IT and HR, sitting on top of your existing stack.Multi-ITSM or non-ServiceNow shops that want a fast front-end assistant without re-platforming.Now owned by ServiceNow. Standalone investment is slowing and the roadmap points to the integrated products — treat every renewal as a decision point.
IBM AskHR / watsonx OrchestrateIBM’s HR-specialist agent (its own AskHR, productized): deep HR-domain automation across Workday, SAP, Oracle and 80+ apps, built no-code.HR-led programs that want an HR-first agent layered over existing systems without ripping them out.HR-centric, not an ITSM platform. You still need something for IT service management and the CMDB underneath it.
HR-specialist assistants (Leena AI, etc.)Point solutions focused on HR service delivery and employee engagement.Companies solving a specific HR-support pain quickly.Narrow scope — another silo to integrate and govern.
IT / employee-support copilots (Espressive Barista, Aisera)Best-of-breed conversational service desk and AIOps assistants.IT-led deflection projects, often across multiple platforms.Overlap heavily with native Now Assist / EmployeeWorks — easy to double-pay for the same deflection.
Enterprise search & copilots (Glean, Microsoft 365 Copilot)Horizontal answer and knowledge layers across all your content and apps.Broad knowledge-findability and productivity, not transactional service delivery.They answer, they don’t act — great at finding information, weak at completing governed workflows.

The honest takeaway: most enterprises already own two or three of these and don’t realize how much they overlap. The winners aren’t the teams who buy the most agents — they’re the ones who map what they have, pick the right front door, and get their data ready so the agent can actually act.

The Four Dragons migration & consolidation playbook

Whether you’re moving off standalone Moveworks, evaluating EmployeeWorks and Otto, or weighing IBM AskHR against a native build, the path is the same five steps. This is the playbook we run with clients:

  1. Map your real footprint. Inventory every assistant, copilot and agent already licensed across IT and HR — Moveworks, Now Assist, Microsoft Copilot, AskHR, point tools. Almost everyone finds overlap they’re paying for twice.
  2. Grade your data and CMDB readiness. Agentic AI is only as good as the data beneath it. A messy CMDB or fragmented HR data means the agent guesses — and guesses erode trust fast. Start with our free CMDB Health Calculator.
  3. Right-size the license before renewal. Reconcile what you actually use against what you’re bundled into, and neutralize the “ServiceNow tax” instead of defaulting into it.
  4. Choose the target architecture. Native (one governed platform), best-of-breed (a specialist front door on top of your stack), or hybrid. The right answer depends on your environment — not the vendor’s roadmap.
  5. Migrate with governance from day one. Roll out through a governed control layer with clear ownership, audit trails and success metrics, so the agents are safe to actually turn loose.

Nine times out of ten the blocker isn’t the technology — it’s a skills gap. Nobody in-house has stood up governed, data-ready agentic AI across ServiceNow, Moveworks and the HR stack before. That’s precisely the gap we close.

Book a working session with our team →

How Four Dragons helps

We’re an independent, boutique ServiceNow consultancy led by a former ten-year ServiceNow employee. On the Moveworks transition we help you read the acquisition honestly and plan your path (stay standalone, migrate, or consolidate), right-size the ServiceNow-integrated licensing to avoid overpaying, and — most importantly — get your data ready so the agentic AI actually works. We fix the foundation others skip.

Score your data readiness first with the free CMDB Health Calculator, then talk to us about your Moveworks transition.

Frequently asked questions

Did ServiceNow buy Moveworks?

Yes. ServiceNow completed its acquisition of Moveworks on December 15, 2025 for roughly $2.85 billion — the largest acquisition in ServiceNow’s history.

What is ServiceNow EmployeeWorks?

EmployeeWorks is ServiceNow’s Moveworks-powered conversational “front door.” It combines Moveworks’ AI assistant and enterprise search with ServiceNow’s workflows and governance.

What is ServiceNow Otto?

Otto is ServiceNow’s unified enterprise AI experience, announced in May 2026, which brings EmployeeWorks (Moveworks technology), Now Assist, and ServiceNow’s AI Experience layer together into one layer.

Will my existing Moveworks contract still work?

Yes. Existing Moveworks contracts are being honored and the assistant keeps working — but standalone investment is slowing and the roadmap now points to the ServiceNow-integrated products.

Should I migrate from Moveworks to ServiceNow?

It depends on your use cases and renewal timing. Treat your renewal as a deliberate decision point rather than defaulting into a bundle — and make sure your data is ready for agentic AI before you migrate.

What is the “ServiceNow tax”?

It’s the pattern where acquired products become premium add-ons bundled into ServiceNow ITSM/ESM licensing, raising overall cost and reducing flexibility. Right-size the license and reconcile it against what you already own.

What is IBM AskHR?

IBM AskHR is IBM’s own HR virtual agent, built on watsonx Orchestrate. It automates more than 80 HR tasks and millions of employee conversations a year, integrating with Workday, SAP and Oracle. IBM now offers the same watsonx Orchestrate HR agents to other enterprises.

Moveworks vs ServiceNow vs IBM AskHR — which should I choose?

It depends on your stack. ServiceNow EmployeeWorks and Otto fit organizations already standardized on ServiceNow; standalone Moveworks suits multi-platform shops that want a fast front door; IBM AskHR on watsonx fits HR-led programs on Workday or SAP. Most enterprises end up hybrid — the real work is mapping the overlap and getting your data ready.

How do I migrate off Moveworks?

Run the five-step playbook: map your agent footprint across IT and HR, grade your data and CMDB readiness, right-size the license before renewal, choose native vs best-of-breed vs hybrid, then migrate with governance in place.