# Migrate a VICIdial server to a new host in four steps

> Move a VICIdial server to a new host: connect the old server, review what moves, start the move, then read the check. Four steps, with pictures.

URL: https://trustane.com/guides/vicidial-migrate-server-new-host
By Trustane. Published 2026-11-17.

> **To the point**
> To migrate a VICIdial server to a new host with the Trustane console, open **Migrate** and pick the server it moves into:
>
> 1. **Connect**: give the old server's address and a login.
> 2. **Review**: read what moves and what it replaces.
> 3. **Move**: type WIPE and start.
> 4. **Done**: read the check, line by line.

Video: [Migrate a VICIdial server to a new host: connect, review, move, check](https://www.youtube.com/watch?v=VlwFnfhwYzw)

The pictures come from our demo account. The moves shown are demo data: the servers, addresses and figures are made up.

## Before you start

A move lands on a server we built for you, so you need one first. [Order a server](https://trustane.com/guides/vicidial-server-hosting-order), or use one you already have. The move replaces the data on that server, so do not pick one your agents are working on.

Then open **Migrate** in the console. It shows the four steps, any moves you have started, and the servers a move can go into.

![The Migrate page: the four steps, Your moves with pine-central moving, harbor-west ready to review and atlas-east moved, and Where it goes](https://trustane.com/media/15913a96c2503ecd-1600x982.webp "Migrate: your moves, and where a new one can go")

Press **Move into this one** on the server you want.

## 1. Connect your old server

The console needs to read your old server over SSH. Give it three things: the old server's host name or address, the SSH port, and the SSH user.

Then choose how it logs in:

- **Use SSH password.** You type the password for that user.
- **Paste a key (no password).** Press **Generate access key** and add the line it shows to that user's `authorized_keys` file on the old server.

Your old server must allow SSH from the address the page names. If you bring recordings, it must also allow SSH from the new server, because the new server copies the recordings directly.

Press **Check my server**. This step only reads the old server and changes nothing on it.

## 2. Review what moves

The console reads the old server and shows four figures: leads, recordings, users and campaigns. Under each one is what it replaces on the new server now.

![The Review screen: 96,412 leads, 38,250 recordings, 28 users and 6 campaigns moving in, Servers moving here 2 to 1, and Ready to migrate](https://trustane.com/media/48ae340d9dd4ab7c-1600x1133.webp "Review: what moves, and what it replaces")

Three more things are on this screen.

**Servers moving here.** If your old setup is a cluster, the screen lists each server with its address and role, and shows them becoming one. References to the old addresses are rewritten to the new server's address: extensions, numbers, remote agents, reports, recording links and web forms. The check at the end lists any that are left.

**What a cluster loses or keeps.** Four figures compare the old servers with the new one: dialing lines, agent seats, duplicate extensions and duplicate logins. If two old servers had the same extension, one copy is kept and the other is renamed and switched off, so nothing registers twice.

**What you can leave behind.** Configuration always moves: campaigns, in-groups, users, phones, numbers, call menus, scripts and statuses. Four groups are your choice:

| Group | If you leave it behind |
|---|---|
| Leads and lists | You start with empty lists and load leads again |
| Do-not-call lists | The dialer stops skipping the numbers on them |
| Call history and reports | Old reports start empty on the new server |
| Call recordings | Past recordings stay on the old server only |

The recordings the move copies are the MP3 files.

Leaving the do-not-call lists behind is almost always the wrong choice, and the screen says so.

**Stopping the floor.** The same screen lists who is logged in on the old server and which campaigns are active. If you want, it logs the agents out and switches the campaigns off for you. Because that acts on your live server, the screen asks you to type **STOP** first. It is the one thing here that changes the old server.

If the console finds a reason the move cannot run, it says **Not ready yet** and names it. One example is too little free disk on the new server.

## 3. Move

Starting replaces the data on the new server with the data you reviewed. So the console asks twice: you type **WIPE**, press **Start migration**, and then confirm in a dialog that repeats the counts.

Before anything is replaced, the console saves a copy of the new server's database. The move itself only reads your old server's data.

The move then runs in stages:

1. Checking
2. Reading your data
3. Importing
4. Copying prompts
5. Copying recordings
6. Verifying

![A move in progress at Copying recordings: 24,180 of about 40,300 recordings, 41.6 GB, 60%](https://trustane.com/media/b782a70d04bf0373-1600x539.webp "The move shows what has been copied so far")

It keeps running if you leave the page. During the recordings stage the screen shows the files and gigabytes copied so far. It shows no finish time, because the speed of a copy between two hosts cannot be known in advance.

If the recordings copy stops part of the way, **Resume the copy** continues from where it stopped.

## 4. Read the check

When the move is done, the console shows a check for each kind of data: the count on the old server, the count on the new server, and whether they match.

![Migration complete, review counts: eight tables, recordings and prompts with their counts on the source and on this server; users reads 46 and 48 and is highlighted](https://trustane.com/media/45b8a4f2a472bf33-1600x1170.webp "Every count, on both servers")

Below the counts are three more lines:

- **Old addresses left.** The console searches the new server for the old addresses, recording links included, and reports what it finds.
- **Addresses merged here.** How many old servers became this one.
- **Phones renamed and switched off.** Any duplicate extensions from a cluster.

Your recorded prompts are compared file by file, not only counted. Anything you chose to leave behind is marked as left behind by your choice, so it does not read as a fault.

A row that differs is highlighted, and the result then reads **review counts**. The users row normally differs by a few. The new server keeps its own service logins, the ones the console and the lead loader sign in with, in place of any with the same names from the old server.

Small differences in the recordings count are normal if calls were made on the old server during the copy.

## What happens to the old server

Apart from STOP, if you used it, the move only reads the old server, so it keeps its own copy of everything.

If you moved a cluster, the console asks what the old servers become:

- **Drop the cluster configuration.** The new server does everything, and no other server is expected.
- **Keep your old nodes and repoint them here.** The old servers are added back, switched off until each one is pointed at the new database.
- **Replace them with Trustane servers.** This records a request for our support team. Nothing changes on the server.

## What does not move

The new server keeps its own identity. Its server entry, its system settings and its carriers are not replaced by the old server's. In VICIdial each carrier entry is tied to one server's address, so you set up your carriers again on the new server. Your carrier must also send your numbers to the new address, because nothing in VICIdial tells a carrier where to send calls. [The migration checklist](https://trustane.com/blog/vicidial-migration-checklist) lists everything to do before and after the move.

## Next steps

- [VICIdial migration checklist](https://trustane.com/blog/vicidial-migration-checklist): before, during and after the move.
- [What a VICIdial move copies and what it never copies](https://trustane.com/blog/move-vicidial-server-what-to-copy).
- [Add a carrier in the console](https://trustane.com/guides/vicidial-carrier-setup-sip-trunk).
- [Order the server](https://trustane.com/order) your move will go into. The first 7 days are free.

VICIdial is a trademark of its owner. Trustane is an independent hosting provider.
