Cloud Migration

To understand where you're going, you need to know where you came from.

This philosophy helps me to understand companies and their information systems.  To understand a company, you have to understand its DNA. The company's DNA is the will to build the creator and the developments according to what it does and what it wants to do.  It is the passage of witness (handover) between the creator of the company and the entrepreneur who will develop it.  The information system reflects this DNA and the evolution of companies.  This SI evolution of information systems is why Enterprise Architect builds an As-Is, a To-Be, and the roadmap to go from one to the other.  Migrating to the Cloud requires knowledge of one's As-Is. Otherwise, the migration corresponds to the creation of a new company. 

Therefore, joining the Cloud requires an understanding of the As-Is and an understanding of the context and, more precisely, the regulation that impacts business.  Indeed, this DNA depends on the existing, it is the determined and functional component of the system that comes to us from the past, the strategic, it is the intentional part that gives us an intentional future, and the daily constraints, internal and external that reality imposes on us. It is the component that impacts the present.  Therefore, the decision to move to the Cloud is, above all, the decision to migrate from As-Is to To-Be. AWS or Azure or Google?  These three companies all offer Cloud solutions. So what are the differences?  The differences come in the way of offering these services.  Like any human enterprise, this way also depends on the DNA of these companies.  AWS's DNA is online sales at a very high level. Microsoft's is integration with tools on devices, and Google's is information sharing.  Thus AWS offers a wide range of services in the image of the major retailers. Azure facilitates the integration with Office and google simplifies storage and sharing of information.  DNA is to be taken into account in the choice of your partner to optimize your future because all these platforms allow migration.  In conclusion, AWS or Azure or Google, is it the question?

To migrate, I would advise a classical approach, but not always applied:

• Knowledge of one's As-Is
• Functional and technical knowledge of each application As-Is (cloud native for example)
• An understanding of the context including its regulatory constraints
• A mapping of the company's DNA and their cloud provider (a hybrid solution is therefore possible)

 Forgetting some of these parameters increases the risk of migration failure or delay.