Migrating from work flow to flow for a catalog item issue for existing RITMs

[Kiddy]

Hi Team,

We have a Catalog Item in Production with 100+ active RITMs that are still in progress and not yet completed.

We recently converted the fulfillment process from a Workflow to a Flow Designer flow. During testing in lower environments, we observed that once the workflow is detached/migrated, the existing RITMs also get detached from their current execution.

We referred to the following KB article:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1080339

The KB suggests moving the stage to “Request Approved” before migration. However, our item has multi-level approvals and complex downstream activities, so we are hesitant to make stage changes without fully understanding the impact on existing approvals and fulfillment logic.

Our main concerns are:

• Preventing impact to existing in-flight RITMs

• Avoiding detachment or broken execution for current requests

• Ensuring multi-level approvals continue correctly

• Safely transitioning future requests to Flow Designer

What would be the best practice or recommended approach to handle this migration safely in Production?

Has anyone handled a similar Workflow-to-Flow migration for catalog items with active requests in-flight?

Any guidance or lessons learned would be greatly appreciated.

Thanks!

[Ankur Bawiskar]

@Kiddy 

My thoughts

-> New RITMs will use flow

-> Active RITMs will continue using the workflow since they have workflow context attached to it

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[krishna_12]

@Ankur Bawiskar 

Nope the existing workflows of RIMTS are getting detached which are in request_approved stage, due to the business rule Start FlowDesigner Flow

if you go through the  article shared in question it says

Cause
As the workflow does not update the stage on the RITM record, it will have a value of "request_approved". The stage value matches the conditions defined on the "Start FlowDesigner Flow" business rule (BR), which triggers the flow

Now we are stuck that we cannot close the approvals and or items to move this change to Production