How to migrate from NICE CXone to VICIdial

NICE CXone (formerly inContact) is a full enterprise contact center suite: ACD, IVR (interactive voice response) routing, workforce management, quality management, analytics, and outbound dialing in a single platform. It is powerful and expensive. When a team decides to migrate away - usually because the contract value no longer maps to what they actually use - the scope of the migration work is larger than most SMB platform moves. This guide is realistic about that scope.

Start with the full framework in our complete guide to migrating to VICIdial. This post covers NICE CXone-specific considerations.

Why teams leave NICE CXone

CXone licensing is modular and per-seat, and the modules add up quickly. Teams often find that after contract negotiations, they are paying for workforce management and quality modules they only partially use. When the operation is primarily outbound dialing and the core need is a reliable Predictive dialing engine with flexible Campaign controls, VICIdial provides that without the enterprise platform overhead. The other common driver is data control: CXone stores everything in NICE's cloud, whereas VICIdial on a dedicated server keeps Call recording files and Lead data on your host.

What to export from CXone

CXone's data is spread across several modules. Allow two to four weeks for a full export, especially for recordings at scale:

• Contact records and Lead list data - export from CXone's Contacts section or via the Data Extract API. Include all custom CRM fields your team uses.
• Recordings - CXone stores recordings in its own cloud. Bulk export via the Recording Download API or request a media export from NICE support. Recordings are deleted after contract end, often within 30 days, so start this immediately.
• DNC and suppression lists - CXone manages DNC list compliance internally. Export all suppression lists from the Compliance module.
• Studio scripts (IVR flows) - CXone's Studio flow designer uses a proprietary format. Document each flow manually: the entry DID (direct inward dialing), menu options, branching logic, queue behavior, and overflow routing.
• Agent skills and routing profiles - export agent lists, skill assignments, and proficiency levels from CXone's ACD configuration.

Rebuilding CXone routing in VICIdial

This is the hardest part of any CXone migration. CXone's Studio is a visual flow builder that handles IVR, skills-based routing, callbacks, and conditional branching. VICIdial handles inbound routing through Ingroup queues and AGI-based dialplan scripts. You cannot import CXone Studio flows - you must rebuild each flow's logic manually.

Prioritize your highest-volume inbound queues first. For each queue, create a VICIdial ingroup with matching hours, hold music, and overflow handling. Assign agents to ingroups with the appropriate rank. Simple skills-based routing (route call to first available agent in skill group) translates directly. Advanced proficiency-based routing requires more configuration work.

Phased cutover for enterprise migrations

flowchart TD
    A[Audit all CXone queues and Studio flows] --> B[Export contacts, DNC, recordings]
    B --> C[Phase 1: Rebuild top-3 inbound queues in VICIdial]
    C --> D[Phase 1 cutover: port DIDs for those queues]
    D --> E[Phase 2: Rebuild remaining inbound queues]
    E --> F[Phase 2 cutover: remaining inbound]
    F --> G[Phase 3: Migrate outbound campaigns]
    G --> H[Validate reporting and QA workflows]
    H --> I[Cancel CXone contract]

A phased approach reduces risk significantly. Migrate one or two queues at a time, validate call quality and disposition rates, then move the next group. This extends the dual-platform period but prevents a single large cutover failure from taking down the whole operation.

Outbound campaigns and Disposition mapping

CXone's outbound dialer uses Skill-based campaigns with contact lists. These map to VICIdial campaigns with Lead list assignments. CXone disposition codes (call result categories) map to VICIdial Status (lead status) codes. Build the full disposition map before any agent starts taking calls on VICIdial. For a systematic approach to that mapping, see mapping dispositions during a VICIdial migration.

Getting the VICIdial server ready

A CXone migration already demands significant planning and rebuilding effort. Adding a VICIdial server install to that workload is avoidable. VICIfast provisions a secured, dedicated VICIdial server in under 40 seconds - you get full admin access, a branded subdomain over HTTPS, and a configured Asterisk instance. Bring your own SIP carrier and start loading your migrated data the same day you provision.

See VICIfast managed plans to choose a server size appropriate for your agent count before starting the CXone export process.