Frequently Asked Questions

Ask a question »

Q.  How long does the migration take?

A.  Every project varies in length depending on number of lines of code, the availability of IT resources [familiar with the system, source code, documentation, data, etc.]. Typically, the project is measured in [a few] weeks, or [a few] months. The key point is that automated conversion is the fastest way to get the business logic and data off of expensive legacy systems.

Q.  What resources do we need to put into the project?

A.  It can be whatever you wish. In some cases, the client just turns over their documentation, code, data, etc. and tell us the target architecture. Our tools and experience can work very independently, bringing your staff back in only for the test/verification of the converted system. 

Q.  What is the effect of the migration on the end-user community?

A.  The "effect" to the end-user community is up to you. This issue is separate from the conversion issue. It's up to the client to determine what changes the users want, and what would help the end-users in their productivity. 

From a migration stand-point, there need not be any impact on the end-user, since the user interface can be left unchanged—users would not know that the system was moved to an open platform except for the increase in performance, and the increased access to the system. 

If the client determines that [a sub-set of] users could benefit from a new [web based GUI] interface, Unicon had the automated tools and knowledge to convert the screens as part of the project.

Q.  What [OS, server, database, etc.] platform do you recommend we migrate to?

A.  The target open system platform is up to you. We have clients that have gone to every combination imaginable with 100% success. Some of the criteria they use in their decision-making is IT staff knowledge [so it can be leveraged for increases in productivity], availability of existing assets [servers, software and database licensing, bandwidth], vendor relationships [to leverage pricing and support], or corporate standards.

Q.  Our system is old and is planned for replacement with a [COTS] package in the next 2 years. Is there a return on our investment that would support making an interim change now?

A.  This is an analysis we hope you will do. We have some tools and benchmark figures that can help you in your evaluation. Generally the payback on a legacy migration project is from 6 to 12 months. The 3 areas from which you can measure your return: most easily and quantifiable are the reduced costs, secondarily, but more importantly, are the softer [but even more important] business benefits.

The migration is a recommended interim step to a planned replacement. Getting the logic, data and screens converted is a step that can be avoided in a COTS implementation—saving time, risk and expense. Also, the COTS project length usually extends over a long period of time—the capturing the saving and opportunity costs will end up funding the COTS project while providing some interim business capabilities. 

Q.  Where do the cost-savings come from and what should we expect them to be?

A.  The cost-savings that come from reduced licensing, maintenance, and specialized personnel are easily quantifiable. Most organizations can also quantify the costs of system downtime and special data center infrastructure [power, air, floor-space, peripherals, networks, etc.]. Harder to quantify, but more important to the enterprise, are the opportunity costs—increases in user capabilities from improved performance, access and functionality.