Home / ES to CX migration / Should you migrate your Dialogflow ES bot to CX?
ES to CX migration

Should you migrate your Dialogflow ES bot to CX?

Check out my courses Learn Dialogflow ES and Learn Dialogflow CX if you would like to learn Dialogflow in depth. 

I am seeing a few people building a CX bot when an ES bot would work just as well.

On the one hand, Dialogflow CX is definitely more powerful than Dialogflow ES.

On the other hand

  • CX is more expensive
  • It is harder to learn CX
  • It is harder to maintain a CX bot
  • CX doesn’t yet have the same tool support

So my suggestion is to first build your bot in Dialogflow ES and then look to migrate it to CX.

This is the first part in my series on migrating your Dialogflow ES bot to CX.

When to migrate to Dialogflow CX

After building an ES bot, here are some good reasons to migrate to Dialogflow CX:

Slot filling

The bar for what qualifies as a slot filling bot is pretty high.

And if you are still sure that your chatbot does need slot filling, you should just start with a CX bot.

Followup intents

If you are using a lot of follow up intents in your Dialogflow ES bot, you should consider migrating it to Dialogflow CX.

Lots of Contextual fallback intents

If you are using a lot of contextual fallback intents, it means there are many places in your conversation flow where you need to handle unexpected input. This is usually a sign that you should migrate the bot to Dialogflow CX.

It is much easier to get back to a good state in a multiple turn conversation in Dialogflow CX.

High context lifespan

I recommend people use as small a context lifespan as possible for their ES bots. If you still find that you need to use high context lifespan values, it is a sign that you probably need to migrate to Dialogflow CX.

Flowchart size

If your conversation flowchart (e.g. I recommend Mindomo to design the conversation flowchart) is more deep than wide, it is usually a good time to migrate to CX.

When not to migrate to Dialogflow CX

There are two scenarios where you most likely don’t need to migrate to Dialogflow CX.

Very Few non-entry intents

In a previous article, I discussed entry vs non-entry intents. If you have very few non-entry intents as a ratio to entry intents, you probably don’t need a Dialogflow CX bot. Usually this is also a sign that you have built a large, one-and-done FAQ chatbot.

“Mostly Scripted” bot

If you are building a phone tree bot, and your user interacts with the bot mostly by clicking on a button, you can usually build it in Dialogflow ES. Even if the user has to occasionally type some text rather than just click on a button.

The BotFlo app gives you many tools which can speed up your Dialogflow bot development

This website contains affiliate links. See the disclosure page for more details. 
"The magic key I needed as a non-programmer"

The custom payload generator was the magic key I needed (as a non-programmer) to build a good demo with rich responses in DialogFlow Messenger. I've only used it for 30 minutes and am thrilled. I've spent hours trying to figure out some of the intricacies of DialogFlow on my own. Over and over, I kept coming back to Aravind's tutorials available on-line. I trust the other functionalities I learn to use in the app will save me additional time and heartburn.

- Kathleen R
Cofounder, gathrHealth
Check out my YouTube courses

Dialogflow CX Beginner Tutorial

Dialogflow ES vs CX using a Decision Tree Bot

Intro to NLU for technical non-programmers

Better Dialogflow ES Bots Using the CTFS Framework

Search the autogenerated transcripts of all my YouTube videos
In this free course, I provide some tips for managing large Dialogflow ES bots without compromising on accuracy.

Similar Posts