Brief Study
This phase gains an insight into the project objective gaining the necessary knowledge of the characteristics of the source information system, its environment and its components. The technical choices for migration in the target environment are evaluated according to their opportunities in this context as well as the different constraints given by Client.

When the brief study is accomplished, the overall migration guidelines are set with production of an inventory of all objects to be transformed. This documents all sources, data files and databases to be migrated to ensure that everything is covered and all objects migrated.

Detailed Study
The inventory set during this phase covers the number and complexity of procedures, programs, transactions, screens, reports, databases. Tables and files are carefully identified, as are program translations and any special considerations.

Planning
Successful transformation depends on proper planning. Tasks are defined and standards are established for the migrated programs. An appropriate migration schedule is worked out based on project priorities and the development and maintenance activities related to the existing system. The secondary objective during the planning phase is to identify external/third party tools and integration issues.

Migration
The process here involves translating programs, translating screens, translating reports and converting databases and files. The migration phase also involves writing new programs for third party tools and integration points/layers such as EDI etc. The phase mainly targets the generation of new programs functionally equivalent to the old programs but stripped of the dependency on the old language, database or computer. It can even restructure programs and database access with uniform standards. The transformation process also limits the redundancy and expansion of code.

Testing
Completion of the transformation process is the testing of the output of the transformed program with the converted output of the original program flagging any mismatches for correction. Every function represented by the test data must be present and working in the converted program. For each combination of source and target programs, a certain number of tests are necessary to check all program conditions. An insufficient number of tests during unit conversion only postpones this requirement until the implementation phase, where runs are longer and more costly. This phase stresses the discovery and correction of errors during unit testing rather than during production runs.

Implementation
The implementation phase covers the following steps:

• Integrating the programs and preparing for system testing.
  
• Updating the transformed system to include current production maintenance changes.
• Converting live production databases and files to operate with converted programs.
• Executing the converted programs with production data.
• Comparing the output with the converted versions of the original output to validate the results.

Our migration service empowers product companies/global software companies/ISVs to:

• Release a product on the latest frameworks such as .Net to J2EE or J2EE to .Net
  
• Migrate to a Windows based product from a Java platform or vice versa
• Re-architect a product to suit different client needs whether a large enterprise or small size business
• Migrate to n-tier architecture from conventional two-tier architecture
• Make the transition from a standalone product to a hosted service model, enabling Software as a Service (SAAS)
• Use AJAX based development, Web 2.0 concept and features to make an application more interactive
• Benefit from Smart Client based development giving an experience of a desktop snappy look and feel but delivered over the web like a rich web application
• Exploit globalization and localization of a product

Read our success stories on how we helped our clients to migrate their products to the latest platforms, frameworks:

• SourceEdge Software Technologies
  
• SourceEdge Software Technologies