Cloud Migration to the right cloud

Strategy and business case

Which workloads will be moved to which cloud, and what will that cost and yield in five years? We also factor in the costs of doing nothing, such as purchasing new hardware or renewing a VMware license. This way, you can see for each workload whether migration is worthwhile.

Migration to AWS, using AWS MAP

For larger migrations, we oversee the Migration Acceleration Program, including the business case and the funding application to AWS. That funding can cover a portion of the migration costs.

Microsoft Azure and Google Cloud

The same approach as with AWS: first an assessment, then a Landing Zone using that cloud’s tools, and then migration in waves. We’ll include your existing Microsoft licenses in the business case.

European and sovereign cloud

We migrate workloads that must remain under European jurisdiction to a European provider, a sovereign cloud, or an on-premises environment. We use a Data Sovereignty Assessment to determine which option is best for each workload.

VMware exit

For each VM, we determine whether it will be migrated to the cloud, placed in a container, or run as a VM on another platform, such as OpenShift Virtualization, SUSE Virtualization, Apache CloudStack, Proxmox VE, or KVM with libvirt.

HPC and research

Computationally intensive workloads and research environments. For NXP, we migrated 22 petabytes of R&D storage to AWS, cutting wait times in the job queues in half. The KNMI now provisions workstations on demand.

Data and database migration

We migrate Oracle, SQL Server, PostgreSQL, MySQL, MariaDB, and MongoDB, among others, to platforms such as Amazon RDS, Aurora, Azure SQL, or Cloud SQL. For each wave, we determine how to synchronize, switch over, and fall back if necessary.

After the migration

After going live, we focus on costs and security. With FinOps, you can see if the business case holds up: at Colect, a three-day analysis resulted in a 43% reduction in monthly AWS costs. We’ll take over management if you’d like.

Analysis and planning

With a Cloud Readiness Assessment, we typically map out your applications, dependencies, costs, and risks within two weeks. For each workload, we recommend a path forward and a target platform, along with a cost comparison. If you’re already running on AWS, we’ll start with an AWS Well-Architected Review. → Cloud Readiness Assessment

Landing Zone

Before the first workload is migrated, we set up the foundation: accounts, identities, networking, logging, security, and cost guardrails, all defined as code. This is usually completed within two weeks. → Landing Zone

Move fast, without disruption

We migrate in waves, starting with the simplest and least critical workloads. For each workload, we choose to rehost, replatform, or refactor. With Re:App, we map out legacy code before modifying it. The old and new systems run side by side temporarily, so that each step can be reversed. → Application Modernization

Manage and optimize

After going live, we monitor costs, performance, and security. With Agentic FinOps, an AI agent identifies anomalies and cost-saving opportunities; an engineer approves every change. Management can remain with SUE through Managed Cloud. → Managed Cloud

From four data centers to AWS. A comprehensive analysis of systems and costs was completed in three weeks, followed by the migration of the entire infrastructure, set up using Terraform. Textkernel now scales with demand without having to expand its IT team. In another project, SUE built a Kubernetes platform on AWS for Textkernel with 99.99% uptime.

HPC to AWS. NXP migrated its High Performance Computing environment, which uses SUE, to AWS to achieve greater scalability and flexibility.

Research environment on AWS. After a proof of concept, researchers set up their own virtual workstations and scale them using AWS CloudFormation, without having to invest in hardware upfront.