This is a great idea and concept but either has to be narrowed drastically in scope or grow to unsustainble levels. When I first clicked in on this link I was

This is a great idea and concept but either has to be narrowed drastically in scope or grow to unsustainble levels. When I first clicked in on this link I was thinking it would allow moving from AWS (for instance) to Azure (or any other vendor). That is a truly hard problem to solve. I see that is not a good use case for this. Thinking about going from SAP -> Oracle E-Business Suite (if that is what Oracle's name is now) is another hard problem and in general takes years. It is not just moving data, but enormous amounts of logic / routines / rules that are not 1:1 mapppable. Producing a solution that is repeatable enough to reuse would take years as well and in that time the products themselves will have shifted Scaping is ok you can get information but the forms of the new ERP will again not be 1:1 Many many years ago I worked on a similar project to this. Migraitng one ERP system to another (not the players mention here. Both were fully on prem. After beating our heads, the wall figuring it all out, we ended up going directly at the database of the source system. This is certainly -not. advisable, it is not supported and not documented. I still have nightmares about sitting for weeks figuring out the schema to the extent we could get the data we wanted. That it was non intuitive is an understatement. What we came up with would not be usable to sell to a different company that wanted to do the same migration. Though we cold give them a lot of hints on the data model. This was all secret. Had the ERP vendor we were moving away from seen what we did they could be quite displeased. I hope I will love to see where this ends up. If you manage to solve it well there are containers of gold in your future. If you end up taking a year or more pre major project then probably not as profitable and higher risk