Dialogflow Migration V2 Guide
By Alessandro Botticelli -- November 27, 2019
Dialogflow have extended the V1 API shutdown deadline to March 31st, 2020. Google announced it would discontinue V1 API support, requiring companies with legacy agents to migrate to V2.
The Bot Forge has been developing chatbots using V2 since the prior year, though many organisations still operate V1 agents requiring migration. Here is our guide to planning your transition.
Migration Complexity
Migration complexity depends on feature usage and integration points. Those using fulfilment webhooks, inline editors, or Dialogflow APIs must update code and endpoints. If agents lack webhook functionality, API calls, or integrations, minimal changes are needed. Web agent implementations calling REST API face the greatest impact due to authentication modifications.
Basic Migration
Organisations with existing V1 website chatbots should begin planning transitions immediately, adding new features post-upgrade. The migration represents potentially significant work for complex bots. For production systems, creating a duplicate bot project for testing is recommended, with comprehensive retesting before deployment.
Chatbot Web Interfaces
We recommend using the V2 API for all custom website chatbot creation. All of our new projects employ V2. If you are seeking assistance with migration, please get in touch -- we are Dialogflow experts and can help ensure a smooth transition.
About The Bot Forge
Consistently named as one of the top-ranked AI companies in the UK, The Bot Forge is a UK-based agency that specialises in chatbot and voice assistant design, development and optimisation.
If you'd like a no-obligation chat to discuss your Dialogflow V2 upgrade project, please book a free consultation.
Want to build with conversational AI?
Book a short call and we will help you choose the right approach.