• 0203 912 0170

  • contactus@transactts.com


Why Migrate to AWS? (Technical Blog Series)

July 9, 2022 - Gordon Scobie

1-3 v.2


Welcome to this technical series on Migrating to AWS. This series talks about the process of migrating your existing website to AWS. You will learn about on-premises constraints, AWS tools for migrations, phases of migrations, creating your AWS account, Database Migration Service (DMS), migrating and backup with CloudEndure, moving complex data, and what to do after migration.

This first post will introduce migrating to AWS and what it can do for you.


What is involved in a migration?

Migrating to AWS Cloud is the process of moving data, applications, and services from your existing infrastructure to AWS. It is sometimes a long and complex process that requires planning, evaluation, analysis, and execution.

Are you considering moving your business to AWS, or are you at the first stage of your cloud migration journey? The following are some reasons why AWS cloud is perfect for you:

Cost-effective – When you host your applications on a physical server, you pay for all the resources needed for it, such as electricity, a cooling system, etc. However, on the AWS cloud platform, you only pay for what you use. This results in business cost savings since you do not have to spend money on maintaining your IT infrastructure.

Scalability – With the AWS cloud platform, you can quickly scale up or down depending on your business needs without investing in additional hardware or software licenses. This helps businesses save money while operating efficiently.

Security – As mentioned above, when using the AWS cloud platform, there is no need to invest in extra software or hardware licenses which reduces the overall cost of operation as well as ensures that all your data is secure.

Operational Resilience – an on-premise infrastructure requires regular maintenance and updates. Once you migrate to AWS, cloud professionals manage the servers and AWS doesn’t have scheduled maintenance windows or downtime due to hardware failures. This means your applications will always be up and running — all the time.


Constraints of an on-premise environment

On-premises constraints can be a challenge for organizations migrating to AWS. Here are some of the most common issues we see:

Capital Expenditure – Capital expenditure is required for setting up an on-premises data centre, including hardware and software investments. In addition, you also need to pay licensing fees for operating systems and applications that run on your servers.

Limited capacity – You only have as much capacity as you’ve bought or rented. Therefore, it will cost you more and possibly add to your lead times if you want more.

Limited choice of Operating System (OS) – You can only run one OS per instance. So if you want to test something new like Windows Server 2016 or Oracle Linux 7, it will take longer and is more expensive than running on AWS EC2 instances.

Poor performance due to limited resources (CPU/Memory) – With an on-premises environment, there are limits on how much CPU/Memory you can use, impacting performance when dealing with large amounts of data.

Low Scalability And Performance – An on-premises data centre has its own set of scalability and performance limitations. It is not easy to scale up an on-premises data centre as it requires additional infrastructure and hardware investment.


AWS Tools for Migrations

AWS Tools for Migrations is a collection of tools that can be used to manage your AWS resources, including the ability to migrate workloads between AWS regions. The tools include:

AWS Migration Hub – An online service that helps you assess, plan and execute migration projects, including cost optimization and TCO tools.

AWS Server Migration Service (AWS SMS) – Use AWS SMS to migrate workloads running on physical or virtual machines. You can use AWS SMS to migrate your applications and operating systems without having to stop them during the migration process.

AWS Database Migration Service (AWS DMS) – Use AWS DMS to migrate large amounts of data between databases in different locations.

CloudEndure - CloudEndure is a cloud migration service that can automate the migration of your workloads to AWS. CloudEndure’s patented technology provides rapid, safe, and cost-effective migration of applications to AWS.

AWS Snowball Edge – Use AWS Snowball Edge to transfer large amounts of data into and out of AWS using portable storage devices, like USB flash drives and hard drives, rather than connecting directly over the Internet or a virtual private network (VPN).

AWS Schema Conversion Tool (STG) – STG is a command-line tool that converts MySQL schemas and data into PostgreSQL schemas and data.

AWS DATASYNC – AWS DATASYNC is a file transfer service that enables you to move data between your on-premises data centre and Amazon S3.


Migration Strategies

The process of migrating to AWS is complex, but it doesn’t have to be. The key is to start with a plan and understand where your organization is on the migration continuum.

The 6 Rs are a way to think about and plan for your company’s data migration. The six key steps in the process are:


The 6 Rs of AWS Migration

Retire –  What is the oldest, most obsolete version of any application? If it is still running, you should retire it as soon as possible.

Retain – Make sure that all of your data is retained at all times. This means backups, archives, and more.

Rehost –  Move your data to a new platform without losing its value. This includes all applications, services, databases, and files.

Replatform – Take advantage of new technologies by repurchasing them or migrating them from one platform to another (for example, from Oracle to MySQL).

Repurchase – Purchase new software licenses or upgrade older versions of the software so that they can connect with the new system.

Refactor – Clean up old code to work better with the new system (for example, fix bugs).



When migrating to AWS, you’ll want to start with a plan.

Detailed documentation is key to everything. Document everything as best you can. You should have a complete inventory of all your systems and applications being migrated over. You should include things like:

What services are being offered? For example, do you have any databases, file servers, or other servers? Do they need to be virtualized? Do they run on Linux or Windows Server?

How many users are using each system? This will be helpful when deciding how many instances should be created for each service in AWS.

Documentation makes it much easier to understand what your infrastructure is supposed to do, making migration easier when it’s time to move your business.



The key takeaways from this article are first to do your research and second to plan. Research everything you can to get an idea in your head of how you want things to look and work – both on AWS and in-house. You need to understand how Amazon’s services work, what they cost, and how they can help you achieve your goals.

Once you have thought through these things, create a plan that outlines your migration strategy, including what AWS services you will use and why, which applications should be moved first and why, and so on.

In the next blog on Migrating to AWS series, we will go over how to migrate your business to AWS cloud, which will include a step-by-step guide on how to get started with migrating your current applications and data onto AWS.

1 thought on “Why Migrating to AWS? (Technical Blog Series) – 1/3”

Leave a Comment

Your email address will not be published. Required fields are marked *