Migration: A Topic of Information Technology or the Physical Movement by Humans?

If you just type in “migration” into your favorite search engine, you might find different results. Some are about sociology, like the physical movement by humans, some might be about animals traveling in search for a new habit, but you also might find results regarding information technology.

Congratulations! If that is what you are looking for, you found it. But what exactly is a migration when we talk about information technology? First of all you should know that there are some different migrations to think of. We can talk about a data migration, an architecture migration, a software migration and a language migration. Broadly speaking, it is about software and hardware migration. However, for today let’s just talk about what kind of changes are possible when we talk about migration in general.

First of all there is the update, also known as patch. Here everything stays within the software product line. There should be no big troubles embedding the latest version into the system environment and all updates should however be possible and from this time on useable without special trained staff. And of course: Nobody has to get new devices due to the update and also nobody has to get a new software license.

Need more than just a software update?

The next form of a migration would be the upgrade. This is generally a replacement of hardware, software or firmware with a newer or better version, so that the upgrade affects the product itself or the compatibility with its environment. Here again, everything stays within the software product line. Existing databases can be migrated with little effort and therefore sufficient tools are provided by the producer, so that no external support is needed.

The kind of migration that has the most impact is for sure the one which replaces a whole system so in this case; we leave the software product line or skip at least one generation of the product. In most cases there is a lack of required migration tools and therefore experts are needed to ensure the overall functionality of the system.

So if you ever consider the last form of migration, be aware that there are two ways to think of it: You can either choose a target date on which the migration will take place at a time or you might consider a step-by-step migration. Sounds interesting? More on that later… Thanks for following our blog!

Do we really need to think about legacy modernization?

If you hear the term “data migration”, it might send a chill down your spine. It doesn't matter, whether you work as a CEO or as a secretary: sometimes you might feel, that something regarding your work with the computer goes wrong or things just should not be the way they are. Then you maybe find yourself swearing at the computer but anyhow thinking: “Never change a running system”.

But what if you always find yourself in trouble, even if the problems are not that big? So first of all, you might want to figure out, whether a legacy modernization or a migration is necessary for your company and could help you, to get your work done more relaxed.

A good way to start this is to take a look outside your window. Relax and think about the following questions – but please: be true to yourself!

1. Do you still have (enough) technical support for your legacy systems?
2. Do you have more and more problems with downtime? If yes, how does this affect your work?
3. Do you have problems, recruiting new qualified employees, who can deal with your legacy systems?
4. Do you sometimes think, that you are way too inflexible with all your legacy systems and wish for more extensions, interfaces or an improved usability?
5. Do you have to deal with data security issues, because your legacy systems don´t accomplish the standards?

So what do you think right now? Might some of this be true? Is it for real, that you just thought about answering at least one of these questions with yes? Because if you do so, you really should answer our title question with yes, too. In this case, you really should think about a legacy modernization.

What does that mean? Well, you first of all should consider, that changing a running system, might be a good thing. As the American writer Alvin Toffler said in 1970: “Change is not merely necessary to life – it is life.”

If this now has been a kick-off for you, to finally become an interest in the topics related to data migration or architecture migration, it would be a pleasure for us to welcome you as a new follower of our blog. Stay tuned for the next articles, in which we offer you more information about what migration is and how it could look like.

Risks of Legacy Applications

There is no better idiom that “If it ain't broke, don't fix it” to illustrate the main barrier to IT migration. The attitude “if a system or method works there is no reason to change it” is the enemy of innovation! Why? Do business executives know what that really means for a company? In this article we will go through the main impacts of legacy applications by highlighting the connection between business and IT and seeing the potential savings and benefits companies get from moving far away from old systems.

Inefficient IT Infrastructures

Console Vs Web GUI

Legacy applications provide companies with systems that, even if they work well, are no longer able to adapt to a changing business environment. See for example the problems financial institutions are facing whose core banking system relies on COBOL programs that were built more than 30 years ago. At that time priority was given to security and reliability and although these criteria are still relevant, today systems need to be more flexible agile and innovative. IT inefficiency would consist of the following points:

• Lack of integration:
  Systems integration is the process of linking together different computing systems and software applications physically or functionally to act as a coordinated whole. It is challenging to link together several applications that use different languages and or architectures. If we go back to the banking example, their core system was developed in COBOL, if additionally they have SAP and if they acquire a new CMS in Java all three items must work together. It is possible to do so but it demands complicated workarounds.
  Advantage of Migration:  A Service Orientated Architecture based on software components that can be re-used for different purposes. 
• Lack of scalability:
  The scalability is the ability of a system to handle an increasing amount of work in a capable manner or its ability to be enlarged to accommodate that growth. The problem with legacy systems is that once it reaches its physical limits it’s impossible to it make it faster. This means that if a company has high potential for economic growth is planning to expand its activities; its legacy system is likely to be overwhelmed by new workload. 
• Lack of accessibility:
  Most of legacy applications still use complicated command line interfaces that limit the ways to use a program, as opposed to graphical interfaces that are more intuitive, and easier to use.  Moreover migration with cross platform technology facilitates the development of mobility applications.

In the long run, inefficient IT infrastructures, lower firm’s competitiveness which directly affect its revenue and market share.

Business Continuity 

Will the company have the resources to fix hardware or software problems? As newer technologies emerge, the pool of skills qualified to work on legacy applications shrinks: employees retire from work, old programming languages are no longer taught in universities, or employees would rather work on projects that keep their set of skills updated.

According to a Computerworld survey of around 350 IT professionals, for 50% of them, the average age of their COBOL programmers is 45 or older, 46% of them already noticed a shortage in COBOL programmers. Next to the skills management issue, the lack of qualified employees brings the problem of respecting Service Level Agreements. For instance, in the financial industry SLAs are made over a 10 year time frame or longer. Given the fact that’s it is already difficult to find staff today we can only be pessimistic about the situation 10 years from now.

Unexpected Costs

A common misconception about modernization is that it's often considered as “spending” rather than “saving”. Although migration costs can be significant, firms could think of it as a way to potential savings and potential business opportunities. Leaving the systems in their current state involve direct and indirect costs, often not fully understood.

Cost comparison of a migrated and an old application

• Labor costs:
• Before Migration:
  Workforces play a major role in determining how decisive it is for a company to modernize its IT infrastructure. Companies have an increasingly tough time in replacing people with critical skills – for example maintaining the old applications – retiring from work. If the company uses an old COBOL, RPG or PL/I application, today’s new generation of developers trained in C++, Java or .Net would need an additional coaching to work with COBOL, RPG or PL/I . Hence, as the pool of resources qualified to work on old systems diminishes, the staff training cost increases.
• After Migration:
  In contrast, new applications simplify system management, which means that less staff is required for ongoing support and maintenance. Even implementing new features is cheaper because it is more efficient with modern programming languages. This does not necessarily result in the reduction of operational staff but rather in the reassignment of personal to responsibilities or projects of higher strategic value. 

• Software Costs:
• Before Migration:
  Companies have to pay thousands of dollars in monthly license fees to run HOST applications while cheaper alternatives exist.
  Operation system: zOS for IBM mainframes
  Database management system: DB2 for IBM or other utility programs proprietary for HOST systems
• After Migration:
  Firms reported up to 83% savings by moving from an Oracle/IBM solution to SQL server which is a Microsoft product with license fees. With the open source MySQL it would even be entirely free.
  Operation System: Unix or WindowsDatabase management system: MySQL or often free systems for modern platforms

• Hardware costs:
  Moving from an expensive IBM mainframe to simple personal computers or rack servers is another source of savings. For instance, an IBM AS/400, which is the mainframe/HOST of small companies, costs around $20 000 for four years. Five rack servers with an equal amount of computing power would cost around $5.000.

• Indirect costs:
  Old systems decrease overall productivity and limit firms’ competitiveness. The advantages of modern graphical interfaces (GUI) compared to terminal applications are one example. This leads to indirect costs that take the form of client’s discontents and therefore business loss.

Migrating legacy applications obviously involves costs. Whether the project is handled in house or outsourced, resources must be affected to the different stages of the process: analysis of the old application, selection of the new platform / technology, definition of the migration strategy and the code and testing of the new application.

“If it ain't broke, fix it!”

It is probably better to try to avoid the problems related to aging platforms in the first place, rather than trying to fix them once they arise.

To compare the relative costs and benefits of either keeping an old application or migrating it, organizations must review their expectations considering the various advantages and disadvantages each solution brings.

A case study by Alinean analyzes the cost reduction of migration projects conducted at two companies from two different sectors: one in financial services and one in manufacturing. The analysis compares the total cost for application migration over four years to what it would have cost to keep the old version (evaluating initial costs, annual support for new equipment and software, and labor expenses).

In both cases, the cost of implementing a new system was much cheaper than the cost of keeping and still maintaining the old one. The financial services company was able to reduce hardware costs by 72.6%, software cost by 78.8%, labor costs by 21.10%, and facility costs by 39.70%. With a total initial investment of $9,363,552 (migration project, hardware and software costs) the company reduced annualized operating costs by 46.4%. For the manufacturing company, the results are even more outstanding. The company reduced hardware costs by 22.9%, software costs by 92.1%, labor costs by 47.6%, and facility costs by 45.9%. With a total initial investment of $6,136,000 the company reduced annualized operating cost by 70.9%. (See the complete case study here).

If the IT department can be isolated from business concerns, application migration emphasis the role of IT projects in the overall business effort of a company. From a financial point of view, IT migration allows great potential savings (that can also pay back the initial investment). From an organizational point of view IT migrations improves processes and hence better support organizational objectives.