If you run sales or service on Salesforce and have put off replacing it because of the time and cost of moving, ServiceNow has just made its pitch. On 12 November 2026, it announced Autonomous CRM Engine, an AI-native tool designed to help organisations move off legacy CRM platforms and onto ServiceNow CRM in weeks rather than months or years.
Anyone who has been through a CRM replacement will treat that claim with caution. But suppose the engine only halves the time. The question most businesses ask first, how long the move will take, becomes less important, and a harder one moves up the list: what should sales and service look like once we are on the new system? No software can answer that for you.
For most organisations, this is a planning question for 2027 rather than a project for next quarter. Here is what to know and what to decide before then.
What ServiceNow has announced
ServiceNow describes the engine as working in four stages:
- Discover: map how the existing CRM is really used, including its workflows, custom objects and integrations.
- Design: propose a new target state based on ServiceNow workflows and good practice.
- Build: build the approved changes directly into ServiceNow CRM.
- Monitor: keep checking the new setup after go-live for configuration errors and drift.
Before you build a plan around it, check three things.
It starts with Salesforce. SiliconANGLE reports that the engine works with Salesforce at launch, with other platforms to follow. If you are on a different CRM, this is one to watch, not one to plan around yet.
Your team must approve the redesign. ServiceNow made it clear that this is not a ‘lift and shift’. The engine proposes a new process and builds only the changes you approve. That means your people need time to review and decide, no matter how fast the software runs.
Most organisations cannot buy it yet. ServiceNow has released the engine in controlled availability, meaning limited access for now, and plans to add capabilities in 2027. It has not published pricing either, leaving a gap in any business case you try to build this year.
Plan for faster, not fast
“Weeks” is the best-case scenario, according to ServiceNow. Amit Zavery, its president and chief product officer, told Diginomica that timing depends on each customer and on what their environment looks like. A CRM that has been heavily customised and adapted for ten years will not move at the speed of the headline.
Your historical data is also a project in its own right. The engine is built to support discovery, design and build, and ServiceNow’s product page explains that this frees your experts to focus on data mapping, migration and integration. CXM World suggests asking early how historical customer data will be handled, since it is often the most demanding part of a CRM move. It is worth giving that work its own plan and budget from the start.
Gartner’s first take advises leaders to assess whether the engine simplifies customer service operations and improves how they are governed. Migration time is only part of that assessment.
The harder question comes first
Discovery has long been one of the slowest parts of a CRM replacement: working out what the old system does, which customisations still matter and which integrations depend on them. If the engine takes on much of the discovery and build, you have to know what you want to change before the project starts. Go in without that and you could end up with the old problems on a new platform, only sooner.
For example, a complaint in your service team goes through three queues before it is resolved because of a workaround someone set up years ago and never removed. The engine should pick up that route and may suggest a shorter one. But should the complaint sit with the team that takes the call or the team that fixes the fault? What do you tell the customer on day two? Do you continue measuring the team on how fast it closes tickets?
Sales and service leaders need to make those decisions, with input from the people doing the work. They will also need time to explain the changes and help teams adopt them. Any savings in discovery and build should leave room in the budget for that work.
Questions to ask before your next CRM move
Whether or not you use the new engine, these questions are worth answering early:
- What do we want sales and service to look like in two years’ time, and what is stopping us today?
- Which parts of the existing setup should we retire rather than move?
- Which historical customer data do we need, and how will it come across?
- Who in the business will make the design decisions, and do they have the time?
- How will we measure whether the new process is working?
- Will the vendor or partner put the timeline in writing, based on our environment rather than a headline figure?
The last question matters most while the product is new, and CXM World gives buyers the same advice. A written estimate makes the vendor look properly at your customisations, integrations and data before committing to a date. It also clarifies what is included, such as historical data, testing and training, and what remains for your own teams. That gives you a sound basis for a budget and a plan you can hold everyone to.
Where Right Prompt fits
Right Prompt is a ServiceNow partner. We help organisations decide what they want from the platform before the build starts, then put the workflows in place and connect them to the systems they already run.
If a CRM move is on your agenda for 2027, now is the time to plan it. We can spend 30 minutes working through the questions above against your own setup. Get in touch.