> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/ai-app-builder/move-from-classic-to-ai.md).

# Move from Classic to AI

Use the existing Classic app as a set of requirements for a separate AI build. Do not assume a prompt automatically reproduces its configuration.

## Rebuild one task

1. Inventory its sources, pages, fields, actions, workflows, permissions, and publishing setup.
2. Choose one small task and prepare test data.
3. Follow [Build your first app with AI](/getting-started/start-here.md) using the same field names and business rules.
4. Compare the new app with the Classic task.
5. Test reads, writes, and restricted access before moving to the next task.

## Plan the switch

Record remaining differences and decide how users will move to the new app. Keep the existing app available until the replacement has passed the required checks.

| Requirement           | Check                                             |
| --------------------- | ------------------------------------------------- |
| Data source           | Reads and writes reach the intended system.       |
| Business rules        | Validation and workflow outcomes match.           |
| Access                | Restricted records and actions remain restricted. |
| Navigation and layout | Users can complete the task on their devices.     |

Use [Maintain an existing Classic app](/classic-app-builder/maintain-an-existing-classic-app.md) for legacy-editor work. Continue with [Test and publish](/ai-app-builder/test-and-publish.md) for the new AI app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/ai-app-builder/move-from-classic-to-ai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.