> 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/user-guide/project-settings/version-migration.md).

# Update to a new version

An update to a new major version can lead to some settings not being saved and there is a chance you won't be able to go back to the previous version after saving changes to the interface because of breaking changes. So do it carefully and at your own risk. 

**It is safe to create a separate project for the new version and copy settings from the old project. We highly recommend this way so you will able to revert any time.**

We are always trying to make version updates fully compatible so you don't need to make anything on your own, but there could be a few that can't be done automatically. 

**You can check your current Jet Admin version in Project Settings**

![](/files/-MjhteCqF6W0JdsNk0yR)

## Migrating from 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jetadmin.io/user-guide/project-settings/version-migration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.