Migrating from Elastix or Issabel to managed VICIdial
Move from Elastix/Issabel-based dialer setups to managed standard VICIdial.
Elastix and Issabel are Asterisk-based PBX distributions, sometimes used as the platform under VICIdial-style deployments. Migrating to managed VICIdial is straightforward when both run Asterisk under the hood.
What's compatible
- Asterisk dial plan logic (with translation)
- SIP trunk configurations
- DIDs (port them to your new SIP carrier)
- Agent training
What's different
- Elastix/Issabel UI is gone — you use VICIdial admin
- Different management experience (FreePBX-style vs VICIdial-style)
- VICIdial has stronger campaign + dialing features; Elastix/Issabel are PBX-first
Migration steps
1. Inventory
What's running on your Elastix/Issabel box?
- PBX features (extensions, voicemail, IVR)
- Dialer (custom AGI? VICIdial-on-top?)
- Recording
- Reports
2. Decide: full replace or hybrid
If your dialer is the primary use → migrate to VICIdial (we manage). If you need PBX features → keep Elastix for PBX, use VICIdial for outbound dialing only.
3. Export data
mysqldump --single-transaction asterisk > elastix-dump.sql
If you're running VICIdial-on-top, the schemas overlap directly. If pure Elastix, lead data probably lives elsewhere (CRM).
4. Import to VICIfast
For VICIdial-compatible data, restore the dump. For non-VICIdial data, transform to VICIdial's schema (typically lead data in vicidial_list).
5. Port DIDs + reconfigure carrier
Standard SIP carrier reconfiguration on the new box.
6. Test + cutover
Pilot a campaign, verify, then cutover. Keep Elastix running 1 week as fallback.
Time required
Most migrations: 2-5 days. We help free.