> For the complete documentation index, see [llms.txt](https://docs.nosto.com/magento-2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/magento-2/guides/upgrading-to-4.0.0.md).

# Upgrading to >= 4.0.0

From this article you can find a checklist what to take into account when you upgrade to Nosto module version >= 4.0.0.

## Upgrade only Nosto module

It's recommended not to upgrade any other modules at the same time when upgrading Nosto module to version >= 4.0.0. If other module upgrades alter the product data it might lead into a full re-index of Nosto product data during the module upgrade process. With large catalog and multiple store views the full re-index might take hours to complete.

## Run the setup commands

As with any Magento 2 module upgrade remember to run `bin/magento setup:upgrade` and `bin/magento setup:di:compile` commands. Note that these might be automated by your deployment flow.

## Set your indexers to "Update by Schedule"

We introduced two new indexers along with version 4.0.0. It's highly recommended to set the indexer mode to be "Update by Schedule" for both of the indexers. Read more about the new indexers [here](/magento-2/features/indexer.md)

## Re-connect Nosto account

If you are upgrading from module version < 3.9.0 you must re-connect your Nosto account. This is due to the fact that order confirmations are also sent through Graphql API that requires an additional authentication token.

## Double check the overrides

As version 4.0.0 introduces breaking changes (renamed classes, new indexers, changes in XML configuration files, etc.) you must carefully amend possibly module overrides you have in place.


---

# 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.nosto.com/magento-2/guides/upgrading-to-4.0.0.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.