How to Migrate Legacy Systems to Improve Performance & Adaptability
The antiquated business systems, apps, and processes that were revolutionary 30+ years ago can’t compete (or integrate) with modern technology.
Even if the legacy systems of yore are still in operation and mission-critical, it’s very likely that they are monopolizing IT resources while also being incompatible with new software. In other words, legacy systems are holding businesses back.
Sooner or later, every organization that is looking to embrace digital transformation has to consider the best legacy migration and modernization strategy — which is often easier said than done. In this article, we explore the different challenges of legacy migration and how low-code technology can streamline the development of new, custom business apps to replace, supplement, or improve your existing systems.
2 types of legacy migration projects
There are two types of legacy migration projects: lift-and-shift and business transformation.
Lift-and-shift legacy migrations
These are typically initiated by IT because the underlying infrastructure or technology needs to be updated or replaced. This is often for cost or technology obsolescence reasons. In these scenarios, the IT organization is looking to rebuild the existing system on a one-to-one basis, and there is no compelling or urgent need for significant change on the side of the business. They simply want a new system that allows them to continue doing what they’ve been doing.
Most of the legacy migrations we see our customers undergo are business transformation initiatives. Driven by the business, these apps are meant to replace legacy systems that don’t sufficiently support business processes or provide the right user experience. While these legacy migration projects require new functionality, they often must support current processes as well.
Within the business transformation category, we see two types of systems:
- Core legacy migrations: Larger systems built by central IT, such as portals and custom ERP systems. These apps require scale, performance, and complex legacy database migration.
- Non-core legacy migrations: Smaller, departmental apps originally built by the business using tools like Microsoft Access, SharePoint, or Lotus Notes. The defining characteristics for successfully migrating these systems are business enablement, centralized governance, and easy data migration.
4 legacy system migration challenges (and the low-code solutions)
1. Lack of flexibility creates tomorrow’s legacy
Legacy migrations require organizations to build a system that is flexible enough to adapt to changes. The last thing IT wants is for the new system to become tomorrow’s legacy.
Low-code platforms enable organizations to employ a modern app architecture that promotes agility by leveraging microservices. Look for a platform that enables the easy creation of autonomous apps and services that can be recombined and shared, while facilitating fast, frequent change cycles so the system can evolve to meet new business needs. It is critical to take advantage of a future-proof platform so you aren’t creating an unmaintainable set of apps or piles of machine-generated code.
Enabling developers to rapidly take advantage of best-of-breed modern technology stacks without having the skills to be an expert in all of them will create a high level of flexibility that is fully documented and visually constructed.
2. Mission-critical apps fail to deliver at scale
Many core legacy systems fail to deliver the required performance at scale. Look for a low-code platform that ensures the new solution can be deployed with the required resiliency and high availability for mission-critical use. A low-code platform with a cloud-native architecture enables automatic failover for continuous operation of business-critical apps, ensuring that they don’t run into the same performance issues as legacy systems.
3. Inadequate oversight of quality
Due to the size and complexity of most legacy migration solutions, there is often inadequate oversight of the quality of the app. It is important to be able to proactively monitor and address the quality of the applications to prevent technical debt and improve long-term maintainability. Look for a low-code platform that embeds automated quality, testing, and performance monitoring within the development lifecycle.
4. Usability is an afterthought
With this type of application, usability is often an afterthought, blunting ROI. Use low-code development to take a user-centric, design thinking approach when creating the new solution. A deeper understanding of the users and business context can help close process gaps that existed in the legacy system, delivering an end-to-end solution that drives substantial productivity gains.
This level of understanding may also result in the incorporation of new capabilities that weren’t available in the legacy system (e.g. mobile, conversational UI), or the removal of unused features. Both help deliver a more focused and engaging user experience. Look for a platform that enables the business to participate in the design process to ensure app usability and success.
Example: How the Boston Globe migrated from Lotus Notes to low-code
The Boston Globe, the largest newspaper and regional website in New England, turned to Mendix’s low-code development platform to migrate a dozen legacy Lotus Notes workflows that were increasingly difficult to maintain and failed to provide a modern user experience. The first project was migrating the Globe’s newsroom corrections legacy database, a key application for monitoring quality for its 350-person newsroom.
The results were phenomenal. What took over a month to code in Lotus Notes was built in just five days with Mendix. Now, the Boston Globe is using the low-code platform to migrate other Lotus Notes apps as well as build new apps to move the business forward. Thanks to the high productivity and collaborative approach to building applications, the Globe is delivering apps in days or weeks, creating immediate and substantial business impact.
This blog post was originally published on January 5, 2018, and has been updated to include the most current information.