VICIdial to CRM: Zero-Downtime Playbook for 100+ Seats

Last month a 120-seat BPO in Cebu ran its final VICIdial campaign at 10:00 PM local time, flipped a DNS switch, and by 10:05 the same agents were dialing out of Teamcorr—no missed calls, no retraining day, no P&L hit. Here’s how they did it, and how you can too.

Why the urgency?

VICIdial’s TCO creeps up fast. We’ve seen shops spending $8–$12 per seat per month on AWS instances just to keep the MySQL cluster from tipping over during peak dials. Add $2–$3 for the SIP trunk, $1 for the recording storage, and another $1.50 for the third-party reporting tool you bolted on because the built-in dashboards are unusable. That’s $12.50–$17.50 per seat before you even pay the agent. At 100 seats, that’s $15k a year you’re burning on infrastructure instead of margin.

Modern CRMs—Teamcorr included—run $6–$9 all-in, including the softphone, biometrics, and real-time dashboards. The math is simple: switch and you free up $6–$11 per seat per month. Do it right and you don’t lose a single call hour.

The 30-day runway

Break the project into four one-week sprints. Each sprint ends with a live test that doesn’t touch production.

Week 1: Data audit & staging
- Pull a full MySQL dump from VICIdial (usually 2–4 GB for 100k leads).
- Spin up a staging instance of your new CRM on a $40/month DigitalOcean droplet—no need for AWS yet.
- Map fields: VICIdial’s vendor_lead_code → CRM’s external_id, list_id → campaign_id, etc.
- Use Talend Open Studio (free) to clean phone numbers—strip +, 00, 0, and normalize to E.164. We’ve seen 8–12% of leads fail dialing post-migration because of bad formatting.
Week 2: Softphone & carrier test
- Route 5% of your inbound DID to the new CRM via a carrier-side SIP trunk (Twilio, Telnyx, or your existing provider).
- Use the same trunk for outbound test calls—no need to port numbers yet.
- Run a 2-hour side-by-side test with 5 agents: same lead list, same script, same dialer settings. Measure ASR, AHT, and wrap codes. Expect ASR to drop 1–2 points during the first hour as agents adjust to the new UI; it should recover by hour two.
Week 3: Biometrics & compliance sync
- If you’re using fingerprint or facial recognition, install the Teamcorr desktop agent on a test PC and enroll 3–5 agents. Run a 30-minute punch-in/punch-out session and compare timestamps to your current biometric system. We’ve seen clock-in times drift by 30–90 seconds when the NTP server isn’t synced—enough to throw adherence reports off.
- Export a week of VICIdial call logs and import them into the new CRM’s compliance module. Verify that the recording URLs, timestamps, and agent IDs match. If you’re subject to PCI or HIPAA, run a manual audit on 50 random calls to ensure the new system flags sensitive data the same way.
Week 4: Parallel run & cutover
- Run a 24-hour parallel campaign: 10% of leads go to VICIdial, 10% to the new CRM. Use the same dialer settings (drop percentage, max lines, etc.). Compare ASR, AHT, and conversion rates. Expect a 2–4% delta in ASR due to carrier routing differences; anything over 5% means you need to tweak your trunk settings.
- Pick a low-volume hour (usually 2–4 AM local time) for the final cutover. Flip the DNS A record for your carrier’s SIP trunk to point to the new CRM. Keep the old VICIdial instance running for 48 hours as a hot standby—just in case.

Carrier & SIP checklist

Task	Tool	Time	Risk if skipped
Port 1–2 test DIDs	Carrier portal	1–2 hrs	Inbound calls fail post-cutover
Test SIP trunk failover	SIPp or manual call	30 min	Downtime during carrier outage
Verify E.164 formatting	Talend Open Studio	2 hrs	8–12% of leads fail dialing
Sync NTP servers	Chrony or NTPd	15 min	Adherence reports drift 30–90 sec
Test recording storage	AWS S3 CLI	1 hr	Compliance audit fails

Agent onboarding that doesn’t kill your schedule

We’ve watched teams try to train 100+ agents in a single 4-hour session. It never works. Instead, use a 3-day micro-learning sequence:

Day 1 (30 min): Softphone only. Agents make 10 test calls using the new dialer. Focus on mute, hold, transfer, and disposition codes. Record a 5-minute Loom video showing the exact steps and send it to agents 24 hours before the session.
Day 2 (20 min): CRM basics. Show the lead card, notes field, and how to log a callback. Run a 10-lead mini-campaign with a $5 gift card for the first agent to convert 3 leads.
Day 3 (15 min): Biometrics & adherence. Agents punch in/out 3 times and verify their timestamps in the real-time dashboard. Use a shared Google Sheet to track who’s completed the drill.

Total training time: 65 minutes per agent. We’ve seen adoption hit 95% within 48 hours using this method—no retraining day, no overtime.

Real-time dashboards you actually use

VICIdial’s dashboards are static HTML pages that refresh every 60 seconds. Modern CRMs push updates every 1–2 seconds. Here’s what to monitor during the first 72 hours post-cutover:

ASR delta: Compare the new CRM’s ASR to your VICIdial baseline. Expect a 1–2 point drop in the first hour; it should recover by hour two. If it doesn’t, check your carrier’s SIP trunk settings—most ASR drops post-migration are carrier routing issues, not CRM issues.
AHT delta: Measure AHT for the same campaign pre- and post-cutover. We’ve seen AHT drop 3–5% in the first week as agents adjust to the new UI. If AHT spikes over 10%, you’ve got a training gap—pull 5 random call recordings and audit the agent’s screen flow.
Adherence drift: Compare the new CRM’s adherence reports to your VICIdial logs. Expect a 1–2% delta due to timestamp rounding. If the delta is over 3%, check your NTP server sync—adherence reports are useless if the clocks are off.

“We cut over 120 seats at 10 PM on a Tuesday. By 10:15, ASR was back to baseline, AHT was down 4%, and we saved $11 per seat per month. The only thing we missed was the NTP sync—adherence reports were off by 45 seconds for the first 24 hours.”

— Operations Manager, 120-seat BPO, Cebu

What to keep from VICIdial

Don’t throw out everything. Here’s what we recommend keeping:

Lead lists: Export your VICIdial lists as CSV and re-import them into the new CRM. Use the vendor_lead_code field to maintain continuity with your lead vendor.
Call recordings: Keep your VICIdial recording storage running for 90 days post-cutover. Use AWS S3 lifecycle rules to archive recordings older than 90 days to Glacier—cheaper than keeping them in hot storage.
Carrier contracts: Don’t port your numbers until you’re sure the new CRM is stable. Keep your VICIdial SIP trunk active for 30 days post-cutover as a hot standby.

Post-cutover checklist

Run a 24-hour parallel campaign with 5% of leads to verify ASR, AHT, and conversion rates.
Audit 50 random call recordings to ensure compliance flags match your VICIdial logs.
Sync NTP servers to ensure adherence reports are accurate.
Port your remaining DIDs to the new CRM.
Decommission your VICIdial instance after 30 days—no need to keep it running longer than that.

Migrating off VICIdial isn’t about the technology—it’s about the plan. Follow this 30-day runway, and you’ll keep dial tone live, agents productive, and your P&L intact.

Ready to run the numbers? See Teamcorr’s pricing or book a 15-minute demo to walk through your exact setup.