# Inflight Migration Hi, We have a requirement where we have to migrat

As you are trying to shift from a different tool and maintain the state of the process, you will need to put in a bit extra effort during designing. The approach stated by Rajat in the first comment will work. Although, there is one more approach.
But to make this approach work, you need to put in a bit extra effort while designing.

Create a table in db with name of the task which you want active per application id.
Now create an PM which will only have a script task. Input parameter for this PM will be application Id & a task name.
Script task output tab will query the db which has the active task data by application id and get the active task name (which you want to be active) and compare the value which will be passed from the main process. If same set the pv!reachedDesitnation = true, otherwise false.
Use this PM, before every task in your whole process and pass the application id & task name (task name which is just after this sub process node) & take out the pv!reachedDesitnation in main process by using output of subprocess node. Now if the next task is the active task for this application Id you will get result as true.

Use a XOR gateway between the subprocess node & task re-route accordingly.
I hope this would make your work easier even if you don't have milestones for each task.

This is not everything you would need to shift the processes.
You still have think about the folder hierarchy & documents transfers.
Also, you have to think out a way to save the active tasks name from the previous tool into db.

As you are trying to shift from a different tool and maintain the state of the process, you will need to put in a bit extra effort during designing. The approach stated by Rajat in the first comment will work. Although, there is one more approach.
But to make this approach work, you need to put in a bit extra effort while designing.

Create a table in db with name of the task which you want active per application id.
Now create an PM which will only have a script task. Input parameter for this PM will be application Id & a task name.
Script task output tab will query the db which has the active task data by application id and get the active task name (which you want to be active) and compare the value which will be passed from the main process. If same set the pv!reachedDesitnation = true, otherwise false.
Use this PM, before every task in your whole process and pass the application id & task name (task name which is just after this sub process node) & take out the pv!reachedDesitnation in main process by using output of subprocess node. Now if the next task is the active task for this application Id you will get result as true.

Use a XOR gateway between the subprocess node & task re-route accordingly.
I hope this would make your work easier even if you don't have milestones for each task.

This is not everything you would need to shift the processes.
You still have think about the folder hierarchy & documents transfers.
Also, you have to think out a way to save the active tasks name from the previous tool into db.