Lack of committent / involvement from the whole org
From my experience there is a lack of committent and involvement of the organisation buying the ERP solution to walk through all the modules/functions with the people who will be using them to see what does or does not fit the way we do it - and then agree what can the org change can do to fit or what absolutely must be customised
So many times we read that the idea was to change the way things are done to keep it all standardised but instead they customise the hell out of it blowing the budget/timescale - I think this was Birmingham's problem of intentions from the top meeting immovable departments at the bottom.
Personally I have taken part in one ERP migration and it was a success because it was fully walked through and fully tested end to end by all departments before going live, and yes they changed the way things were done (and many were improvements)
As for UK councils - they need a UK council ERP system which is the same from council to council as they have pretty much have the same core functions, if years ago they had got together to write one it would have saved a shed load of money by now. Yes some may have some edge cases but once that "module" is developed others could use it.
Yes I know I am seeing unicorns for the last paragraph but it riles me to see our tax money being spaffed out on failure after failure - with NO lessons ever learned or they would have solved it by now