The AWS Migration Acceleration Program (MAP) is AWS’s migration program, featuring a structured three-phase approach and potential funding for selected migrations. SUE guides you through the “assess,” “mobilize,” and “migrate” phases (modernize), builds the business case, and works with AWS to determine what support is available for your migration.
MAP funding is a good reason to make a decision now. It is not a reason to migrate everything.
For each workload, we determine whether migration is worthwhile, what dependencies exist, and how to prevent costs from rising after the migration. Not every workload needs to be migrated, and not every application requires the same approach.
SUE combines expertise in legacy environments with cloud native engineering. Business logic is often deeply embedded in legacy applications, and dependencies aren’t always documented. That’s why we look beyond the standard questionnaire.
You'll receive a business case outlining the current costs, the expected AWS costs, and the investment required for the migration. After each phase, you'll decide whether it makes sense to proceed.
For eligible workloads, AWS may finance a portion of the initial migration costs. What is possible depends on the scope, workload, business case, and AWS approval. We’ll explore this during the assessment.
AWS MAP consists of three phases: assess, mobilize, and migrate & modernize. SUE breaks these down into six steps, ranging from an initial assessment to post-migration management and optimization.
01
We'll assess your current situation, business drivers, and migration goals, and determine whether AWS MAP is a good fit and which workloads qualify.
02
We work with AWS to define the scope. We identify applications, dependencies, and expected AWS costs, and use that information to build the business case.
03
For each workload, we determine the migration strategy based on technical feasibility, risks, costs, and operational impact.
04
We're laying the groundwork: landing zone, identity, network, security, governance, monitoring, Infrastructure as Code, deployment processes, and operational agreements.
More about landing zone05
We migrate according to the chosen path: rehost where speed matters, and replatform or rearchitect to containers or Kubernetes where that adds value.
More about Application Modernization06
After going live, we focus on costs, performance, security, and availability, and we provide advice on rightsizing, contract types, and further automation.
More about AWS ConsultancyWould you like to read the background information first? The guide “ Cloud Migration ” outlines the strategies and pitfalls. To learn how SUE approaches the entire migration process, visit the page Cloud Migration.
A well-reasoned business case
Lower risk of migration
Potential funding from AWS
A Foundation for Modernization
01
SUE is familiar with both legacy application landscapes and cloud native platforms. This allows us to quickly identify which workloads can be migrated directly to AWS, which ones need to be adapted first, and which ones are best modernized in phases.
02
We don't just rely on standard models. We take into account compute, storage, networking, licenses, usage patterns, performance requirements, and management to ensure that the business case remains valid even after the migration.
03
High-performance computing, large-scale storage environments, end-user computing, and applications with heavy dependencies. At NXP, SUE migrated the HPC environment to AWS.
Read the NXP case study04
Sometimes migrating first is the right move; other times, containers, Kubernetes, or Managed Services make more sense right away. We decide on a per-workload basis.
Textkernel, a provider of AI-driven recruitment technology, was running on four data centers worldwide. Costs were rising, and many processes were manual.
Within three weeks, SUE analyzed the systems and costs and compared the on-premises situation with a migration to AWS. SUE then migrated the entire infrastructure to AWS. The AWS environments are set up using Terraform and are updated via merge requests, so very little manual work is required on an ongoing basis.
Read the full case study: A flexible and scalable future for Textkernel through a Cloud Migration to AWS.
"Textkernel has taken a strategic step toward a future-proof IT infrastructure in collaboration with SUE, allowing the organization to focus entirely on innovation rather than infrastructure management. SUE's in-depth knowledge was decisive in this regard."
SUE is a Dutch cloud native solutions partner that modernizes mission-critical applications, reduces cloud costs, and manages your platform. Specialists in Linux, Kubernetes, and the cloud.
29+
Years Experience
150+
Engineers and consultants
1.150+
Certifications
ISO
9001 & 27001
500+
Projects
75+
Research papersTell us which workloads you want to migrate. We'll work with AWS to determine if MAP is a good fit and schedule an exploratory meeting.
Tell us which workloads you want to migrate. We'll work with AWS to determine if MAP is a good fit and schedule an exploratory meeting.
* required
