Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Migrate from Flex UI 1.x.x to 2.x.x

Why migrate to Flex UI 2.x.x?

why-migrate-to-flex-ui-2xx page anchor

Twilio Flex UI 1.x.x will reach end-of-life (EOL) on June 30, 2024. As a result, you must migrate to Flex UI 2.x.x by July 2024.

We recommend that you upgrade to Flex UI 2.x.x so you can continue accessing new features, such as:

Getting expert help with your migration

getting-expert-help-with-your-migration page anchor

You have several options for migrating to Flex UI 2.x.x:

  • If you have an in-house developer team, you can use this guide to migrate on your own.
  • You can tap into the expertise of Twilio Professional Services(link takes you to an external page) . Flex solutions experts will complete a focused evaluation of your business's environment and provide documented recommendations for a smooth upgrade. If you decide to take this route, start by reaching out to your Twilio Account Executive to learn more.
  • You can reach out to one of Twilio's partners. Twilio has an ecosystem of system integrator partners that work extensively with Flex. They can assess your business's current Flex environment and work with you to develop a migration strategy. See details about our recommended partners(link takes you to an external page) .

Use this guide to migrate on your own

use-this-guide-to-migrate-on-your-own page anchor

This Flex UI 1.x.x to 2.x.x migration guide covers breaking changes to the Flex UI programming interfaces. It covers required changes you may need to make to custom code or plugins. The most notable changes are:



For details on each Flex UI interface mentioned in this migration guide, their description and usage code examples, check out the Flex UI API docs(link takes you to an external page).

If your migration doesn't go as planned, you can roll back your changes to use Flex UI 1.x.x if necessary.

Review these resources to learn more about Flex UI 2.x.x:

Migration process overview

migration-process-overview page anchor

Try the migration in a test environment first. Starting with a test environment enables you to identify and correct any unexpected effects without impacting your production application.

The following sections outline high-level migration steps that you must take:

Without custom plugins

without-custom-plugins page anchor

If you don't have any custom plugins for Flex UI, complete the following steps:

  1. Ensure that you have read Set up your account with Flex Conversations: Prerequisites . Flex UI 2.x.x is designed to work with Conversations.
  2. Enable Flex UI 2.x.x on your account .

If you have deployed custom plugins to Flex UI, complete the following steps to ensure that your plugins will work with Flex UI 2.x.x:

  1. Review Flex UI 2.x.x updates that can affect your customizations to understand what updates you will need to make.
  2. Ensure that you have read Set up your account with Flex Conversations: Prerequisites . Flex UI 2.x.x is designed to work with Flex Conversations.
  3. Disable your existing 1.x.x-based plugins.
  4. Enable the latest version of Flex UI on your account using the Versioning and Updates page on
  5. Update dependencies to be compatible with Flex 2.x.x .
  6. Test your plugins in Flex UI 2.x.x. If necessary, update your plugins for Flex 2.x.x .
  7. Apply any updates to your customizations that you identified in step 1.
  8. Deploy your Flex UI 2.x.x plugins .

Rate this page: