Migrations
Migrations
Detailed guides for moving an existing VICIdial install to us. Most teams complete the migration in under a day with zero downtime. We help free.
Migrating from a ViciBox install
What the automated ViciBox migration actually moves, what it leaves on the old box, what you rebuild by hand, and the cutover window you should book.
Migrating a self-hosted VICIdial box
Moving your own VICIdial box onto managed hosting: what carries over unchanged, what the new box does differently, and where the real work sits.
Moving from Five9 to managed VICIdial
Five9 keeps recordings 30 days and offloads them forward-only, so set that up first. What exports, what you rebuild, and the order to work in.
Migrating from GOautodial
GOautodial runs on VICIdial's own tables, so the data move is standard. What you actually lose is the interface and the REST API, not the data.
Genesys Cloud CX to managed VICIdial
What Genesys Cloud actually exports, what you rebuild by hand, and the billable 30-day data-retrieval window their contract makes you ask for.
Moving from Aircall to managed VICIdial
Port your numbers before you cancel, get your contacts and recordings out while you still can, and rebuild the dialing side on managed VICIdial.
Moving from 3CX to managed VICIdial
With 3CX you usually own the trunk, so there is often no port. What transfers, what you rebuild, and why most teams keep 3CX for the PBX side.
Migrating from Issabel or Elastix
Moving off an Issabel or Elastix box is a rebuild, not a data move, and you are probably changing dialing model at the same time. What that involves.