It is undeniable that the cloud migration can come with tons of benefits. According to Triangu for business owners, it has things to do with the scalability, reliability, flexibility, productivity, as well as cost effectiveness in the long run.

Regardless of the promising prospect’s knowledge of the cloud migration strategy, the execution of the migration will come with the strings and challenges you need to face. Not only the security challenges, but also different types of factors like connections, adaptations, effectiveness, and so on.

In the end, cloud migration indeed comes with the perks and benefits. But to get there, you will need to break all of the obstacles that might hinder the process of migration. Therefore, it is important to see the cloud migration examples from other companies so that you will learn some important things from them.

From Bare Metal to Cloud – Betabrand

Betabrand is a crowd-funded retail clothing e-commerce company. The company planned to migrate from Bare metal to Cloud.

The Betabrand company had issues with the bare metal maintenance difficulties. With their conventional metal infrastructure, it was hard for them to scale their business up. The more crowded their website, the harder they can handle the peak website traffic.

With the Kubernetes or Google Kubernetes Engine, Betabrand bare metal infrastructure was migrated to Google Cloud Infrastructure.

They managed to complete the migration before the Black Friday 2017. and it was a successful migration.

The surge in web traffic happened again in Black Friday 2018. And they could handle it really well. The auto-scaling cloud infrastructure from Google Cloud helped them to handle the loads without any hassle. Since the cloud migration, the company has never met any significant issue in their cloud environment.

There’s a sensible reason behind their success. Before the actual migration process, the company with the help of GKE performed several tests to demonstrate the practices of the migrations. They found out poor results in the code paths when they tested the server in heavy workloads. But they were able to fix the problems before Black Friday 2017. From this study, we must know that series of tests are necessary before conducting actual migration.

Cloud to Cloud – Shopify

If you have been around the internet marketing for a while, you will surely be familiar with Shopify. It is popular because of its e-commerce software platform which has helped hundreds of thousands of small to mid-sized businesses around the world to get online visibility.

To make sure to maintain their wonderful service, Shopify decided to move their cloud-based server to the better cloud environment. They would want to upgrade their infrastructure to provide much better support for their customers.

There are three core things which were implemented in the Shopify cloud migration strategy. They are:

Building Shopify cloud with google

Building “Shop Mover” database migration tool

Upgrading Docker containers and Kubernetes

With those three important aspects in cloud migration strategy, Shopify managed to improve their data center quality so that they can answer the demands from their customers. As a result, the scalable applications boost the company services in various sectors including control, monitoring, reliability, as well as consistency.

Scalability is the main objective of Shopify migration. The cloud-to-cloud migration has helped the company’s servers to meet the heavy workloads. As we know, Shopify often comes with promotion and flash sales where this activity triggered the traffic peak.

Cloud to Multi-Cloud Waze

Waze, as the real competitor of GMaps app has always been offering such competitive features. The GPS-enabled navigation app constantly uses real-time user location data. The users are also able to submit the report to Waze app to suggest the optimization of the chosen routes and tracks.

Although Waze had started their rodeo with the cloud, they quickly found out complications with their older cloud environment. The issues were mostly coming from the production aspect. That’s why the Waze boomers back then complained about the slow loading of the navigating system.

To handle this, Waze decided to operate their infrastructure on multiple cloud providers. They have been using GCP and Amazon Web Services.

To make easier rollbacks, they use open source Spinnaker. Spinnaker eases the engineers to command across the cloud platforms. The good thing here is that both platforms can work together without any hassle.

As important as the GPS system in our life, we know that the slight delay can make the GPS users miss the turning point. Waze could not take the risk. They did their best to avoid downtime, fix the bugs at a rapid rate, and ensure the quality of the production on their part.

We can learn that running on multi-cloud can help us to improve the speed of delivery.

Cloud to Hybrid – Dropbox

Most of us have known what Dropbox is. And if you think that this service has evolved wonderfully these past five years. Then you are totally right.

Dropbox company uses the Amazon S3 (Simple Storage Service) for their house data. Meanwhile, they keep their meta-data on-premise. But overtime, the company wants to avoid the booming in the costs so they decided to bring the data to in-house infrastructure again.

Dropbox built their in-house infrastructure. They moved around 90% of their files back to their own servers.

After seeing Dropbox, we realize that on-premise infrastructure might still be sensible for some businesses. It is so sensible because Dropbox wants to provide fast and reliable data access. And by this time, there is no better way than using their in-house servers with low to zero latency. Cloud services have limits. If Dropbox is too big to take care, the most sensible approach is by building their own in-house network.

That’s why it is fair that we call it a Cloud-to-Hybrid solution.

Bare Metal to Hybrid – Cordant Group

Cordant Group is a global social enterprise which works in various fields such as security, health care, technicians, electrical, recruitment, and so on. People from around the world use Cordant Group and the number of users increased significantly. Then they decided to switch to cloud’s pay as you go as the implementation of Operational Expenses or OpEX.

Their cloud migration was not as smooth as other companies in this list. They initially moved to virtual private cloud on AWS. But the Windows DFS restriction came with access problems. But then NetApp Cloud ONTAP fixed the problem. The issue wouldn’t stop them from moving. The file and storage management were conducted without flaw.

The users were unable to access the files as quickly as they needed to. That’s why the Cordant Group team revisited their strategy. But then, Cordant Group quickly found that Cloud was a much better option to carry their OpEx.


Each case has different things to learn. If you are thinking about cloud migration, consider learning from what they’ve done since not all problems can be fixed by one solution. Check your case on Triangu to find out the best cloud migration strategy for your company.