Does migrating to the New Builder preserve Router (conditional) step logic?

I'm planning to migrate a workflow from the Classic Builder to the New Workflow Builder (V2). The in-app migration dialog says webhook URL, connections, field mappings, and task history all stay the same — but it doesn't mention Router/conditional branching steps specifically.

My workflow has a Router step with multiple branches (routing leads by postcode serviceability and duplicate-check results before pushing to a CRM). Before I migrate, I'd like to confirm:

1. 1. Do existing Router branch conditions and routing logic carry over exactly, the same way connections and field mappings do?
2. 2. Is the migration reversible if something looks wrong afterward — can I go back to the Classic Builder version?
3. 3. Has anyone seen Router steps break or reorder after this migration?

This workflow handles live lead data for a client, so I want to be sure before migrating. 

Any guidance from the Pabbly team or others who've migrated a workflow with routers would help. 😀

Hello Dhawal,

Thank you for reaching out!

We understand your concern about migrating your live workflow, and we’re happy to clarify the process before you proceed.

1. Router Logic Preservation:
   When a workflow is migrated from the Classic Builder to the New Workflow Builder (V2), the existing Router conditions, connections, field mappings, and routing logic are carried over. You do not need to recreate the Router or workflow steps from scratch, provided the trigger app and event remain unchanged. If the workflow behaves differently after migration, we recommend checking whether there are any changes in the webhook configuration, such as a different webhook URL or trigger event (for example, Catch Webhook - Preferred vs. Catch Webhook - FileData).

2. Reversibility:
   Please note that the migration is not reversible, and the Classic Builder will be discontinued shortly. As a precaution, we recommend cloning your workflow and keeping the cloned version inactive before proceeding with the migration. This will allow you to retain the original workflow configuration for reference.

3. Router Stability:
   We have not received any reported issues of Router steps breaking or being reordered during migration. However, if you notice any unexpected behavior after migration, please share the details with us, and our team will review the workflow and assist you accordingly.

We hope this clarifies the migration process and helps you proceed with confidence.