Rebuilding CRM integrations after migrating to VICIdial

One of the quiet costs of migrating from a cloud dialer to VICIdial is that the CRM integration you relied on does not come with you. Cloud dialers bundle native connectors to Salesforce, HubSpot, and similar platforms as part of the subscription. Those connectors write disposition outcomes, call notes, and Call recording links back to contact records automatically.

VICIdial does not include native CRM connectors out of the box. What it does include is an open API — the Agent API — that exposes call events, Disposition updates, and Lead data in real time. That surface is what you build your integration on. The work is real, but it is bounded, and most teams underestimate how much of it they can defer past cutover.

Before scoping the rebuild, review the complete VICIdial migration guide to understand where integration rebuild fits in the overall migration sequence.

Audit what the old integration actually did

Before writing any code, document every flow your current dialer-to-CRM integration performs. Common ones:

• Screen pop: when a call connects, a CRM contact record opens in the agent browser.
• Disposition writeback: when the agent selects a call outcome, it posts to the CRM as an activity or lead status change.
• Recording link: the CRM activity record receives a URL to the call recording.
• Lead sync: new CRM leads are automatically pushed into the dialer list.

Rank these by business impact. Screen pop and disposition writeback usually matter most. Recording link and lead sync can often be deferred or done manually during the transition window. Write down the exact CRM fields each flow touches — many teams discover the old connector was quietly updating a custom field that nobody tracked, and missing it shows up as a broken report weeks later.

How VICIdial exposes data for integrations

VICIdial's AGI (Asterisk Gateway Interface) scripts run at call events (answer, hangup, disposition) and can call external URLs. The Agent API is a URL-based interface that accepts commands and returns call state. Combined, these two surfaces let you build most integration flows without modifying VICIdial's core code. A small middleware service usually sits between them and your CRM, translating VICIdial events into CRM API calls and handling retries when the CRM is briefly unavailable.

Screen pop is typically handled through VICIdial's custom fields and the script URL feature — when a Lead is dialed, VICIdial can open a URL in the agent's browser with the lead ID appended. Your CRM receives that ID and pulls up the matching record. Because the URL is built from lead fields, you can pass whatever identifier your CRM keys on, not just the phone number.

Integration rebuild flow

flowchart TD
    A[Audit current integration flows] --> B[Rank by business impact]
    B --> C[Screen pop and disposition writeback first]
    C --> D[Map VICIdial AGI events to CRM API calls]
    D --> E[Build and test on staging campaign]
    E --> F[Verify disposition writeback with real calls]
    F --> G[Add recording link once core flows are stable]
    G --> H[Automate lead sync last]

Test against a staging campaign first

Build the integration against a small test Campaign with a handful of internal phone numbers, not your live lead lists. Place real calls to your own phones, disposition them, and confirm each outcome lands in the CRM with the right fields populated. This catches the small mismatches — a status code that does not map, a timestamp in the wrong time zone — before they reach production data.

Realistic timeline

A screen pop and disposition writeback to a mature CRM API (Salesforce, HubSpot) typically takes a developer one to two weeks to build and test, assuming the CRM API is already familiar. Platforms with a thinner API surface or unusual data models take longer.

If the integration is not ready by cutover day, plan for manual disposition logging during the gap window. It is tedious, but it keeps the CRM accurate while the integration catches up. This connects directly to your cutover sequencing — see the migration cutover plan for how to sequence these dependencies.

To have a VICIdial server ready to build against before your integration work starts, see VICIfast managed plans — the server is ready in under 40 seconds, giving you a real environment to develop against from day one.