> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-forms/17.latest/upgrading/version-specific.md).
# Version Specific Upgrade Notes
This article provides specific upgrade documentation for migrating to Umbraco Forms version 17.
{% hint style="info" %}
If you are upgrading to a minor or patch version, you can find the details about the changes in the [Release Notes](/umbraco-forms/17.latest/release-notes.md) article.
{% endhint %}
## Version Specific Upgrade Notes History
Version 17 of Umbraco Forms has a minimum dependency on Umbraco CMS core of `17.0.0`. It runs on .NET 10.
### Upgrading directly from Forms 13.9.9
This fix was introduced in version 17.5.0. It affects you if you upgrade directly from Forms 13.9.9 to an earlier version 17 release.
{% hint style="warning" %}
Versions 17.0.0 to 17.4.8 do not recognize the migration state that the 13.9.9 security patch added. The upgrade fails at boot with `The migration plan "UmbracoForms" does not support migrating from state "6149738f-25bd-44ac-9c1d-d66bbe9d4e2b"`.
{% endhint %}
Upgrade to version 17.5.0 or later instead. See [issue #1772](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1772) for details.
### Storage method for tracking rendered forms
This change was introduced in version 14. It affects you if you upgrade directly from version 13 to version 17.
In version 13, Forms tracked the forms rendered on a page using `TempData`. From version 14 onwards, the default value of the `TrackRenderedFormsStorageMethod` configuration option is `HttpContextItems`.
If your template renders form scripts using a custom snippet that reads the rendered form IDs from `TempData`, the snippet no longer finds them. As a result, the form scripts and any assets registered by custom field types stop rendering.
{% hint style="warning" %}
The scripts fail silently. Forms still submit, but conditional logic, field behaviors, and custom field type assets are missing from the page.
{% endhint %}
To resolve this, choose one of the following options:
* Update your snippet to read the rendered form IDs from `HttpContext.Items`.
* Use the `` tag helper, which respects the configured storage method.
* Set `TrackRenderedFormsStorageMethod` back to `TempData` to keep the version 13 behavior.
For the updated snippets and the tag helper, see the [Rendering Forms Scripts](/umbraco-forms/17.latest/developer/rendering-scripts.md) article. For the configuration option, see the [Configuration](/umbraco-forms/17.latest/developer/configuration.md#trackrenderedformsstoragemethod) article.
### Forms API URL paths
This change was introduced in version 14. It affects you if you upgrade directly from version 13 to version 17.
The Forms API endpoints moved under a `delivery` path segment. Both the endpoint for requesting a form definition and the endpoint for submitting a form entry changed:
| Endpoint | Version 13 | Version 14 onwards |
| ------------------------- | -------------------------------------------- | ----------------------------------------------------- |
| Request a form definition | `GET /umbraco/forms/api/v1/definitions/{id}` | `GET /umbraco/forms/delivery/api/v1/definitions/{id}` |
| Submit a form entry | `POST /umbraco/forms/api/v1/entries/{id}` | `POST /umbraco/forms/delivery/api/v1/entries/{id}` |
{% hint style="warning" %}
Requests to the version 13 paths return a 404 status code. Client-side scripts that submit forms fail without a validation error, as the request never reaches the Forms API.
{% endhint %}
Update any code that calls these endpoints, including client-side scripts, server-to-server integrations, and generated API clients.
For the current endpoint definitions, see the [Headless/AJAX Forms](/umbraco-forms/17.latest/developer/ajaxforms.md) article.
## Legacy version specific upgrade notes
You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/blob/umbraco-eol-versions/11/umbraco-forms/installation/version-specific.md).
---
# 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.umbraco.com/umbraco-forms/17.latest/upgrading/version-specific.md?ask=&goal=
```
`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.