Hi,
We are upgrading from CRM2011 to CRM2015. This is an upgrade rather than an ETL migration so we are lifting the CRM database dropping it into CRM2011 RU18, then lifting and dropping into CRM2013 and finally lifting and dropping into CRM2015.
We have a large number of 'in flight' workflows which are in a waiting state based around x number of days etc. The deployment across CRM instances and the volume of data necessitate a number of days for this deployment. This means that many of these workflows would invoke/fire during the deployment as their dates will come into play.
I would really appreciate any suggestions/advice around how we can mitigate this situation.
We have considered letting things run but I don't think this is adequate as the workflows call plugins where we are likely to have issues with plugins unavailable etc.
The other option we are considering is pausing all the workflows and restarting a few days later. The concern around this is that when the workflows re start on CRM2015 and run asynchronously we may have a situation where dependent (child) workflows start at the same time as the parent and are awaiting a state that has not yet occurred.
I would really like to hear other people's experience here. I imagine there is no silver bullet scenario but would like to know how we can have some assurance as to what the status of the workflows might be in CRM2015.
Thanks in advance.
D