Enterprise System Spectator blog: ERP and enterprise system vendor evaluation, selection, and implementation.

The Enterprise System Spectator

Friday, June 16, 2017

Strategies for Dealing with Legacy Systems

Developing an IT strategy for some organizations can be difficult because of the presence of a legacy system. Legacy systems that are old, out-of-date, and difficult to maintain are a huge obstacle to innovation. As a result, business leaders become increasingly frustrated by their inability to roll out new mobile apps, connect with customers, analyze business performance, or become a digital business.

In recent years, it has become popular to describe organizations with an out-of-date legacy system as being in “technical debt.” I would take this a step further. If an organization ignores the need to update the system for too long, it can lead to what I refer to as “technical bankruptcy.”

We can define technical bankruptcy as a situation where the organization cannot, or finds it exceedingly difficult to, pay off the technical debt. It does not mean that the organization is in financial bankruptcy but rather that its systems are broken or held together in a way that makes them extremely difficult to upgrade.

Significant Percentage of Organizations Are at Risk of Technical Bankruptcy

In work with our clients at Strativa over the past several years, we have gained new insights into challenges facing organizations that have out-of-date legacy systems. We recently took the opportunity to combine those insights with survey data from our sister IT research firm, Computer Economics, to produce a new report, Avoiding Technical Bankruptcy in Legacy Systems. (Click the link to download the report free from the Strativa website.)

Figure 3 from the full report shows the magnitude of the problem as it applies to ERP systems. A small but significant percentage (7%) of organization have not upgraded their ERP systems for 10 or more years. These are likely to already be in technical bankruptcy. But the 13% of organizations that have not upgraded their systems in the five-to-nine-year time frame are in the danger zone: Technical debt is building, and if the organization does not undertake a major upgrade, it risks falling into technical bankruptcy.

Signs of Technical Bankruptcy

What are typical signs that a legacy system has reached the stage of technical bankruptcy? We found five characteristics:
  • Extensive modifications, extensions, and interfaces.
  • Poor understanding of the system by users and IT alike
  • Direct involvement of IT personnel in business processes.
  • Legacy system atrophy as shadow IT emerges.
  • Upgrade or replacement hard to justify.
In the full report, we explore the symptoms of technical bankruptcy and the devastating effects that it has on the organization. We continue by quantifying the scope of the problem specifically for ERP systems, using our research on the typical age, frequency of upgrades, and extent of modification of these systems.

Most importantly, we conclude with recommendations on how to avoid technical bankruptcy and, for organizations that have reached this stage, strategies for getting out and staying out of technical bankruptcy going forward.  

Download the full report, free from the Strativa website:
IT Strategies for Legacy Systems: Avoiding Technical Bankruptcy.

Bonus: Watch a Datamation's James McGuire in a video interview with me about the report.

Labels: , , ,

by Frank Scavo, 6/16/2017 03:50:00 PM | permalink | e-mail this!

 Reader Comments:

Hi Frank,

The technical bankruptcy phenomenon is hugely pervasive. You describe the causes well.

I see three ways out of it:

The first is tenant aware SaaS. You have been a proponent of this for many years and for good reason.

The second concerns the separation of customer code from vendor code. This concept can apply to both cloud and on-premises deployment. Many vendors have embraced this concept already with the idea being that the customer makes as many enhancements as they wish but that their logic interacts with the vendor functionality via APIs only. This protects against the entanglement of customer code and vendor code that is present in many "customized" legacy systems and that results in paralysis.

The idea of this second approach is to enshrine ownership of separate code lines, which allows changes to be made more easily on either side by the respective parties.

The third way concerns visual development and empowering business analysts to extend functionality in and around the front end. The basic idea is to reduce reliance upon hand coders and manually driven productivity suites such as Microsoft Office. The Microsoft Flow and PowerApps combination, and SmartSheet/AppSheet combination, are two examples of this approach. However there are more open and general purpose aPaaS (application PaaS) alternatives arising such as Bubble.is

Where funding is not available for imminent legacy system replacement, the best approach might be to "ring fence" legacy systems and cease updates as much as possible, and instead begin to build a sidecar application system on a cloud platform which over time augments and replaces legacy system workloads - and to also serve as a unified front end for user interaction. Thereby legacy systems are gradually subjugated and can be quietly removed with little business disruption. In other words the application system running on the cloud platform effectively takes charge by orchestrating everything that happens - much like what happens in some conventional tightly-coupled and highly integrated and hideously expensive ERP systems.

Furthermore, using a micro services architecture in the application system running on the cloud platform - allows changes to be made more easily thanks to looser coupling. Gone is the monolithic architecture where changes in one part all too often result in unforeseen problems elsewhere.

Hi Mattthew, you comment is a post unto itself. Good job. I agree with all this. Of course, better to adopt these strategies from the start rather than wait until the organization has gotten to the point of technical bankruptcy.

Thanks Frank. I tend to get carried away - as I shall once more demonstrate :)

The main point I wanted to convey is that many legacy systems are not worth updating and that the best way to deal with them is to relegate them into the background behind an application running on a Cloud Platform - with the intention of quietly swapping them in and eventually out later on.

I should give you credit for this post from 2002 which touches on the same concept.


Despite advocating this I still have a lot of faith in ERP Suite offerings as they avoid interface complexity. But on the flip side, maturity and cost effectiveness of modern Cloud Platforms and simpler interface protocols and services (such as Dell Boomi) breaths new life into the older EAI approach.

The downside with ERP suites is the cost of migration - and risk - because it generally needs to be done in a "big bang" approach. And like I was saying earlier this can be prohibitively expensive or just too difficult for many customers - particular those customers who have a patchwork of legacy ERP systems.

Building a custom application is ambitious - even in The Cloud - but it can be built gradually, starting with a front end followed by a unified user permissions model and a universal monitoring and scheduling consoles, for example.

Amazon Cloud Services, Google Cloud Platform, Microsoft Cloud Platform System, Pega 7 Platform, Salesforce Platform, Workday Cloud Platform, and SAP Cloud Platform (and other Cloud Foundry partner platforms) are some examples of where to build an enterprise application that glues together all the bits and pieces that invariably come and go in most large organisations. I've listed a bunch to avoid bias (in no particular order). Some are more general (or open) in nature while others might be a little more closely aligned with particular industry verticals or other products offered by the same vendor.



Post a Comment

Powered by Blogger

(c) 2002-2018, Frank Scavo.

Independent analysis of issues and trends in enterprise applications software and the strengths, weaknesses, advantages, and disadvantages of the vendors that provide them.

About the Enterprise System Spectator.

Frank Scavo Send tips, rumors, gossip, and feedback to Frank Scavo, at .

I'm interested in hearing about best practices, lessons learned, horror stories, and case studies of success or failure.

Selecting a new enterprise system can be a difficult decision. My consulting firm, Strativa, offers assistance that is independent and unbiased. For information on how we can help your organization make and carry out these decisions, write to me.

My IT research firm, Computer Economics provides metrics for IT management, such as IT spending and staffing benchmarks, technology adoption and investment trends, IT management best practices, IT salaries, outsourcing statistics, and more.

Go to latest postings

Search the Spectator!
Join over 1,700 subscribers on the Spectator email list!
Max. 1-2 times/month.
Easy one-click to unsubscribe anytime.

Follow me on Twitter
My RSS feed RSS News Feed

Computer Economics
IT Spending Ratios by Industry and Company Size
IT Spending as a Percentage of Revenue by Industry, Company Size, and Region
Outsourcing Statistics
IT Spending and Staffing Benchmarks
IT Staffing Ratios
IT Management Best Practices
Worldwide Technology Trends
IT Salary Report


2014 Best Independent ERP Blog - Winner 2013 Best ERP Writer - Winner Constant Contact 2010 All Star Technobabble Top 100 Analyst Blogs

Key References
Strativa: Business strategy consulting, strategic planning
Strativa: IT strategy consulting
Strativa: Business process improvement, process mapping, consultants
Strativa: IT due diligence
Strativa: ERP software selection consulting and vendor evaluation
Strativa: CRM software selection consulting and vendor evaluation
Strativa: Project management consulting, change management
StreetWolf: Digital creative studio specializing in web, mobile and social applications
Enterprise IT News: diginomica

Spectator Archives
May 2002
June 2002
July 2002
August 2002
September 2002
October 2002
November 2002
December 2002
January 2003
February 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009
August 2009
September 2009
October 2009
November 2009
December 2009
January 2010
February 2010
March 2010
April 2010
June 2010
July 2010
August 2010
September 2010
October 2010
November 2010
December 2010
January 2011
February 2011
March 2011
April 2011
May 2011
July 2011
August 2011
September 2011
October 2011
November 2011
December 2011
January 2012
February 2012
March 2012
April 2012
May 2012
June 2012
July 2012
September 2012
October 2012
December 2012
January 2013
February 2013
March 2013
May 2013
June 2013
July 2013
September 2013
October 2013
December 2013
January 2014
February 2014
March 2014
April 2014
May 2014
June 2014
July 2014
August 2014
September 2014
October 2014
November 2014
December 2014
February 2015
March 2015
April 2015
May 2015
June 2015
July 2015
September 2015
October 2015
November 2015
February 2016
May 2016
June 2016
July 2016
August 2016
September 2016
October 2016
January 2017
February 2017
May 2017
June 2017
October 2017
January 2018
April 2018
May 2018
January 2019
February 2019
Latest postings