The purpose of this blog is to highlight issues to consider when migrating off the IBM i to a new platform. This is a high-level summary and is not inclusive of all the pitfalls that I have seen.
I do want to stress that “We need to get off this ‘antiquated server’ that does not have GUI” is the WRONG reason.
Further, as with any move to new technology proper discovery and planning are essential to ensure success. It can also take much longer than you think — like 5-7 years. Sometimes longer to successfully implement a new ERP system.
Disclaimer: IBM i is an operating system. iSeries and AS400 are servers. I use these terms interchangeably to make it easy for folks to find this kind of information.
Last week I was speaking to an IBM i expert who explained that 5 years ago new management grumbled that their IBM i system was an antique because it was character-based instead of GUI. Consequently, they chose to replace it with a prominent GUI-based Software-as-a-Server (SaaS) CRM. This IBM i expert lost his job.
As an experienced IBM user, it comes as NO surprise that 5 years later the GUI SaaS CRM had NOT replaced the IBM i system. Even though the company spent BIG bucks, the replacement project was a failure. The innocent were punished and the guilty were promoted.
Sound familiar?
How can that be?
Well, a quick Google search of “what percentage of ERP implementations fail?” will tell you 75%.
I have seen and heard of multiple decisions to migrate from IBM i business applications to new GUI-based applications. Most all cost WAY MORE than originally projected. For the few that do go live, they are about 5-7 years later than the original 1- 2 year “go live” plan (many still much longer).
Perhaps you are aware of similar experiences.
Quite simply the “new management” that make the choice to throw out “antique” IBM i applications are unaware of critical factors that have little to do with GUI screens.
There are many root causes. Here are a few.
Functionality And Business Logic. The evaluation to select the new system did not include an in-depth assessment of functionality and business logic compared to the current IBM i application.
Nuance And Custom Refinements. The selection team were unaware of nuances and custom software refinement that had been added over the decades of use.
Databases And File Design – Sometimes field lengths are insufficient. In cases where the field lengths can be resized, I have seen implementation teams unaware that related field lengths did not reconcile. I have also seen cases where the file layouts did not include fields critical to the unique business.
Migration Team Missing Key Teammates With Critical Expertise And Company Knowledge – I have witnessed other cases where the application manager or key power users with in depth process expertise were NOT included in the implementation team. Consequently, key information and processes are omitted.
Implementation Teams – I have observed implementations where one team knows software and nothing about the infrastructure, another team knows just the server hardware, another team’s knowledge is limited to Windows software, another team just knows networking – but not ALL of the teams are talking together or understand each other’s technology.
Non-Standard Data – All too common non-standard fields updated by users for “notes” because the current software did not have fields for new specific software.
Those who decide to switch out IBM i applications are unaware that the current system has probably evolved over 2-3 decades and includes nuances and custom features tailored for the business. Worse yet, they may not understand the business.
What Is The Solution?
There is no simple solution when migrating software. Nor was there a simple solution 10-30 years ago when the ERP software was first implemented.
Software implementations are challenging.
The most successful ones have team members that understand the business, dig deep to understand what they have and what they are getting, and set realistic goals to implement the software with the help of knowledgeable teammates.
What Leads To Failure?
The mindset that “this IBM i is out of date because it does not have GUI.”
If this is the impetus to change, beware.
Need guidance and would like to discuss this topic in further depth? Call me at 714-593-0387 or email me at blosey@source-data.com.
Leave a Reply