[hef19898]

You already cannot map data automatically from one SAP instance to another, so forget auto migration. What usually happebs is, to keep the legacy system around for auditing purposes, and the live business happens in the new one. With cut-off dates per function and or department. With manually developed interfaces, and all the crap that comes with those, during the migartion period.

An nothing of this has anything to do with SAP, and everything with ERPs and the messy reality of businesses.

[laser]

Why is it not entering the realm of possibility for the migration system to function not at an API layer but at the levels of pixels and OCR and RPA to click through every possible interface within the ERP to export and structure the legacy data to complete a total migration? Like humans copying over the data manually?

[hef19898]

Because the migration has to be auditable. And the data fields between the systems / databases mapped against business processes, on both systems. If you find a solution to automate that, cudos...

[arach]

would it be fair to suggest an automated migration solution (therefore less manual) might be more auditable than human driven?

You'd probably start with a human in the loop solution but mapping should be a solvable problem

[hef19898]

No, from my experience it wouldn't be fair to say that.

There is a reason why migration projects are yearlong, multi million projects. Go through one, ideally multiple, of those first before looking at automating any of that. Added benefit, jobs at those projects pay incredibly well for the functional consultants involved. And when, when not if, automation doesn't work out, you still don't have to worry about a job ever again.

[arach]

it's complicated because it's complicated and the pay is good sounds like good white collar jobs about to get automated away

[hef19898]

Serious question, what is your experience with ERP systems so far?