> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Moving to another server

> Transfer the Remnawave panel along with the data, check the nodes and switch the Axottle connection.

The relocation wizard transfers the Remnawave panel and its data to the new server.
It checks the nodes and switches the existing Axottle connection.
in the connection card if you have access to Remnawave backups.

Use PostgreSQL server only to change
[setup external BD](https://docs.axottle.com/en/remnawave/external-database.md).

## Preparation

* Create and check out fresh [backup](https://docs.axottle.com/en/remnawave/backups.md).
* Prepare SSH access to the new server and at least 5 GB of free space.
* If the original Remnawave is separate from Axottle, prepare SSH.
  Go to the original server. First, successfully find it runtime.
* Configure the API address of the new dashboard, DNS, TLS and reverse proxy.
  The old domain, before the DNS changes, can continue to lead to the source.

Creating a plan doesn't start the transfer. At the same time, the connection can be
Only one incomplete move; set up the external database first complete.

## Stages

1. **Transfer Panel.** Axottle checks servers, transfers environment and dump,
   deploys a new stack and checks the panel with an existing API token.
   The panel version comes from the source: the relocation is not an update to Remnawave.
2. **Stop the old panel.** Click "Stop the old panel" or
   If you confirm that you're stopping yourself, as long as both panels are running, they can
   Control the same nodes. Stop the panel container.
   The original database and server are saved.
3. **Check and rebind nodes.** View the list and reasons for inaccessibility.
   If necessary, Axottle updates the connection of available managed nodes
   Many nodes are already fitting the new panel after restoration.
   Dump; missed nodes remain in the report with the cause.
4. **Switching Axottle.** Changes the address of the existing connection,
   Therefore, the associated Flow, nodes and profiles retain the binding.

Long stages show progress in the card.
After restarting Axottle, the unfinished phase may require
Re-start; read the result first.

External PostgreSQL source is supported: data is copied through the host
Remnawave to the local PostgreSQL 17 of the new server.
Transfer from the newer main version of PostgreSQL to 17 is not supported.
External Redis is not portable – the target stack gets its container.

## Verification

1. Wait to check the new API and compare the number of users and nodes.
2. Make sure that the old panel is stopped and each node has a clear result.
3. After switching, check sync, client connection, and links
   The subscription domain is portable in the settings, but its DNS needs to be checked.
4. Recheck backup profiles: records with the old server are not overwritten
   automatically, they are listed in the final summary.

## Rollback

If the API check after switching fails, Axottle returns the previous one.
The **Download** button is also available after the move has been completed.
It returns the address of the original panel; it is not a data transfer back.

Before restarting the source, check which panel is currently operating.
If the original panel has been stopped, it needs to be stopped.
Changes to the new server won't show up in the old database.
Save the new data before you return it.

Once the move is complete, the SSH task details are removed from Axottle.
Save the original installation until you check the new server and backups.

Availability depends on the installed assembly; the instruction does not confirm the transfer on the live stand.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.