Migrating from GoAutoDial to managed VICIdial

Move from GoAutoDial (GAD) to standard managed VICIdial. Schema mapping, fork differences.

GoAutoDial is a fork of VICIdial. Migrating involves schema mapping because the forks have diverged.

What's compatible

Lead data (vicidial_list rows)
Agent users
Most disposition codes
Recordings (file format is the same)

What's different

Some custom GAD tables don't exist in standard VICIdial
GAD's UI customizations are GAD-only
Some GAD-specific dial-plan additions need translation

Migration steps

1. Export lead data

mysqldump --single-transaction asterisk \
  vicidial_list vicidial_users vicidial_campaigns vicidial_lists \
  vicidial_inbound_groups > gad-export.sql

(Some table names may differ in GAD — verify with SHOW TABLES.)

2. Restore on VICIdial server

After ordering your VICIfast server, copy + restore the dump. The schema overlap is ~80% — most data lands cleanly. The 20% delta is GAD-specific tables we can ignore.

3. Recreate campaigns

Campaign settings don't transfer — too many forked-feature dependencies. Rebuild manually in VICIdial admin.

4. Rebuild custom dispositions

Map GAD-specific dispositions to VICIdial codes. Usually a Sunday afternoon's work for someone who knows the campaigns.

5. Re-attach recordings

Copy /var/spool/asterisk/monitorDONE from GAD to VICIdial, same path. Recording playback works without further config.

6. Test campaigns

One agent, one test list, one test phone. Verify:

Outbound calls connect
Recording lands in monitorDONE
Agent disposition saves to VICIdial properly
Reports show the call

Time required

Most migrations take 1-2 days end-to-end. We help free.

When NOT to migrate

If you're deeply invested in GAD-specific features (e.g. their reporting UI, custom AGI scripts), evaluate whether the move is worth it. For most operators, standard VICIdial's broader documentation + community wins long-term.