Hey Steve, I agree that a migration tool would be very useful. One of the things to consider when converting from custom to bionic rules is that usually there shouldn't be a blanket 1 to 1 conversion, as in some cases it took multiple custom rules or even a rule chain to accomplish something that can be done in a single bionic rule. And if we just did a 1 to 1 conversion, we might miss some opportunities to benefit from the efficiencies inherent to bionic rules. 





So ideally a precursor to any migration step (and I agree that a migration tool would help here a ton) would be a review of all rules to identify ones that should be combined and re-written vs ones that should just be a 1 to 1 conversion. 





I'd love your thoughts and expertise on this approach. 

---

Hi Steve,





As Dan mentioned, 


While we are working on  a utility to migrate custom rules to bionic rules, but that alone might not be a good idea because the utility will convert one custom rule to 1 bionic rule.





However, multiple custom rules can be merged to one bionic rule if they solve the same business need and one Bionic rule helps improve manageability. 





We suggest you to convert your exiting custom rule(s) [with or without utility] to Bionic Rule, Validate and test completely to ensure it solves the same purpose in a better way.





Advantages of Switching to Bionic Rules


1) Lot of additional extended capabilities including Transforming, aggregating, pivoting and merging data


2) No need to create multiple rules for different source objects if they solve the same business problem. That can be accomplished by just one bionic rule.


3) Lesser number of rules => Better manageability of rules





Regards,


Jitin

---