If you think that replicating all of your databases in cloud will be a good solution, think again. A better approach would be creating a functional database set on cloud to avoid complexity of the aftermaths of lifting and shifting of databases.

Database normalization as a best practice in multi-cloud architecture can be a better concept within the cloud migration strategies in coming times.

Database normalization is the process of plummeting redundancy of the databases themselves, to create a set of databases that are more focused on catering the business application requirements and for data analytics.

The challenge is that databases and data slated to move to the cloud are overly complex and full of redundancy. Most people moving that data to the cloud just want to replicate the databases to the public cloud destination—a huge mistake, and here’s why.

I understand that most budgets are limited and that the cost of moving and combining data to cloud-native and noncloud-native databases is much higher than simply pushing bad database architectures to the cloud. However, I also understand that you’re better off figuring that out as you move to the cloud, rather than having to fix it later.

If you don’t, you’ll have to migrate data twice: First lifting and shifting to a public cloud or clouds, then having to loop back and fix things once you figure out that the database architecture in the cloud is not optimized (because it’s overly complex, or redundant, or too expensive).

What an IT manager with the responsibility of cloud migration in the company should do for such requirements ???

1. Inform your management about the strategies of migration and justify the cost it will incur by creating a TCO vs ROI statement. It is required as you will spend minimum twice as much for the migration and normalization, including changing applications to process the new database. If management team is not so keen on providing the budget it requires, explain the risks and future costs.
2. You need to also get DBAs onboard with fluency in existing database, cloud-native database options, database design, data security, governance and data migration processes.
3. Planning the migration will be the most crucial part of the entire migration exercise. Selection of the cloud platform to the databases changes and selection of new or existing ones to use in the environment, will play a crucial role. If you’re miss out selecting the right middleware while planning and execution, it will have to be redone.