EBS Transformation Strategy. Cloud Migration or Re-implementation
Systems strategies are constantly being renewed and in today’s day and age there is a proven need to move to cloud services, for a number of reasons that we do not intend to go into in this article, but in our vast experience in the market we always come to the crucial question, do we migrate to the cloud or do we re-implement?
This is not a casual question or one that should be passed over without analysis. In fact, before starting any change project, this question is fundamental, whether we are going to the cloud or simply upgrading to a new version.
The key points to consider are:
How standard is the product?
Does it currently meet my needs without trauma to it?
How much effort does it require to maintain its performance?
By looking at each of these questions we should have clarity on the answers and be able to measure those values.
If the current operation of the system requires a lot of effort to operate, think of the effort as the time my staff must invest in keeping the system running, whether it be patching, software changes, data adjustments. If the effort is definitely great, it is time to review whether what is required is to re-implement the system to correct its configuration from scratch, the system should work as freely as possible without intervention by development or new configurations, if these are permanently changing, even if I switch to cloud I will have the same problem and what will generate is a cost in the cloud operator that will be transferred to me as it is not a standard process of the application.
The second question may sound similar, but while in the previous one constant changes had to be made to make it work, in this one what we want to know is if the system that is not asking for changes meets what I really need to operate, the information it delivers is sufficient to fulfil my obligations and allows me to make decisions at the right time, if this is not the case, it means that there are many manual processes that are done once the information is received and it is generating burden to my staff, then I do not have a system solution to help me but it is burdening me in operations that should be solved by the system itself, in this case it is time to think about a reimplementation.
And finally, how standard is my product, are there many changes that I made to it to make it work now, how does it do it, what is going to happen when I have a bug tomorrow, do I have enough knowledge in my team to support the system? We must remember that systems change every day and new versions are released, or applications that can help me improve my system, when we have too many customisations this is tying us to a system directly and could hinder future change or the same support by not having the staff to understand the changes made. EBS is developed with best business practices in mind, so the ideal is to adapt to these flows without major changes.
In conclusion we should think about a re-implementation, if we permanently have to make adjustments to our application for its operation, if in the day to day operation we have many traumas because the information that is delivered must be manipulated or if our application looks like something else and not the EBS system that was initially contracted, if we do not have any of these problems we are ready for a migration to Cloud.