> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/administrator-guide/installation/upgrade.md).

# Upgrade

## Upgrade from 6.3

There is no in-place upgrade from Flopsar 6.3 to Flopsar 7. Install a new 7 environment, issue new agent tokens, and attach 7 agents. Configuration, licenses, profiles, and collected data from 6.3 are not migrated.

What changes between the two lines:

* The Workstation is bundled with the server — there is no `flopsar-workstation.zip` to unpack.
* Server configuration is `settings.toml`, not `settings.yml`. EULA acceptance is `FLOPSAR_EULA=accept`, not an `eula:` key in YAML.
* Agents authenticate with a per-application pre-shared key (`key=`). A 6.3 agent cannot connect to a 7 server.
* TLS on the management interface is on by default.

See [Installation](/administrator-guide/installation.md) for a fresh 7 install.

## Upgrading within Flopsar 7

Within the 7 line, upgrade through the package manager. Configuration, TLS material, the master key, and collected data are preserved. See [Updates & Patch Management](/security/updates-and-patch-management.md).

```shell-session
# Debian / Ubuntu
$ sudo apt update && sudo apt install --only-upgrade flopsar-server

# RHEL family / Fedora
$ sudo dnf upgrade flopsar-server
```

### Agent

Replace the agent library with the new one and restart the JVM so the new library is loaded.

{% hint style="warning" %}
Upgrading the server restarts the service and invalidates API sessions. Users must sign in again.
{% endhint %}