VICIfast
Migration program

Migrate from VICIbox.

30-minute cutover. Zero data loss.

Point us at your source box. We dump your vicidial_* tables, rsync your recordings, regenerate your PJSIP carriers, and stand up a fresh managed VICIdial server with everything in place. Nothing on your existing box is modified. You flip DNS when you are ready.
See pricing

Free trial · Your old box stays intact · Nothing is deleted on your source

30 mintypical cutover
< 60sagent downtime
7-dayrollback window
Read-onlyon source box

How it works

Four phases. Nothing on your old box is modified.

  1. PHASE 01

    Point us at your source

    You enter your source box hostname, SSH credentials, and MySQL credentials in the migration screen. We probe via a read-only handshake — no writes, no mutation. The screen lists exactly what we will pull before you approve.

  2. PHASE 02

    The copy (campaigns paused)

    The worker dumps your vicidial_* tables, copies your AGI scripts from /var/lib/asterisk/agi-bin, and syncs /var/spool/asterisk/monitor. Campaigns must be paused and agents logged out before the copy starts — the worker checks and refuses otherwise, so plan a window.

  3. PHASE 03

    Validation pass

    New box stands up. We boot Asterisk + VICIdial against the imported DB. Smoke tests — admin URL reachable, agent login works, a sample disposition writes back to vicidial_log. You preview the new box on a pre-cutover URL before flipping anything.

  4. PHASE 04

    You flip DNS

    When you approve, we update the customer-facing DNS to the new box. Agents see ~30-60 seconds of "redialing" then log back in on the new box at the same URL. The old box stays running for 7 days as your rollback safety net.

Agents keep dialing on the floor while the migration runs in the background
Tima Miroshnichenko / Pexels

What the worker actually runs

Read-only. Your source box stays untouched.

# What the migration worker runs against your source box.
# Read-only. Nothing on your existing dialer is modified.

ssh root@your-vicibox.example.com \
  "mysqldump --single-transaction \
     -u${VARDB_user} -p${VARDB_pass} asterisk \
     vicidial_campaigns vicidial_lists vicidial_users \
     vicidial_list vicidial_log vicidial_closer_log \
     vicidial_inbound_dids vicidial_carriers \
     | gzip" > /tmp/source-dump.sql.gz

rsync -aP --bwlimit=20M \
  root@your-vicibox.example.com:/var/spool/asterisk/monitor/ \
  /var/spool/asterisk/monitor/

rsync -aP \
  root@your-vicibox.example.com:/etc/asterisk/ \
  root@your-vicibox.example.com:/var/lib/asterisk/agi-bin/ \
  /tmp/source-asterisk-conf/
The migration screen shows you the exact commands before you approve them. We never modify your source box; we never write back to it. The worker has read-only credentials.

What stays the same

Everything that matters keeps working.

Same VICIdial version

Your campaigns, lists, leads, users, dispositions and hot keys come across as they are. The new box runs our current build rather than a copy of your old one, so treat the version as ours — the data and the way you work with it are what carry over.

Campaigns, leads, dispositions, reports

Every vicidial_* table moves over — campaigns, lists, leads, statuses, dispositions, callbacks, agent users, custom_<list> tables. Your historical reports keep their continuity; the lead IDs do not rotate. Pre-cutover reports still pull the right data.

Your recordings

We rsync /var/spool/asterisk/monitor in the background. Recordings stay on the new box (or in your own S3 if you set up external backups). Older calls remain searchable from the same VICIdial reports — playback URL just points at the new box.

Your agent logins

Agents log into the same vicidial_admin.php URL on your subdomain. Same username, same password, same hot keys. The only thing they see different is a faster page load.

What changes

Two things, both under your control.

Honest list. These cannot be fully automated and we are not going to pretend otherwise.

Your DNS A record

The dialer URL points to a new IP. You either update your A record to point at the new VICIfast subdomain, or you keep your own hostname and we issue a Let's Encrypt cert for it via DNS-01.

Your carrier's IP whitelist

The new box has a different egress IP. Twilio, Bandwidth, Telnyx, Skyetel, Voxbeam — wherever your trunks live — needs the new IP whitelisted. The migration screen surfaces it as a one-click copy with deep links to each carrier console.

Sources we migrate from

If it speaks VICIdial, we read it.

  • VICIbox (any version since 2014)
  • GoAutoDial
  • VICIhost / managed VICIdial competitors
  • Self-built VICIdial on AWS EC2, DigitalOcean, Linode, custom on-prem
  • Any deployment with a standard vicidial_* MariaDB / MySQL schema
Migrating a self-hosted VICIdial box onto managed infrastructure

30 minutes. Read-only on your old box.

Start the trial; the migration screen walks you through everything. 7-day rollback window if you want to compare. Free if you commit to 6+ months hosting.

FAQ

Migration questions

Stop running VICIbox by hand.

Start the trial. Free for 7 days while you validate. We do the migration; you flip DNS when you are ready.

How fast it deploys