The effort associated with large scale software platform migration for both data and application logic can be enormous, daunting and prone to business, schedule and financial risk. Most common approaches to this migration effort in the industry are technology focused, often because the services are delivered by the technology platform providers.  

Indellient offers better outcomes by driving the migration of the business process not the technology features. This approach provides customers with a more realistic migration process and budget, and also a more cost-effective and supportable technology solution in the future.

Catalog / Organize

The Indellient migration process starts by organizing the electronic assets distinct functional classes. Each class contains applications which fulfill a common business function, and can in some cases include with a class applications which have been implemented in differing ways to meet that common business objective.  During this stage an effort is also made to filter out assets which will not ultimately be migrated to the new platform due to obsolescence or inactivity.

Stratify

The next key phase of pre-migration activities is to stratify all electronic assets further into migration sub-categories.  Each sub-category contains assets that can be handled in an identical fashion in terms of:

• Target technology components
• Design migration approach & philosophy
• Data migration approach & philosophy
• Application migration timing priority

Plan

The first element of the planning stage is to establish a Rough Order of Magnitude (ROM) estimate for the entire migration activity.  The ROM cannot be treated as a final estimate of the work to complete the migration due to the lack of a detailed design effort at this point in the project; however, the ROM can be used to make appropriate decisions regarding ROI for proceeding with the migration, assignment of resources and additional filtering on the assets that will be migrated.

Following ROM development, a detailed project plan for implementation will be generated in concert with an assignment of roles and responsibilities between Indellient and client team members.

Migrate

The migration phase of the project entails those activities required to configure / establish the target application, tailor that environment and / or develop custom application code if required by the Target Application Class.   The phase starts with detailed business stakeholder interviews for each application within a class in order to make a final assessment on the migration strategy for the Target Application Class, and to identify any application specific roadblocks.    The interviews are followed by development of a high level design specifications and an iterative code development process if required.

Deployment

The Deploy phase comprises the activities to implement each electronic asset in the new environment.  After the deployment of the application itself (if not already in place), the legacy data is transferred. In most cases a selection of third-party tools are available from business partners of Indellient.  The final two elements of the deployment phase after data transfer are the training of the users or trainers of the users and ultimate support of the assets in the new environment for a range of 60 to 180 days.