VICIfast
All migrations

Migrating from self-hosted VICIdial

How to move from a self-hosted box to managed VICIfast hosting.

Self-hosted migrations are usually the cleanest because you have full control of both ends.

Pre-migration checklist

  • [ ] VICIdial version match — or newer compatible. We ship 22.5.1 currently.
  • [ ] OS — your box is probably Ubuntu 18/20/22 or CentOS/Rocky. We're on Ubuntu 22. Schema is OS-agnostic.
  • [ ] Disk usage — check recordings size. Add the volume addon to your VICIfast plan if needed.
  • [ ] Custom code — anything you've patched into VICIdial source needs to be re-applied or replaced.

Database migration

Standard mysqldump + scp + restore. See the Vicibox migration for the commands; they apply identically.

Asterisk config

Copy your custom configs:

# On the old box
cd /etc/asterisk
tar czf /tmp/asterisk-config.tar.gz extensions_custom.conf sip_custom.conf manager_custom.conf

Don't copy extensions-vicidial.conf or sip-vicidial.conf — those are auto-generated from the database.

Custom dial plan + AGI

Anything in /usr/share/astguiclient/ that you've added (custom AGI scripts, custom hot-key handlers):

tar czf /tmp/custom-agi.tar.gz /usr/share/astguiclient/custom_*

Drop these on the VICIfast box at the same path.

DIDs + carrier

Your DIDs stay with your carrier. Update the IP allowlist + you're done.

Cutover

Two strategies:

Hard cutover — all-at-once, accepts ~10 min of "transition" downtime:

  1. Stop dialing on old box
  2. Final DB dump
  3. Restore on new box
  4. Update DNS
  5. Resume dialing on new box

Soft cutover — zero downtime, more work:

  1. Get new box running with a recent backup
  2. Run a few non-critical campaigns on new box
  3. Verify everything works
  4. Schedule a 30-min maintenance window
  5. Final dump + restore
  6. Update DNS
  7. Resume

We recommend soft cutover for production.

Need a hand?

Migration assistance is free — open a ticket once your VICIfast account is up and we'll help.