Migrating/Porting Java/J2EE Enterprise Applications to SAP Netweaver is picking up steam. We will quickly try to understand why. In addition to that we will take a look at the claims which follow. Does this migration actually open up opportunities for the organization? Does the cost of migration justify the move? What are the impacts – downtime? Risks? and most importantly – who do i talk to, to get this done smoothly at a cost which does not squeeze me till i get suffocated. In addition, I have seen how migration projects go on – they just keep extending and keep draining funds without a deadline.. Should i rather stay away?
If you own a software product, chances are that you would have already contemplated migrating your project into SAP so that you can atleast buzz past the first door where the customer is skeptical about your product and the massive amount of changes they need to undergo in their existing SAP backbone which is fueling their business. Inevitably, you need to change your product. Now, changes to your product might mean more customization time, more time to get the product market ready and there is every possibility that this changed product would be only suited for the client you are talking to. The client next door would have a separate need for a similar system and you keep customizing your product at the expense of more time and money and end up making smaller margins. If you are slightly less lucky, as we all feel looking at the greener grass on the other side, then by the time you are ready with the changes, the client might just say – we have had restructuring inside the org and product needs to change again!! There can be many more such situations.
What is the way out?
You would already be thinking by now – Ok then – tell me how SAP can help in such a situation.
Logic is simple. If you start looking at companies which run on SAP, instead of companies which are uniquely different from each other, the amount of customization you would need to do is limited and one time. After the initial set of customization is done and you enable your product to talk to SAP backend, it can just become a plug and play system and you would see more and more clients coming forward to know more about your product, taking up your product since it costs them nothing more to adopt it to their million dollar SAP backend. That is when they look at the innovation in your product, the creativity with which your product does what it is intended to do. Even if your client is using a customized SAP infrastructure, the amount of changes needed to your already-SAP-enabled product will be less. But first things first – your products need to be SAP certified and compatible.
Mindfire – What is it? Can it even do what it claims?
Well, two ways to know the answer to this other than I telling you – Yes we can do it. First, take a smaller product – send it to us for a quote and get a risk free trial of a few days in place. I am sure you would be surprised at two things – at the comparative lower quotes than you would expect from IT majors in India and second, at the expertise and commitment levels of Mindfireans. The second way to know the answer to the question above would be to wait till we at Mindfire finish about 40-50 migration projects and then you can speak to our references and then think about your decision to migrate your product. Time lost can become detrimental but that’s fine. Better be safe than be sorry.
We dont claim to be the best. And we also say NO clearly when we feel that we dont have expertise to do a project. But once we commit to something, we will everything it takes to finish that by then. After all, we have a business to run.
Please do send me if you have any questions and i would be glad to take it up for you.