Home >> Services >> Migration of Legacy Applications

Migration of Legacy Applications

Partial Migration of Legacy Applications

Often, applications at the end of their life-cycle are missing critical functionality. Modifying the application may not be possible due to missing source code, lack of documentation or unavailability of the vendor.

However, organizations may not be ready for a complete migration, instead, wanting to protect their investment and prolonging its life a little further. Brainwave recommends a partial migration in this scenario.

Stage 1: Import data from the legacy application into Brainwave.

Brainwave provides connectors to major databases such as Oracle, Microsoft SQL Server and MySQL. Additionally, any data which is available in Microsoft Excel or Comma Separated files can also be imported into Brainwave. Foreign key relationships and cross-references are maintained while importing the data. Moreover, once the data is imported, additional attributes or relationships can be added on a per record basis.

Stage 2: Implement new functionality in Brainwave.

New features which cannot be implemented in the old application can be built as new apps on Brainwave. Since all apps share the same Brainwave server infrastructure, the incremental hardware and software cost per app is zero.

Stage 3: Synchronize changes between applications.

Brainwave is capable of using web-services to import and export information. Assuming the legacy application supports this functionality, changes there can be pushed to Brainwave periodically.

Complete Migration of Legacy Applications

Brainwave provides services to migrate legacy applications to the Brainwave Platform. Typically, the process involves 3 stages.

Stage 1: Import data from the legacy data store into Brainwave.

Brainwave provides connectors to major data stores such as Oracle, Microsoft SQL Server and MySQL. Additionally, any data which is available in Microsoft Excel or Comma Separated files can also be imported into Brainwave. Foreign key relationships and cross-references are maintained while importing the data. Moreover, once the data is imported, additional attributes or relationships can be added on a per record basis.

Stage 2: Implement functionality as Brainwave apps.

Implementing legacy functionality can be cumbersome and unwieldy. Since all data in Brainwave is available to all applications, you can choose to selectively implement key features as individual applications in Brainwave thereby staggering the development process to your preference. In the meantime, basic operations such as creating, reading, updating and deleting data is still possible using tools provided out of the box.

Stage 3: Switch over from legacy app to Brainwave.

Once the new application infrastructure is ready, you are free to switch over to Brainwave.