Quick answer: A Genesys Cloud CX migration onto Devotel Orbit follows the per-family swap pattern proven on the enterprise CCaaS runbook, ordered so connectivity crosses first and the customer profile layer crosses last: port phone numbers in staged waves, re-verify the WhatsApp WABA, re-author contact-center queues against the Orbit ACD, move verify (OTP) flows last because they carry the hardest idempotency constraints, and cut the CDP over as its own workstream with identity-resolution rules mapped field by field. The Orbit vs Genesys matrix and the best Genesys alternatives round-up covered the comparison; this is the execution.
The audience is operations and platform leads who already accept the comparison outcome. Genesys Cloud CX prices per seat on annual contracts, sells through a sales cycle, and splits the rest of the communications stack across separate Twilio or SendGrid accounts plus a CDP it only re-announced as a platform-level capability this year. On Orbit those three procurement facts invert: published usage-based pricing, self-serve signup, and the contact center, messaging, and customer data layer on one pay-as-you-go wallet.
Step 1: the trigger audit before any port window
The comparison and the migration scope are decided on the same inventory. Before any porting paperwork, export from the Genesys admin console:
- Every queue in the ACD with its routing method, skills, SLA targets, and overflow or fallback destination. One exported queue row becomes one queue to re-author on Orbit; a queue nobody answers shows up in this audit, not halfway through the rebuild.
- The full IVR call-flow inventory: menu trees, prompts, business-hours routing, holiday schedules, and every node's destination. Map each node to an outcome (queue, announcement, voicemail, hang-up) so the rebuilt IVR reproduces the routing contract node for node before any caller experience changes.
- The agent roster with skills assignments and the presence state model. Orbit's agent-state routing reproduces the same available, busy, and wrap-up model; map it now so the cutover does not strand an agent mid-interaction in a state with no equivalent.
- Analytics exports, recording exports, and retention obligations. Historical reporting stays with the incumbent; export what retention and compliance policy requires while Genesys still lets you, and name the legal-retention obligation on the audit sheet before the export window closes.
That inventory is also the business case: each wave that validates shrinks the per-seat bill still owed on the annual contract, so sequence the audit early even if the contract has a year left.
Step 2: port phone numbers first, in waves
Connectivity crosses before anything else, and voice numbers cross in staged waves rather than a big-bang event.
- Stand up SIP trunking first. Bring-your-own-carrier means the existing carrier relationship continues while Orbit layers the new call flow on top; if termination moves to Orbit instead, calls route on Devotel's own wholesale softswitch once the trunks land. The SIP trunking BYO-carrier guide covers that surface.
- Port the numbers last within the step, in waves. Start with a non-critical queue's numbers, a regional line or an after-hours number, validate the full call path on Orbit, then port the customer-facing queues in batches. Number porting is a regulated, days-to-weeks process per country and the regulatory registrations travel with each number, so stage windows such that no two customer-facing queues move at once. The phone number porting guide is the canonical reference for the local-number-portability mechanics: the bulk portability check, the combined readiness gate, in-platform LOA signing, FOC timelines, and porting webhooks, including the bulk CSV flow that moves hundreds of DIDs at once.
Done in this order, every element is exercised on real but low-stakes traffic before the customer-facing volume moves, and a failed wave validates back against the still-live incumbent with no caller-visible change.
Step 3: re-author the contact center against the Orbit ACD
Recreate each audited queue with its skills filters, SLA targets, overflow destinations, and in-queue callback on Orbit's contact center pillar, then the agent roster with skills and the state model. Recreate each audited menu flow in the visual IVR builder so prompts, business hours, and destinations match the routing contract loaded in the audit. Run the rebuilt queues on shadow traffic, a ported non-critical number, before any production queue points at them. The comparison matrices list Genesys's built-in CCaaS as parity rather than a gap, which makes this step a re-authoring exercise rather than a capability downgrade.
Step 4: sequence the messaging layers; verify flows move last
Voice numbers and contact-center routing are only one family. The messaging families each carry their own re-verification or registration gate, and the gate decides the order:
- WhatsApp WABA re-verification. Connecting a WhatsApp Business Account to a new provider means a fresh Meta Business verification and template re-approval cycle. Register the WABA and its templates on Orbit's WhatsApp Business surface while the Genesys integration stays live, because the re-verification clock is the longest lead time in the messaging family. The WhatsApp Business API guide covers the WABA product surface this attaches to.
- SMS sender registrations. A2P sender identities, 10DLC in the US or alphanumeric sender IDs elsewhere, re-register against the new provider. Sender-level configuration is tenant-owned on Orbit, not a platform-wide default, so the registration name and campaign metadata travel with the audit sheet.
- Verify (OTP) flows move last. OTP endpoints carry the hardest of the idempotency constraints: a switch that re-sends a code on retry is a customer-facing incident. Move the verify flows after the queue and messaging paths validate, with idempotency on safe retries as the sequencing rule, and keep Genesys's verify integration live until the Orbit verify API accepts the full production retry window.
Step 5: the CDP cutover, identity resolution mapped field by field
Genesys announced Genesys Cloud CDP as a platform-level capability in 2025, and many enterprise deployments still sit on a Segment or other standalone CDP beside the contact center. Either way the cutover is its own workstream inside the migration, sequenced after the channel families because it is the layer the families report into.
- Map identity-resolution rules, not just profile fields. Export the identifiers Genesys or Segment stitches on (email, phone, device ID, Genesys contact id) and the survivorship rules that pick a winning value per field. On Orbit's native CDP, identity resolution plus deterministic and probabilistic matching stitch scattered identifiers into one golden record, so the mapping exercise is rule-for-rule rather than field-for-field.
- Recreate computed traits and segments. Recreate the audit's trait and segment definitions in the no-code rule builder or SQL before any profile sync starts; a segment that recomputes on stale rules corrupts downstream routing rather than just reporting.
- Cut over event collection surfaces last. Move the event-collection endpoints (calls, messages, flow events, agent interactions) to the Orbit CDP's collection surface once the channel families above are live, then retire the standalone CDP connection. The native CDP one-year-on recap is the honest snapshot of what that surface ships today.
Compliance posture in this workstream is tenant-configured on Orbit: identity rules, consent at activation, retention, and erasure behavior are set per tenant rather than inherited from a platform policy, exactly as the audit's compliance row names.
Frequently asked questions
Is Orbit a good Genesys alternative?
The Orbit vs Genesys matrix treats the two platforms as parity on contact-center and AI capability and divergent on commercial model: published usage-based pricing and self-serve signup against Genesys's sales-led, per-seat enterprise licence. "Good alternative" here means the migration scope is a re-authoring exercise across a capability-parity matrix, not a downgrade, and the best Genesys alternatives 2026 round-up scores it alongside the incumbent suites on the same axes.
Can I migrate Genesys flows to Orbit?
Yes, by re-authoring rather than exporting. Genesys flow definitions are proprietary, so a flow does not import; its routing contract does. The audit exports every IVR node and queue with its destination, the visual IVR builder reproduces the contract node for node, and the ACD queues are recreated with the same skills, SLA targets, overflow, and callback behavior. Done in this order the rebuilt path validates on shadow traffic before any caller touches it.
What moves first, and what moves last?
Phone numbers move first (in staged waves, with SIP trunking stood up even earlier). Contact-center queues and IVR follow once a non-critical number validates on the new path. WhatsApp WABA registration and SMS sender re-registration run in parallel because they carry long provider-side lead times. Verify (OTP) flows move last because a retry re-send on an OTP endpoint is a customer-facing incident, and the CDP cutover closes last because the channel families must report into it before the standalone connection retires.
Do we have to rip out Genesys to start?
No. SIP trunking stands up beside the incumbent, rebuilt queues run on shadow traffic through a ported non-critical number, and each wave validates before the next port batch. Genesys keeps serving production traffic until the last wave validates; rollback stays available because trunks crossed first and numbers moved in waves.
Where to go next
- The commercial comparison that this runbook executes: Orbit vs Genesys and the ranked best Genesys alternatives 2026 round-up.
- The generic version of the same arc across Genesys, Talkdesk, Five9, and NICE CXone: migrate from an enterprise CCaaS suite.
- The per-channel mechanics: phone number porting, WhatsApp Business API guide, and idempotency on retries.
- The destination surfaces: contact center, native CDP, and pricing for the usage-based bill the migration business case is graded on.
Published 02 September 2026.