Migration and Data
Today, IT systems evolve considerably faster than 10 years ago due to the agile approaches in software development. Consequently, the question of updates has become an essential issue in the decision-making process. It is no accident, i.e., that Microsoft has switched Windows to a so-called „rolling release,” where versions have become an extinct species (which is, by the way, a feature taken from the Open Source world).
But new versions do not only have problems with changes in the front-end, but data also have to be migrated. It is, of course, easiest to have your provider operate your solution through a Cloud, which takes care of the whole problem, including the data issue.
However, relinquishing the sovereignty over your data while only being able to buy rights of use creates an unholy alliance, at least in our opinion. This will, after all, lead to a total dependency on the system provider in every respect.
In-house operation, whether on your hardware or in your cloud, would be the counter concept to the above. Here, the possibility to migrate data within the scope of a service contract is incomparable and hard to beat. Until now, we have always talked about a “migration project,” after all. As the term already implies, a project requires effort and timeframe.
Source Code – future-proof security
Besides the rather obscure licensing models of many providers and the patent situation, there is another important reason why Open Source has become a worldwide success story in recent years: The source code becomes available with the installation. This is not about transparency, but about two aspects made possible by this fact:
Since the source code is made available with the installation, customers are independent of the provider. As long as the respective software is not a niche solution but finds a broad acceptance (as is the case with Odoo), there are other experts able to provide support and customized solutions – the 1,000 certified Odoo partners worldwide.
2) Future-proof security
Since the source is not only available for the adaptations but for the complete system, the community of platform users as a whole becomes independent of the provider. If there are developments not acceptable to the community or if the provider has financial difficulties, the project will continue under a different name as a so-called Fork, as past examples have shown.