> 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/jet-bridge-deployment/environments/version-migration.md).

# Update to a new version

Select a Jet Admin platform version and test updates before Production.

Use the **Jet Admin Version** selector in environment settings to control platform updates. This is separate from [Version History](/ai-app-builder/test-and-publish/version-history.md), which tracks changes to your app.

## Update through environment settings

1. Open the app menu in the top-left corner of the builder.
2. Under **Environments**, select the gear icon beside the environment you want to update.
3. Review **View Changelog**.
4. Select **Latest** for automatic platform updates, or choose a specific available version.
5. Select **Save**.
6. Verify the selected setting and test your app's important flows.

See [Environments](/jet-bridge-deployment/environments.md) for the current settings screen and the staging-to-production scenario. The version number displayed beside Latest changes over time.

## Test before updating Production

Start in a staging environment connected to appropriate test resources. Check pages, data actions, integrations, workflows, and user permissions. Record the tested platform version before selecting it in Production.

Download an environment backup before a significant update. For major-version changes, review compatibility requirements and confirm your recovery approach before applying changes. A configuration created or saved on a newer platform version may not work on an older one; do not assume that selecting an older version is a complete rollback.

## Earlier migration reference

The notes below apply specifically to the historical 1.x.x-to-2.x.x transition. They do not describe current platform limitations.

## Historical migration: 1.x.x to 2.x.x

What should be done before the update:

* If you have never saved Menu items – apply any change and save menu customization

What should be done after the update:

* If you use any 3rd party integrations – run the Sync operation inside the resource settings

The following functionality is temporarily unavailable in 2.x.x:

* Adding/displaying Custom Fields (ex. FlexFields)
* Adding Collection segments in the Menu
* Adding Custom Views (ex. FlexViews)
* Adding Webhook tasks

The following features will be deprecated in the future and should be reconfigured differently

* Dashboard page type (use Custom page instead)
* Collection Segments (use Menu items grouping instead)


---

# 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/jet-bridge-deployment/environments/version-migration.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.