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. Your existing box keeps dialing the whole time. You flip DNS when you are ready.
See pricing

Free trial · Old box keeps dialing · 7-day rollback safety net

migration worker
00:00$ ssh root@vicibox.example.com
00:02$ mysqldump asterisk vicidial_* | gzip
00:07✓ db dumped · 1.2 GB · 47 tables
00:09$ rsync /var/spool/asterisk/monitor/
14:22✓ recordings synced · 487 GB · 142,381 files
14:24$ rsync /etc/asterisk /var/lib/asterisk/agi-bin
14:26✓ AGI scripts + conf transferred
14:27$ vicifast-restore --target=acme.vicifast.io
28:14✓ new box ACTIVE · admin reachable
28:14⏸ awaiting DNS cutover approval…
30 mintypical cutover
< 60sagent downtime
7-dayrollback window
Read-onlyon source box

How it works

Four phases. Your old box never stops dialing.

  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

    Background copy (old box keeps dialing)

    The worker dumps every vicidial_* table, rsyncs your /var/spool/asterisk/monitor and /etc/asterisk + /var/lib/asterisk/agi-bin, regenerates PJSIP carrier configs from your vicidial_carriers rows. Your live box never stops dialing during this phase.

  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.

What the worker actually runs

Read-only. Your source box stays untouched.

# What the migration worker runs against your source box.
# Read-only. Your existing dialer never stops dialing.

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

We do not force-upgrade. If you are on 2.14, the new box runs 2.14. Your campaigns load the same way, your hot keys press the same keys, your reports read the same columns. We can upgrade post-migration; you opt in.

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

30 minutes. Old box never stops dialing.

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