# Version Specific Upgrade Notes

This page covers specific upgrade documentation for migrating to version 17 of Umbraco Commerce.

{% hint style="info" %}
If you are upgrading to a new minor or patch version, you can find information about the breaking changes in the [Release Notes](/umbraco-commerce/release-notes.md) article.
{% endhint %}

## Version Specific Upgrade Notes History

#### 17.0.0

* The default property aliases for Customer Comments and Internal Notes have changed: `comments` is now `customerNotes`, and `notes` is now `internalNotes`. After upgrading from v13, existing data still lives in the database under the old aliases, so these fields appear empty in the v17 backoffice. To restore visibility without a database migration, remap the fields back to the original aliases in your composer using `OrderPropertyConfig`:

  ```csharp
  builder.WithOrderPropertyConfigs()
      .UpdateDefault(cfg => cfg
          .For(x => x.Notes.CustomerNotes).MapFrom("comments")
          .For(x => x.Notes.InternalNotes).MapFrom("notes"));
  ```

  Or scope to a single store with `.Update("yourStoreAlias", cfg => …)` instead of `UpdateDefault`. This remap covers both reads (backoffice display) and writes (saving edits).

## 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/tree/umbraco-eol-versions).


---

# Agent Instructions: 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:

```
GET https://docs.umbraco.com/umbraco-commerce/upgrading/version-specific-upgrades.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.