Untangling Enterprise Systems for a Sudden Acquisition or Divestiture: Are You Prepared?

Untangling Enterprise Systems for a Sudden Acquisition or Divestiture: Are You Prepared?

As more companies announce mergers, acquisitions and divestitures to survive, the orderliness of their enterprise systems is critical: The "messier" a company's systems, the harder it will be to attract potential buyers. But the more up-to-date a company's systems, the more money they'll fetch.

IT Is a Key Player

Berez is unequivocal about IT's role in any acquisition or divestiture right now. "The way that technology is managed in the business," he says, "makes a huge difference in terms of the difficulty and success of both divestitures and integration or acquisition." In other words, the better two companies manage their technology, the easier and more successful a merger or acquisition will be.

In numerous client engagements over the years, Berez has seen a wide range of IT footprints, ranging from the "messy" to the neat. He's seen legacy ERP applications with tons of hard-coding and connections between systems. He's witnessed too much enterprise architecture fragmentation among various divisions using different software for similar business processes.

Comparatively, he's also seen "cleaner" IT environments "where you're working with modern packaged systems, you're in reasonably current releases of systems, and you've got relatively few systems."

Not surprisingly, the cleaner the IT environment in a particular line of business, the easier it will be to sell that business to an acquirer, Berez says, "because it's going to be better documented, more understandable, better supported by vendors and have lower operating costs."

Companies will also likely pay more for organizations with top-notch IT systems than they will for organization's whose systems are in disarray, says Berez. "Sophisticated acquirers revise their price based on how difficult it's going to be [to integrate IT systems]," he says. "So a company that has a mess in their IT systems and can't clearly describe what's supporting their business is going to get a lower price."

Even when your company is the acquirer, the flexibility and maturity of your own IT systems still matters, too. In one example, Berez says that one acquirer didn't fully understand the complexity of the acquiree's back-office systems and the massive problems that were likely to surface as a result when it came time to integrate-in part because IT hadn't been involved in any of the preliminary discussions.

Consequently, Berez adds, the acquiree will wind up spending nearly two extra years and millions of "wasted" money to upgrade and migrate both systems to a new platform. (For more on the trials and tribulations of enterprise software, see the Enterprise Software Unplugged blog.)

"The moral of the story is: Know thyself, first, and what your own capabilities are as an acquirer, says Berez. "And second, make sure you involve IT when considering deals, even in screening. You might decide not to do the deal once you see the true cost of [a potential acquisition]."

And not doing the deal might end up being the best business decision.

Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags ERPmergers

More about General ElectricSaturnWall Street

Show Comments