--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Migrating to Build Agent # Migrating to Build Agent {#ariaid-title1} Release version: Australia Updated August 27, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Migrating to Build Agent Build Agent is the advanced, agentic development experience within the ServiceNow AI Platform designed to extend and enhance application development beyond the capabilities of App Engine Studio (AES). ServiceNow customers should consider migrating their AES applications to Build Agent when their development needs require custom logic, scripting, or the creation of global apps instead of scoped ones. This migration enables developers to work in a more flexible and powerful environment that supports complex app development workflows. Show full answer Show less ## When to Migrate Migration to Build Agent is recommended when AES's guided, wizard-based development approach limits your app's functionality. For example, when you need to: * Add custom scripting or logic * Develop global scope applications * Modify base system applications Build Agent is embedded within existing IDEs like ServiceNow Studio and the ServiceNow IDE, allowing seamless transition as app complexity grows. ## What Migration Involves The migration process is primarily a shift in development workflow rather than a technical migration. When moving to Build Agent, your AES app is converted to ServiceNow Fluent, enabling use of IDEs for development. Existing artifacts such as tables, flows, workspaces, ACLs, and playbooks remain accessible and modifiable. Key changes include: * Transition from AES's step-by-step wizard interface to a natural language prompt-driven, iterative development cycle with Build Agent. * Adoption of a new workflow centered around prompting, reviewing, and accepting or rejecting Build Agent outputs. * Access to scripting capabilities, global applications, and modification of base system apps. This requires developers to adapt to new tools and practices suitable for more complex and large-scale development tasks. ## Key Differences Between AES and Build Agent * **Interface:** AES uses a guided wizard; Build Agent uses conversational prompts within IDEs. * **Scope:** AES supports only scoped apps and a limited set of artifacts; Build Agent supports both scoped and global apps and a full range of artifacts including business rules, script includes, client scripts, and UI Builder pages. * **Script Access:** AES requires conversion to ServiceNow Fluent and IDE use for scripting; Build Agent integrates scripting generation and modification directly. * **Base System Modification:** AES restricts modifications to custom scoped apps; Build Agent allows edits to any application including base system apps. For customers, migrating to Build Agent means unlocking a more powerful, flexible development environment embedded in familiar IDEs, enabling advanced app customization and scaling beyond AES limitations. Build Agent is the agentic development experience on the ServiceNow AI Platform. Migrate your applications from App Engine Studio to Build Agent to expand your app's capabilities and take advantage of the agentic developer experience. ## When to migrate to Build Agent {#aes-migrating-to-build-agent__section_arc_xtd_vjc} When building apps with App Engine Studio (AES), you may reach a point where your development needs exceed the scope of what AES can offer. You might need to add custom logic to an app, add scripting, or build global apps instead of scoped ones. When this occurs, you need to migrate your application to a development environment that supports more complex capabilities. Build Agent, the agentic developer experience on the ServiceNow AI Platform, supports these advanced capabilities, and the process of migrating apps to Build Agent happens in the background. Build Agent is embedded within the same development environments (ServiceNow Studio and the ServiceNow IDE) that AES you already use when your work exceeds AES capabilities. The agent generates full-stack applications and artifacts using natural language prompts. To learn more about Build Agent, see [Build Agent](https://www.servicenow.com/docs/uPGWJkjDyp1tG_cmu3eF3Q "The ServiceNow Build Agent application is an autonomous AI agent that creates and updates ServiceNow applications from natural language prompts. You can also use Build Agent to get answers to general ServiceNow development questions."). Whether you have an AES app that you want to extend, or you want to build something new, Build Agent offers the full suite of developer tools and the agentic development experience on the ServiceNow AI Platform. ## What migration involves {#aes-migrating-to-build-agent__section_what_migrates} Migrating to Build Agent is more of a development workflow adjustment than an actual migration process. When you're ready to migrate to Build Agent, the agent converts [the the AES app to ServiceNow Fluent](https://www.servicenow.com/docs/U8znXdwPI50FjwnB9jp1XQ "Convert an existing application to support development in source code with ServiceNow Studio."), enabling you to work in an integrated development environment (IDE). When your app is converted to ServiceNow Fluent, you can also work in ServiceNow Studio. Existing applications and app artifacts, such as tables, flows, workspaces, ACLs, and playbooks, are already accessible in ServiceNow Studio and available to be modified with Build Agent. What does change is how you complete tasks. AES developers are accustomed to thinking in terms of wizard steps and form completion, which guides them through completing specific tasks. Development using Build Agent, however, operates using natural language prompts and iterative development. So if you plan to migrate to Build Agent, you must adjust to the cycle of prompting, reviewing, and accepting or rejecting Build Agent output. You also gain access to scripting, global scope applications, and modification of base system applications with Build Agent. For some, this might mean learning new systems or developing new practices for a different scale of work. For more information about adjusting to the Build Agent development workflow, see [Getting started with Build Agent](https://www.servicenow.com/docs/4l1fZrA8CbBxUoEZJsI9ZA "Use the following guidelines to help you transition from using App Engine Studio to Build Agent."). ## Key differences between App Engine Studio and Build Agent {#aes-migrating-to-build-agent__section_key_differences} In addition to the workflow adjustment, there are several differences between AES and Build Agent that affect the developer experience. Interface : AES uses a guided wizard interface, while Build Agent uses a conversational prompt interface inside ServiceNow Studio or the ServiceNow IDE. Scope : AES supports scoped applications only and creates only the artifacts enabled by its integrated builders, such as tables, experiences, flows, workspaces, and ACLs. Build Agent supports scoped and global applications and can create the full set of development artifacts, including business rules, Script Includes, Client Scripts, ACLs, and UI Builder pages. Script access : To add scripting to AES applications, you must convert the application to ServiceNow Fluent and open the application in an IDE, such as ServiceNow Studio. Because Build Agent is already embedded within an IDE, the agent generates and modifies scripts. Base system application modification : With AES, you can modify only custom, scoped applications. Build Agent supports the modification of any application, including base system applications. For a full side-by-side comparison between App Engine Studio and Build Agent, see [App Engine Studio and Build Agent feature comparison](https://www.servicenow.com/docs/g~_R3mydUJjbb7RrwzASjw "App Engine Studio (AES) and Build Agent differ across interface, artifact scope, scripting access, application scope, and governance. Use this feature comparison to understand what changes when you migrate to Build Agent.").