Real time to value with migration planning

I have blogged about technology migrations and our migration services a couple of times and I come back to this topic again because every enterprise needs to address the issue of migrating at some point or another. In today’s ultra fast world new technologies are introduced daily to improve agility and ease of use for customers of all kinds. Users are demanding faster and simpler tools to do their jobs and at the same as consumers, setting the bar for more efficient access to information.

Our customer successes revolve around three main attributes; a wining value proposition for the specific solution being acquired, a flexible and value oriented financial model, and finally the ability to implement the solution which often requires a replacement of an older generation of the incumbent solution. This third piece can be tricky and has to be  completed quickly and effectively to gain the value from the procured solution. Several years ago IBM recognized this important need and established a dedicated migration team that specializes in the science and art of the migration process. Now with insights from 100’s of examples, automated tooling to accelerate the process and migrating best practices, this team has become an important competitive advantage. One in which IBM provides as a no charge service … an investment in our customer’s success.

There are several steps the migration team commonly follow. First is a “Discovery” to scope the level of complexity and impact the migration to the IBM solution would entail. Typically done remotely over a few hours, the team will walk the client through a series of ‘discoveries’ to map out the effort and uncover any unique and complex areas. With mutual agreement to move forward, the discovery is followed by an “Assessment” which occurs on-site and involves usually two people over a 1 -2 week period. Yes a significant investment of skilled individuals, but a critical step in ensuring the new solution will be providing value in as quick a period as possible while at the same time minimizing business risk. Within the assessment effort the team will apply the automated tooling and experience and often show through POC’s the effectiveness of the approach and a forecast of how the overall effort can be managed. Armed with a detailed ‘blueprint’ or step by step approach the client now has a full picture understanding of the impact of the new solution choice.

In an effort to accelerate this process and simplify the initial stages, the team has recently launched an automated “Discovery” tool, which allows clients to gain insights on the migration effort very early in their decision analysis to upgrade or replace an existing piece of technology.


And here are a few tips to guide you through the estimation process:

  • Complete the Online Migration Questionnaire that most closely matches your current requirements..
  • In most cases, the question uses industry standard terms that Java EE architects and developers will understand;
  • Answer all of the questions as accurately as you can based on your current application inventory..
  • If you think the estimate is too low or too high then, try the migration assessment again tuning it to classify your applications and infrastructure

This ballpark estimate is the first step in the IBM migration process and is based on the team’s experience and IBM historical data. And it’s ideal for budget assumptions and planning. Now this of course is just an estimate and needs to be validated to gain confidence and budget assurance for your project.

Categories: Migration

Tags: , , , , , ,

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: