VICIfast
Migration

Migrate from ViciBox.

Free on every plan.

Point the migration tool at your old server. It copies your VICIdial database and your own AGI scripts onto your new VICIfast server, then your recordings in the background. Nothing on the old server is changed. You add your carrier trunks and switch campaigns on when you are ready.
See pricing

Migration tool on every plan · Nothing changed on your old server · White-glove option $499

$0on every plan
Read-onlyon your old server
Minutesdatabase copy
$499if we run it for you

How it works

Four steps. Nothing on your old server is changed.

  1. STEP 01

    Connect your old server

    On your new server’s page, click Migrate from ViciBox and enter the old server’s address, SSH port and user. Paste the one-time key it shows into that server’s authorized_keys. A read-only probe lists every table and row count it will copy before anything moves.

  2. STEP 02

    Pause, then copy

    Pause every campaign and log your agents out on the old server: the copy refuses to start otherwise. Your new server pulls the VICIdial database and your own AGI scripts over SSH and restores them. In the migrations we have run, that took from under a minute to about 12 minutes.

  3. STEP 03

    Recordings follow

    Once the database is in place, your recordings and voicemail sync in the background. Set a bandwidth cap if that link also carries calls. About 30 GB has taken us roughly 18 minutes; your old server’s upload speed decides yours.

  4. STEP 04

    Switch over

    Add your carrier trunks on the Trunks tab, allow the new server’s IP at your carrier and point your agents at the new address. Campaigns arrive paused: switch them on when a test call goes through. Your old server is untouched, so it stays your fallback.

What stays the same

Your data, and the way you work with it.

Campaigns, lists and leads

The whole VICIdial database comes across apart from what belongs to the old machine: its server entries, carriers, system settings and live-call tables. Campaigns, lists, leads, statuses, callbacks, users and custom_ list tables keep their IDs.

Your call history

vicidial_log, vicidial_closer_log and recording_log move with the lead IDs intact, so reports from before the move still pull the right rows, with the same campaign IDs, statuses and agent usernames.

Your recordings

Copied to the new server after the database, and playable from the dashboard’s Recording search. Links inside VICIdial’s own reports still point at the old server’s address.

Your agent logins

Agents keep their user IDs and passwords and sign in at the new server’s address, or at your own domain once it points there. The new server keeps its own 6666 admin login.

What changes

Three things you set up yourself.

They belong to the old machine, so the tool leaves them to you.

Your dialer’s address

The new server has its own address. Send agents there, or put the server on your own domain with a CNAME record at your DNS provider; we issue its certificate.

Your carrier's IP allow-list

The new server has a different IP address. Add it at your carrier (Twilio, Telnyx or whoever carries your calls) before you switch campaigns on.

Your carrier trunks

Carrier settings are not copied: the source box has its own IPs and paths baked into them. Add your trunks on the new server from the Trunks tab before cutover.

What your old server needs

If it runs stock VICIdial, the tool can read it.

  • ViciBox, or any VICIdial install with its standard MariaDB / MySQL database
  • A root-level SSH login to the old server that your new server can reach
  • Asterisk, VICIdial’s install files and /etc/astguiclient.conf in their usual places
  • 10 GB free in /var/tmp on the old server
Migrating a self-hosted VICIdial box onto managed infrastructure

Free on every plan. Read-only on your old server.

Order a server or start the trial, then click Migrate from ViciBox on its page. Want us to do it? Add the White-glove migration ($499, one-time) from Manage addons.

FAQ

Migration questions

The migration tool is free on every plan, with no commitment. If you would rather we run the move, check every list, campaign and in-group against your old server and sit with your first shift, add the White-glove migration: a one-time $499 add-on that any plan can take.

No. Every vicidial_log, vicidial_closer_log, recording_log, and call-history table moves over with the lead IDs intact. Reports from before the cutover keep working - same lead IDs, same disposition codes, same campaign IDs, same agent usernames.

Yes. Once the database is restored, your recordings and voicemail sync in the background over SSH. It runs at full speed unless you set a bandwidth cap on the migration screen. In our runs about 30 GB took around 18 minutes and 71 GB about 38 minutes; your old server’s upload speed decides yours.

From when you pause campaigns on the old server until you switch them on at the new one. That is the database copy (under a minute to about 12 minutes in our runs, depending on its size) plus the time you take to add trunks and update your carrier. Recordings sync afterwards and do not hold you up. Most teams move outside calling hours.

No. It is the same VICIdial agent screen and admin pages, with the same campaigns, users and hot keys. Agents sign in at the new server’s address.

The tool copies your own agi-*.agi scripts from /var/lib/asterisk/agi-bin; the stock ones come with the new server. It does not copy /etc/asterisk - the new server has its own generated Asterisk config, and overwriting it would break the dialer. If your scripts read files outside the standard paths, copy those across yourself.

It reads your data and changes none of it. It adds a one-time key to root’s authorized_keys, removed again after the recordings sync, and writes an error log to /tmp during the copy.

Your old server keeps everything it had. If the copy fails or something looks wrong on the new server, switch your campaigns back on at the old one and carry on there while you retry.

Any server running VICIdial with its standard database, such as ViciBox or a self-built install. The probe checks first that it can log in as root over SSH and finds Asterisk, /etc/astguiclient.conf and 10 GB free in /var/tmp. A host that does not give you root access cannot be read this way.

Anything that calls VICIdial or reads its database needs the new server’s address; the API users and campaign webhook settings come across with the database. Port 3306 is closed to the internet, so a tool that reads MariaDB directly connects through an SSH tunnel with a read-only login.

Stop running ViciBox by hand.

Start the 7-day trial and run the migration tool on it. Switch over when your trunks are in and a test call goes through.