Few objects such as Connectors could be mapped directly from Waveset into Oracle Identity Manager as the same concepts exist in both platforms. Email Templates and Task Scheduler could be migrated with minimum effort. But the majority of objects with heavy dose of business logic require significant effort to re-develop in Oracle Identity Manager. They could potentially be replaced by out-of-box and customized Process Forms, Adapters and Provisioning Processes with features split or merged from different Oracle Waveset objects. Sounds quite sticky and rightly so. In my opinion having automated tools do this re-engineering for you is certainly possible but it would be very difficult to achieve with reasonable precision and accuracy. These "translations" are really a case-by-case battle, not to mention having to ensure performance and scalability in newly generated code. Y2K tools and vendors should enter this market!

The success of migration is not determined by being able to map every single Oracle Waveset object onto its Oracle Identity Manager equivalent but rather by having the business process successfully implemented on the target platform. The termination example is a relatively simple use case. For example, if you have scenarios involving approval workflows (and most customers do have them), they add a few more layers of complexity to the picture.

Besides the migration effort itself, there are also other challenges that Oracle Waveset customers need to keep in mind when moving to a new platform:

1. A smooth operational transition
The migration effort calls for both implementation of a new solution and the operational transition. Customers of Oracle Waveset need to ensure a smooth transition while at the same time continuing to support the existing solution and even investing further to meet evolving business needs. Tall order.

2. Consider migration with improvements
Companies often choose to leverage the migration opportunity to find ways of adding new features and improving existing implementations. Some say they do this in order to streamline business processes, reduce operational costs and improve performance. Others say they do this to justify the budget. The truth is in between (and out there). Improving life while moving to a new platform is even a taller order.

3. Select the right implementation partner
Due to the nature of work and above challenges, migration projects call for professional business planning and execution, subject matter expertise and deep product knowledge. To have a well-designed plan and resources from the right implementation partner with both old and new product knowledge is the key to success. (Our supercomputers borrowed from the National Security Agency) tell us that you, dear reader, might be interested in hiring us to hep you with migration. Kittens are optional).

There is no rush to take on the migration, but it’s never too early to start planning. Now is the time to know your options. It's also interesting to widen the scope of inquiry a bit and take a look at the latest advancements in Identity Management marketplace. To help you get started, we will review some of the available migration tools and discuss best practices of pre-migration preparation. Stay tuned.