# RPC Migration to 9.x.x

Run the following command to migrate the database and configuration files of your RPC node to the latest version. 

The database migration requires syncing a snapshot that we have already updated and may take several hours, so you may want to consider running the process in the background.

```
./migrate_to_v9.x.x.sh rpc <container_name> <host_supra_home> <validator_ip>
```

After the script completes:

1. Transfer your custom settings from `config_v8.0.x.toml` to `config.toml.`
2. Enter the updated Docker container and attempt to start the node interactively:

```
docker exec -it <container_name> /bin/bash
./rpc_node start
```

Wait for a couple of minutes to see if the process terminates with an error.&#x20;

If it does, then please contact [Supra Support](/supra/network/node/creating-supradesk-tickets-via-email.md) and share a screenshot or text copy of the error.

If no error is shown, stop the node again and follow the [normal steps](broken://pages/8CTJ3vUs7C9ZJogsEh0n) to start it again&#x20;

Finally, follow the steps in the[ Monitor Node Synchronization article](/supra/network/node/node-upgrade-guide-mainnet/monitor-node-synchronization.md)  to check if your node is in sync.

\ <br>


---

# 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://supraoracles.gitbook.io/supra/network/node/node-upgrade-guide-testnet/rpc-migration-to-9.x.x.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.