Hi Miguel,
I don't believe there is currently a supported/native "conversion" path between Genesys Dialog Engine Bot Flows and Genesys Digital Bot Flows. They are built on different execution models and channel assumptions inside Architect, even though conceptually they look similar.
Technically, exporting and modifying the flow definition may look tempting, but in practice it becomes difficult because:
the internal flow schemas are different
supported actions/components are not always equivalent
channel capabilities differ
input handling behavior differs between voice-oriented and digital-native experiences
Some intent/slot logic may be reusable conceptually, but things like:
prompting behavior
quick replies/cards
wait-for-input handling
knowledge behavior
session handling
DTMF/voice assumptions
often require redesign rather than direct conversion.
Another important point:
Genesys does not publicly document the underlying YAML/JSON structures as stable migration contracts, so manually editing exports can become risky and fragile during future platform updates.
What I've seen work better in real projects is more of a "logical migration" approach:
reuse intents/utterances/NLU concepts
reuse Data Actions
reuse business logic/tasks where possible
rebuild the orchestration layer natively for Digital Bot Flow
That usually produces a much cleaner result than trying to force a direct conversion.
If the environment has many existing bot flows, automation may still help partially:
for example generating intents/slots/prompts programmatically via SDK/API tooling and rebuilding the surrounding digital flow structure separately.
But I would be cautious about relying on unsupported export manipulation for production deployments.
------------------------------
Gabriel Garcia
NA
------------------------------
Original Message:
Sent: 05-18-2026 12:13
From: Miguel Lopez
Subject: Bot flows to digital Bot Flows
Has anyone tried to "convert" a Bot Flow to a Digital Bot Flow? Maybe exporting and modifing certain tags should be possible? What do you think?
#Architect
------------------------------
Miguel Lopez
Solutions Consultant
------------------------------