Upgrading may be a simple task if your organization is operating on a fairly recent version (think 12.0 or 12.1). But if you’re considering replacing a version that’s been around for awhile, the upgrade process may not be quite as easy, and a re-implementation is a better option.
Every single day, your company is producing tons of data. That’s useful to keep your business functioning at its peak, but it also increases your chances of having bad data. And without clean data to pull from, analytics quickly lose their worth.
When it comes to updating their system, many organizations look to the speed of the process first. And it makes sense: at first glance, an upgrade seems like the best and fastest way to reach their EBS 12.2 end goal. But, in addition to speed, it’s vital to look at the state of your data, too—because there are a lot of risks involved in upgrading a system that houses questionable data. This includes bringing old issues into EBS 12.2, which will only compound the previous problem.
Upgrades give you the opportunity to piggyback off of current customizations and keep their system’s processes intact. With historical data and a tailored EBS system keeping your business up and running, an upgrade may be the better option. This will allow you to expand on existing functionality quickly. But it does come with a downside: Should you choose to upgrade, you’ll lose some of the shiny new features and enhancements that come along with EBS 12.2.