VICIfast
Guides & tutorials

How to migrate from Vonage Contact Center to VICIdial

Vonage Contact Center (formerly NewVoiceMedia) combines CRM-native routing with a contact center platform, but licensing costs and Salesforce dependency drive teams to look for alternatives. This guide covers the migration path to VICIdial.

VICIfast Support
··3 min read
Servers in a data centre — illustration for: How to migrate from Vonage Contact Center to VICIdial
Photo by panumas nikhomkhai on Pexels

Vonage Contact Center (VCC), originally NewVoiceMedia, built its reputation on tight Salesforce CRM integration - routing calls based on CRM data, logging activity automatically, and surfacing customer context on the agent screen. It works well when Salesforce is the center of your operation. The friction appears when teams without a deep Salesforce investment are paying VCC's licensing to get features they could get from a standalone dialer at a fraction of the cost.

The full migration framework is in our complete guide to migrating to VICIdial. This post covers what is specific to a Vonage Contact Center migration.

Why teams leave Vonage Contact Center

VCC pricing is per-agent-seat plus a platform fee. For teams that moved away from Salesforce or never used it heavily, the CRM integration advantage disappears and the cost-per-seat is hard to justify. Outbound campaigns in VCC are functional but the Predictive dialing controls are less granular than VICIdial's - you have less visibility into the Hopper fill rate and [[dial-level]] adjustments are not as fine-grained.

Exporting from Vonage Contact Center

VCC stores data in two places: inside VCC's own platform (recordings, routing config, agent data) and inside Salesforce (leads, contacts, activity history). Make sure you export from both before the subscription ends.

  • Recordings - VCC uses Amazon S3-backed storage. Use the Vonage API or bulk export request via support. Recordings tied to Salesforce call logs have a reference URL in the activity object.
  • Lead and contact data - export from Salesforce Leads and Contacts objects as CSV. Include custom fields and the call disposition history from Salesforce activity records.
  • DNC list - VCC does not maintain a standalone DNC (do not call) list; suppression is handled via Salesforce Do Not Call fields. Export contacts with Do Not Call = true and import them into VICIdial's DNC system.
  • Phone numbers (DID (direct inward dialing)) - initiate port requests with VCC support. Vonage typically uses Bandwidth or Level3 as the underlying carrier, so LOA-based ports work normally.

Rebuilding VCC routing in VICIdial

VCC's interaction plans (routing logic) define how inbound calls flow through IVR menus, queue into skill-based groups, and reach agents. In VICIdial, inbound routing uses Ingroup objects with optional IVR front-ends. Document each VCC interaction plan: entry DID, menu options, queue behavior, and overflow rules. Build a matching ingroup for each queue, then wire the DIDs to those ingroups in VICIdial's phone configuration.

Outbound campaigns map more directly: a VCC outbound calling list becomes a VICIdial Lead list loaded into a Campaign. Map VCC's call result codes to VICIdial Disposition statuses before loading the leads so agents have the right options from day one.

VCC to VICIdial cutover flow

flowchart TD
    A[Export Salesforce contacts and DNC] --> B[Export VCC recordings]
    B --> C[Document VCC interaction plans]
    C --> D[Build VICIdial ingroups and campaigns]
    D --> E[Load leads and DNC into VICIdial]
    E --> F[Configure SIP trunk]
    F --> G[Agent training]
    G --> H[Parallel run validation]
    H --> I[Port DIDs to new carrier]
    I --> J[Update Salesforce CTI to VICIdial API]
    J --> K[Cancel VCC subscription]

CRM integration after the move

VCC's Salesforce integration was one of its main selling points. VICIdial has a CRM URL field on each campaign that can open a CRM record in a browser tab when the call connects. For deeper Salesforce write-back (logging calls, updating contact records), you wire up VICIdial's URL callback or AMI events to a small middleware layer. It requires custom work but it is not unusual - many teams run VICIdial alongside Salesforce this way.

For reporting continuity during the transition, see bridging the reporting gap during a VICIdial migration.

VICIfast gets a secured VICIdial server running on a dedicated VPS in under 40 seconds, so you can start building your configuration before the VCC export is even complete. See VICIfast managed plans for sizing and pricing.

About VICIfast

We run VICIdial servers for call centres, so you don’t have to. You get the dialer set up, secured and kept running — we handle the server, the updates and the backups. Bring your own phone carrier at no markup, or use VICIfast Voice, our own US calling and numbers, from $0.0085 a minute. From $49 a month per server.

Questions? Call +1 636 556 0022 and talk to someone who runs dialers.

Citing this article

VICIfast Engineering. “How to migrate from Vonage Contact Center to VICIdial”. VICIfast LLC, June 29, 2026. Retrieved from https://vicifast.com/blog/migrate-vonage-to-vicidial

Have questions?

Related posts

You might be interested in

Comments

Comments are reviewed before they appear. We never publish your email.

No comments yet - be the first.