Genesys Cloud CX to managed VICIdial

Moving off Genesys Cloud CX is a rebuild, not a data migration. Genesys exports your data in Genesys-shaped formats; nothing on either side converts a Genesys org into a VICIdial box. Budget for re-creating your configuration by hand and you will not be surprised.

Still deciding rather than planning? The VICIfast vs Genesys Cloud CX comparison is the head-to-head, including the parts where Genesys wins outright - their bring-your-own-carrier support is genuinely good and outbound campaigns are included in every published tier.

Start the clock on your contract, not your build

Do this before any technical work. The Genesys Cloud Services Agreement (§10.4.2, "Retrieval of Customer Data") states that if you need more time to retrieve your data after termination, you "may request, and Genesys will grant, a 30-day extension to the Subscription Term" - but only if the request is made "on or prior to the termination date," and "during the extended period, Customer will be charged for its usage."

Three consequences worth planning around: the window is not automatic, it closes the moment you pass your termination date without asking, and it is billable. Get your export requirements agreed in writing before you give notice.

EU customers get more under the Data Act addendum Genesys publishes alongside the agreement - a data-retrieval period of at least 30 days, and a termination notice period capped at two months. That addendum also defines "Exportable Data" so as to exclude anything protected by Genesys' or a third party's intellectual property rights, which is the contractual reason configuration comes out in Genesys' own formats rather than a neutral one.

What genuinely exports

Contact lists - yes, as CSV, and more easily than most guides suggest. Genesys documents an Export button under Outbound → List Management → Contact Lists; the export is asynchronous and lands a comma-separated file in your browser's download folder. It needs the Outbound Contactlist View and Outbound Contact View permissions. There is a matching API pair - a POST to start the export and a GET to fetch the resulting URI.

Genesys documents the ceilings on the lists themselves: one million contacts per list, five million per org, 50 columns per list and 10 phone-number columns. We could not find a documented row cap on the export operation itself, so treat a very large list as something to test rather than assume.

Interaction and call history - yes, with real caps. View exports come out as CSV or PDF, up to one million rows. The catch is recency: Genesys limits exports of interactions less than 24 hours old to 10,000 conversations per 12-hour period, because that data comes from a real-time store "not tailored towards bulk retrieval." Older interactions get the full million-per-export allowance. If an export exceeds the limit you get partial data plus a timestamp marking how far it reached, so check the tail of every file. PDF exports cap at 150 columns; CSV does not.

Recordings - possible, but plan it, don't improvise it. There is no single "download my recordings" button, and there are two different mechanisms that are easy to confuse:

• The AWS S3 recording bulk actions integration is the real bulk path. It exports recordings, screen recordings, attachments and metadata into an S3 bucket you own, under an IAM role you configure. Files land in a dated path per conversation with a metadata sidecar. Archived recordings can be exported without restoring, but a batch download of archived recordings requires restoring them first.
• The batch download request API is a different thing with a hard limit: Genesys documents a maximum of 100 items per request, and the signed URLs it returns are valid for 60 minutes by default and 60 minutes at most. That is a slow instrument for a large archive.

Retention is policy-driven rather than a fixed number. Genesys states that your quality-management policy's retention period determines how long recording files are kept, and that voice and digital recordings have "no maximum or minimum limit" while screen recordings cap at one year. Do not assume a default - read your own policy, because that is the only thing that tells you how much history still exists.

What does not transfer

Configuration. Genesys does export it, and none of it is loadable anywhere else. Their own retention table names the mechanisms: configuration objects come out through CX as Code as Terraform, Architect call flows export as YAML or as a .i3flow file, and user records come out as JSON over SCIM.

The honest reading is Genesys' own warning about Architect flows: moving a flow between two Genesys orgs "loses all mappings to queues, data actions, and more," and you must remap them manually. If a flow does not survive a move between two Genesys tenants intact, it is not going to become a VICIdial in-group. Treat these exports as documentation of what you built - genuinely useful when someone has to rebuild it - not as something importable.

You are also unbundling a suite. Workforce management, quality management, speech analytics and Genesys' AI features have no VICIdial equivalent. Replacements exist and sell standalone, but they are separate procurements, separate invoices and separate integrations that you now own.

What you rebuild

All of it, and this is the part that decides your timeline. On the VICIfast side these are dashboard screens rather than config files, which helps, but somebody still has to make every decision again:

• Campaigns, dial method and pacing, plus recycle and retry rules
• Lists, custom lead fields and their mapping
• Dispositions, mapped from your Genesys wrap-up codes
• In-groups and call menus, replacing queues and Architect flows
• DIDs and inbound routing
• Trunks - your carrier, configured against the new box's IP
• Caller-ID groups, agents, user groups, and calling windows and holidays

Leads load through the dashboard's CSV importer. It takes CSV only, up to roughly 500,000 rows per file, maps your columns onto VICIdial's lead fields, and needs at minimum a phone number and a last name. It has dedupe scoping, a DNC mode that either skips or flags matches, timezone assignment from area code or postal code, a downloadable error report and a ten-minute undo. Plan on more than one pass.

One thing to be clear about: our automated migration reads a standard VICIdial database over SSH. It cannot read a Genesys org, and no tool of ours can. Anyone who tells you a CCaaS tenant can be automatically converted is describing something that does not exist.

The order to do it in

1. Agree the export scope in writing and confirm the retrieval window before you give notice.
2. Configure the S3 recording export early and let it run. This is the item most likely to run out of time.
3. Export contact lists and interaction history, in date-bounded chunks, and verify row counts against what the reports say.
4. Export your configuration through CX as Code and Architect - as the reference document for the rebuild.
5. Provision the VICIfast server and connect your carrier. Genesys supports BYOC, so if you already bring your own carrier this is an allowlist and routing change rather than a port.
6. Rebuild campaigns, in-groups, dispositions and users; import a single pilot list.
7. Run a pilot campaign in parallel while Genesys still carries production.
8. Migrate campaign by campaign, priority order, both systems live.
9. Cut over, then cancel - in that order, and only once the export you paid for is verified on your own storage.

For an enterprise floor, six to twelve weeks is a realistic span, and most of it is rebuild and change management rather than data movement.

What to test before cutover

• A full outbound call on each trunk, and inbound on each ported or re-routed DID
• Every disposition writing back correctly, including the ones your reporting depends on
• Calling windows and per-state rules, with timezone assignment spot-checked against known leads
• DNC scrubbing on a list you have deliberately seeded with a suppressed number
• Recording capture, storage location and playback
• Agent login, transfers and the closer path
• That your exported recordings are readable from your own bucket - before the contract ends, not after

Cost, honestly

Genesys publishes four tiers at $75, $115, $155 and $240 per user per month billed annually, with outbound campaigns listed as included on all four. VICIfast bills per server. At 100 agents the gap is large in either direction you cut it, but how large depends entirely on which tier you are on - and the comparison is not like-for-like, because the workforce-management and analytics tools bundled into the higher Genesys tiers become separate purchases on your side. Model those before you sign anything. The full breakdown is on the comparison page, and the plan grid is at pricing.

Genesys also documents that at least 15 agents are recommended for predictive and power campaigns. That is a recommendation in their outbound documentation, not a contractual seat minimum - worth knowing if a smaller floor is part of why you are moving.

Next steps

• VICIfast vs Genesys Cloud CX - published per-user pricing, their BYOC terms, and where Genesys wins.
• VICIfast pricing - the plan grid this migration lands on, billed per server.
• Start a 7-day trial - card validated, nothing charged until day 7. Worth standing a box up early so the rebuild has somewhere to land.

Want a second pair of eyes on the plan? Talk to us - scoping help costs nothing. A done-for-you migration is a paid onboarding add-on, and it is included free on the top plans.