Table of Contents

Migrate your web bot from the Old Builder (legacy) to the New Builder (Landbot 2 and 3)

Rafaela Basso Updated by Rafaela Basso

It is possible to create a copy of your bot from the Old Builder to the new Bot Builder, so you don't have to create it from scratch.

In this guide we will explain how to do it and clarify all your doubts about this process ๐Ÿš€

How can I create a copy for the current Builder?

Once inside your bot you will see a button on the top right corner, named COPY TO NEW BUILDER.

Click on the button, and a copy of your will be created to the new Builder.

What is going to happen to my bot?

The migration will not affect your current bot, it will stay the same.

We will create just a copy that is partially compatible*** with the new builder.

The new bot will have a new URL and a new ID. If your bot was already in production or embedded, it will stay as it is.

***NOTE: Check the Known Issues section below to see the compatibility of the blocks and the adaptations you must make.

You can easily see which one is the bot from the old builder, because it will have the OLD VERSION tag:

Where I can find the copy?

You can find the new bot in the Dashboard with the same name, but starting with "Copy of".

Known Issues with "Migrated Copies"

Not supported Blocks:

There are some blocks that due to their nature won't be available in the new Builder or need to be updated, here is a list of all of those, that will have to be set again in the copy of the new Bot Builder .

Blocks that do not exist in the new builder:

  1. Callback
  2. Keyword Jump
  3. Jump bot

Blocks that need to be created from scratch in the New Builder:
  1. Set a Variable
  2. Notifications (if Slack/Email notification in the same block). In the new Builder, these are 2 separate blocks.
  3. Human Takeover (if there is no Simple Flow Assignation)
  4. Webhook: All those Webhooks that used the Callback block to deal with responses, in the new Webhook block will need to be set up again. Keyword routing is deprecated.
Other features/actions not compatible
  1. Connections from not supported blocks will disappear: Connections that lead TO not supported blocks will remain there, but the arrows that come FROM the not supported blocks (output arrows) must be created again
  2. {html} tags in messages will become plain text visible to the user: In the new version of the message blocks it will understand html tags, so it needs to change {html} and {/html} for <html> and </html>
  3. * bold * tags must be set up again: The new text editor brings the Bold option
  4. Bot Jump FROM or TO New Builder bots are deprecated: It is not possible to jump between bots from different bot builder versions. We recommend migrating all your bots to the New Builder, and then use the Jump To feature between them.
  5. Graphic overlap: The location of the blocks will be very similar to the current one. However, as the size of some blocks is different, some blocks will be on top of others, and you might need to move them to be able to see them.

FAQ & Troubleshooting

Once the copy is done it doesn't allow me to preview or save and publish

If you have "Aliens" blocks that need to be recreated the bot cannot be saved or previewed. To fix it, look for the Alien blocks like the one in the picture below:

I created a copy of my bot, but there is a problem with the arrows/connections

If you have "Aliens" blocks that need to be recreated the bot cannot be edited. To fix it, look for the Alien blocks like the one in the picture above.

Then proceed with the following:

  1. Delete all the aliens before changing anything in the flow.
  2. Save the bot.
  3. Refresh the page.
  4. Keep working on the bot normally.

I'm trying to create a Copy and there is an error that says: AN ERROR OCURRED WHILE PROCESSING THE REQUEST :(

It could be a "TimeOut error", it means that due to a slow connection the process took too long for the servers to process. Please make sure that the process is done with good connection and without interruptions

How did we do?

How to migrate your bot from Landbot v2 to Landbot v3

Contact