2018?
IMHO if you get an ERP system, a big success factor is implementing straight out of the box, with limited customizations. Be cautious and frugal - configure, don't develop.
(After doing due diligence that it will support your business volumes - large retailers and volume businesses have struggled with general purpose ERP systems that do not take kindly to a firehose of transactions)
An excess of time, $ and development consultants is not always a good thing.
Customizing ERPs is almost always a problem - possibly straightaway, because your corporate IT and consultants aren't really up to re-designing best practices on top of a complex software solution. Or later, because you can't track patches and updates coming in from your vendor. Especially problematic if the software is buggy to start with - many patches to be expected. But, hey, it looks attractive when you have access to the development tools, does it not?
Good requirements management, proper C-level sponsorship, user training and change management are better places to spend effort on and cost way less. Do pony up for data integration feeds.
If you are planning for a 4 year rollout, it could mean one of two things.
a) you are doing a cautious bit-by-bit rollout, but each module is put online in a relatively quick fashion. What should be easy wins (but the devil is in the implementation), spread out over time.
b) you're budgeting a lot of time and $ to customize, rather than configure, your ERP to your requirements. Big bucks, big bang. Much risk.