> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/enterprise/upgrading.md).

# Upgrading

## Upgrading

Upgrades come in two flavors: software upgrades and appliance upgrades.

Software upgrades are released as minor version bumps (eg 2.0 to 2.1) and can be performed directly on the current installation.

Appliance upgrades are released as major version bumps (eg 2.0 to 3.0) and require you to fire up a new instance and migrate your existing enterprise data over from the old one.

We strongly recommend [backing up your existing data](/enterprise/backing-up-enterprise-data.md) immediately prior to any upgrade.

## Software Upgrade

1. [Back up your existing data](/enterprise/backing-up-enterprise-data.md)
2. Download the latest .ksb
3. Install the ksb at `<hostname>/enterprise/install`.

The installation is complete once you see the following screen:

![Installation Complete](/files/t1NGtRWMuEvcC16oO5O3)

Note: You do not need to upload your license again if your license is still valid.

## Appliance Upgrade

Occasionally the underlying appliance will need to be upgraded as well. Although not as simple as the basic upgrade, the process only requires a few steps.

1. [Back up your existing data](/enterprise/backing-up-enterprise-data.md)
2. Download the latest .ova
3. Install your license on the new instance
4. [Add your ssh key](/enterprise/ssh-access.md) to the new instance
5. [Restore your existing data](/enterprise/restoring-enterprise-data.md) onto the new instance


---

# 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.kumu.io/enterprise/upgrading.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.