> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/xport/use-cases/reconfigure-sites.md).

# Reconfigure Sites

Add Servers, Move Services between servers as the site expands

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2F5zXFxodtv6ZrX0iNP57B%2Fimage.png?alt=media&amp;token=9c101900-af77-4036-b92b-d9ad15e2e9e1" alt="" width="563"><figcaption></figcaption></figure>

## A Transportation Use Case Example

### The Problem

* **Road transportation** — a single server runs Management, SQL, and Recording for over 100 cameras covering depots, highways, and tunnels.
* **Camera-count expansion** — growing fleet demands more capacity than the all-in-one box can handle.
* **New hardware spin-up** — IT provisions a new server with XProtect Management, a new SQL instance, and an additional Recorder service. Its goal is to stop the Management Service and SQL on the previous machine while retaining the recorder and reconfiguring it to connect to the SQL on the new machine, all while preserving the media database.
* **Manual migration** = days —  re-adding 100 + cameras, and reconfiguring SQL ties risks downtime and errors. It also makes the previous media database inaccessible.

### The Solution

* **XPort automates** the entire cutover — moving configs, retaining media access, and rewriting recorder pointers — within hours, all within a single maintenance window.
* **70 % labor** savings — seamless scalability lets security teams focus on keeping roads safe, not babysitting systems.

### XPort Workflow Recipe

A single run of the [Move Recorders, Keep Footage](https://docs.vega365.com/xport/user-manual/move-recorders-keep-footage.md)workflow.

## Case Study Video

{% embed url="<https://youtu.be/CkJTVDViRY4>" %}
