One of the hardest things about software upgrades is knowing when to give it a shot. Upgrade too frequently and you'll lose functionality and complicate your systems with the learning curve implicit in almost any upgrade. But upgrade too seldom and you'll find yourself on the edge of an upgrade cliff, requiring a major software overhaul that will take too much time, energy, and resources. In the spring of 2009, an electronics company was determined to complete and implement an SAP upgrade by December. They knew it wouldn't be easy, so they called for extra help.

In this case study, see how a company used a third-party service to rapidly complete their SAP upgrade by avoiding redundant and useless "fixes," determining what was important and what was not to the company's specific ERP system.