Consider this option only if your business requirements are fairly commonplace, standard, and if you're willing to adapt your business processes to align with those of the packaged application. But, recognize the following:

• You will lose the custom functionality inherent within your legacy application and unique to your business.
• You will be dependent on the software vendor or expensive system integrators for enhancements.
• Packaged applications typically take a long time to implement when significant customization is involved.
  
  

• You're willing to wait. It takes a long time to build a new application "from scratch".
  
• You have the in-house expertise required to develop a custom solution, and can make them available for an extended period of time.
  
• You can afford to hire a 3rd party system integrator to develop the solution.
  
  

3. Port the Legacy Application

PowerHouse porting is often used as an interim step for clients that need to further extend their investment in their PowerHouse application for a determinate period of time. CORE Migration’s PowerHouse porting preserves the existing PowerHouse language while the hardware and databases are moved to a different platform such as, Unix. For CORE Migration’s PowerHouse clients, the porting process maintains the existing PowerHouse functionality while providing a low risk, economical short-term solution.

4. Migrate the Existing Application

Application migration, in which the existing legacy application is transformed to a modern computing platform while preserving the core functionality, uses code migration software to automate the process. Migration offers the benefits of "buy" (faster time-to-market) with those of "build" (custom functionality).

To learn more about these alternatives and CORE Migration, get our free business white paper.