How to manage the technological legacy

We recommend changing by layers or making it new but little by little, gradually transferring old things to the new model


Below we reproduce an excerpt from the interview that they conducted with us in the Emprendedores magazine. You can read the full article here:


Whether we turn to SaaS or if we talk about custom tools, we may find ourselves with the difficulty of adapting new solutions with what we already have implemented in our business. Normally companies already have systems designed to control the business and its departments, but not to provide customer service. That ERP connection from the 90s with the new e-commerce platforms, CRM, etc. It is one of the great problems in execution, in addition to the adjustment in the organization and the culture of the company What to do if we are in that position? Do we eliminate everything we had before? From MIGRATION we are more in favor of making transitions by layers rather than doing a Big Bang because the latter does not usually work. We are in favor of changing by layers or making it new, but little by little, gradually transferring old things to the new model. Trying to change everything old for something new is much more complicated, more expensive and you are not taking into account that throughout that period your own client is changing and evolving. Our recommendation is to look for a partner that works in a modular way, that is, that applies Agile as a work methodology and that is applying modules. I mean, now I do this, then I do this, then this … That it is not a monolithic structure and that they work fast.


This website uses its own and third party cookies. If you continue to browse we consider that you accept their use. You can change the settings or get more information here.