AWS implementation

Who supported the organization through the migration?

AWS Consulting Partner

0 %

In-house employee(s)/ internal resources

0 %

Independent contractor

0 %

AWS ISV (Independent Software Vendor)

0 %

Not sure

0 %

Of those organizations that used in-house employees, 56% (up from 39% our last study) also enlisted the help of an AWS Consulting Partner. Additionally, 31% sought help from an independent contractor to support their internal staff, showing a rise from 26%. This indicates a continued trend of organizations using external resources to assist with AWS integration projects.

Do you need a contractor to help get your project over the line? Find out what makes a contractor accept a contract offer.

What challenges might you expect when working with a partner?

Keeping the project to budget
25%
Communication difficulties
21%
They struggle to understand our requirements/business processes
21%
Problems defining the scope of the project
21%
They struggle to understand our industry
13%
Keeping the project on schedule/meeting agreed deadlines
13%
None
38%

According to partners, what challenges do end users face when migrating to AWS?

We asked those that work for a partner what challenges their clients commonly face during a migration to AWS—difficulties mentioned this year include:
Lack of technical knowledge in-house to manage and execute the project
35%
Issues with data mapping and migration from legacy system(s)
31%
Incorrect budgeting of the costs involved
20%
Lack of clear project scope, including precise requirements for platform functionality
20%
Issues sticking to the project timeline
18%
Confusion regarding AWS's product offerings, capabilities, and limitations
18%
Difficulties aligning business processes with product features
18%
Underestimating the amount of time required to replace their legacy system
18%
Communication difficulties
16%
User adoption, engagement, and training challenges
16%
Poor data integrity
14%
Lack of change management processes on the client's end
14%
Not sure
12%
Other
4%
We also have insights into the challenges partners face when working with end-user clients, allowing you to address these issues proactively and ensure your AWS project runs smoothly.

Why are organizations choosing to implement AWS?

0 %

The functionality of the product/services

0 %

Desire to move
to the cloud

0 %

Need to increase business responsiveness

Trusted products/services
41%
Desire to reduce costs
38%
Variety of products/services
38%
Ability to integrate with third-party vendors
30%
Ease of migration
27%
Need for global capabilities
27%
Ease of user adoption/user friendly
24%
Lack of confidence in previous cloud service provider
16%
Post-migration support offered
14%

How long do migrations to AWS take?

Our respondents tell us their migration took, on average, 4 months and 2 weeks to complete.

With this in mind, it’s important to ensure you have the skills required to get your AWS implementation over the line. If you lack those skills internally, a short-term contractor with experience in your vertical (or business size) is the perfect answer to make sure your project sticks to time and budget, with consultants often able to help you map out exactly what lies ahead in order to avoid delays.

AWS go-live delays

Under a quarter (22%) of organizations experienced a delay to their scheduled AWS go-live.

What factors caused the delay?

Poor planning prior to migration
38%
Data migration issues
38%
Rescoping of the project/changing needs of the project during implementation
38%
Staff shortage
25%
Lack of skills in-house to manage/work on the project
25%
Poor project management
25%
Delay in training staff
13%
Issues with testing
13%
Issues dealing with partner/consultancy
13%

What are the top challenges faced by organizations during an implementation?

0 %

Lack of appropriate skills internally

0 %

Integrating AWS with other products

0 %

User adoption
challenges

Lack of appropriate skills available in the market
22%
Difficulties managing projects
22%
Rescoping of the project/changing needs of the project during implementation
22%
Loss of productivity during the migration
19%
Difficulties migrating data from legacy environment to AWS
19%
Poor project management
19%
The business was not ready for the change
19%

Under three-fifths (58%, up slightly from 51% in our previous survey) of organizations surveyed encountered implementation challenges stemming from a lack of internal skills, suggesting that there is still a lack of skills in the AWS universe.

Struggling to find in-demand AWS talent with the right skills and industry experience?

Revolent can help. By tapping into fresh talent pools, we can source, train, and deploy delivery-ready AWS talent for all your project needs.

Revolent Group is a Tenth Revolution Group company. The AWS partnership for Revolent is managed through Jefferson Frank, a Tenth Revolution Group company.

Are organizations integrating AWS with non-AWS products?

Results show that 62% of AWS customers we surveyed have integrated their AWS product with a non-AWS product.

What non-AWS products are customers integrating AWS with?

0 %

Microsoft Azure

0 %

Kubernetes

0 %

GitHub

Gitlab
39%
Google Cloud
34%
Snowflake
19%
Databricks
16%
VMWare
11%
Other
18%
‘Other’ responses include on-premise data centers or custom-built applications.

Careers and Hiring Guide

AWS Edition 2025

Key Findings

Our key findings report contains highlights from this year’s Careers and Hiring Guide, plus our salary tables to allow you to compare your compensation or benchmark your teams’ salaries or rates no matter their role in the AWS ecosystem.

Skip to content