Skip to main content

Convert classic apps

Convert classic apps to the new app building experience.

Retool supports converting classic apps to apps that use the new app builder. Through this process, the existing classic app is preserved, and you create a new version of the app with a refreshed user interface and functionality.

The classic app experience is still supported, and you are not required to convert any apps you've created to the new experience. Classic apps will continue to be supported for at least two years after the general availability of Retool's new app building experience.

Convert classic app​

Before converting your app, review the capabilities and limitations that currently exist for converted apps.

Use the following instructions to convert your existing app to the new app experience:

  1. From the apps landing page, click Create > App.
  2. In the Chat tab, select Convert classic app.
  3. In the modal that appears, find the app that you want to convert and click Convert.
  4. In the Chat tab, review the initial message from the agent, and click Start conversion.
  5. The agent begins work converting your app. The existing app will be untouched—the agent does not have permission to edit it. The agent prompts you when you need to approve a function run. Refer to the how it works section for more information about what the agent does during the conversion.
  6. When the agent is done building, review the generated app, and test key use cases to ensure that the app is still functioning as expected. If the generated app is missing features, prompt the agent to address specific gaps. It can help to specifically tell the agent to look in the linked classic app for the functionality you're looking for.

How it works​

When you convert a classic app to the new app building experience, an agent does the following:

  • Imports the classic app source code as read-only files to use for context.
  • Creates a phased conversion plan.
  • Converts resource queries, JavaScript queries, and other code into functions.
  • Builds the new app one phase at a time. This keeps large conversions from depending on one long model context. Context is cleared for each new phase, aside from a summary the agent writes at the completion of each phase.
  • Compares the generated app against the classic app source code and queues follow-up fixes for obvious gaps.

The agent continues running if you navigate away or close the browser at any point. You can stop the agent at any time from the prompting box.

Keep the following considerations in mind when converting a classic app:

  • The conversion process can take a long time for complex apps. For large apps, conversion could take up to an hour.
  • Depending on the model that you are using, the process is also token-intensive. To keep costs lower, consider choosing a model with lower per-token costs.

Capabilities and limitations​

The following tabs show a summary of the current capabilities and limitations of classic app conversion.