Platform work where the security baseline is part of the build
Cloud platform and migration is the work of building a cloud foundation your team can operate and moving a known set of applications onto it. SEYA Group takes a program from inventory through landing zone to cutover, so that every application moves on a documented plan with a shared foundation underneath. Identity, network boundaries, and logging are part of that foundation.
For migration programmes where security is not the driver, our sister company Cloud Architects Expert leads the architecture and move.
Who this is for
CTOs and heads of infrastructure who have decided to move and now need the move to happen without a surprise bill or an unplanned outage. IT project managers who have inherited a migration with a date attached and an incomplete inventory. Solution architects who need the account structure, network, and identity design settled before the first workload lands.
If the open question is still whether to leave the data centre at all, start with cloud adoption. This engagement begins once a move is the working assumption.
Problems we solve
- An estate that is only partly inventoried, with dependencies nobody has written down.
- A cost case built on list prices that has not been checked against how the workloads actually run.
- Migration work that is about to start before accounts, network, identity, and baseline controls exist.
- A move between clouds, or from a hosting provider, where the current environment was never captured as code.
- Applications that depend on databases or services that must stay on premises for now.
What you get
- Platform recommendation. A written choice of platform, account structure, and tooling for the workloads in scope, with the options considered. Your team keeps the decision.
- Migration cost estimate. An estimate of what the in-scope workloads will cost to run on the target platform, so the business case can be reviewed before build starts.
- Landing zone. The accounts or projects, network, identity, logging, and baseline controls that migrated workloads land in, built as infrastructure as code and handed over with its documentation.
- Discovery and wave plan. Every application and its infrastructure listed, placed on one path (rehost, replatform, repurchase, refactor, retain, or retire), and grouped into waves with the preconditions for each.
- The migration itself. The agreed path carried out for the applications in scope, including data migration, connectivity to anything that stays behind, and testing before and after cutover.
How an engagement runs
- Assessment call. You describe the estate, the deadline, and the constraints. We agree what discovery needs to cover and who needs to be involved.
- Discovery and design. We inventory applications and infrastructure with your teams, draft the target design, and produce the cost estimate and wave plan for review.
- Landing zone build. The foundation goes in as code, is reviewed by your security and network owners, and is documented for your operators.
- Migration waves. Applications move in the agreed order, each with a test plan, a cutover window your business signs off, and a rollback path.
- Handover. Runbooks, code, and access are transferred, and the open items for any refactor work are written up for the next phase.
Technical scope
SEYA has carried out migrations onto AWS, Microsoft Azure, and Google Cloud, including cloud-to-cloud moves. Foundations are built with HashiCorp Terraform, with Packer for machine images and Ansible for configuration where the estate calls for them. Rehost work has used AWS Migration Hub and CloudEndure; container paths have used Docker and Kubernetes. Hybrid connectivity to on-premises databases, autoscaling groups, and load balancer configuration are part of the move when the applications need them.
What you need in place
A named decision-maker for the migration, access to the current environment and its documentation, and security and network owners who can review the landing zone design. Cloud accounts are opened in your name and billed to you. Where an application needs redesign before it can move, discovery says so, and that work is scoped separately.
Out of scope here: deciding whether to move at all, which is cloud adoption; rebuilding an application onto a cloud-native design, which continues under cloud-native development; and security checks inside your delivery pipeline, which is security and DevSecOps. A managed operations contract or a compliance certification is not part of this engagement.
Related work
- Boeing: migrating the GoldCare application stack to Azure with connections to on-premises databases
- Broadcom: a cloud-to-cloud move of API management infrastructure from AWS to Google Cloud
- Clearly: moving from Rackspace and on-premises hosting to AWS, with Terraform and autoscaling
Questions buyers ask
How long will the migration take?
That depends on how many applications are in scope, how well they are documented, and how much change each one needs. Discovery produces the wave plan, and the plan carries the dates. We will not quote a duration before we have seen the estate.
Who owns the cloud accounts and the code?
You do, from day one. Accounts are created in your organisation, the infrastructure code lives in your repositories, and SEYA works through access you grant and can revoke.
How do you work with our operations team?
Alongside them. Your operators review the landing zone design, sit in on cutovers, and receive runbooks written for the environment they will run. The aim is that nothing depends on us after handover.
What about downtime during cutover?
Each application gets a cutover window and a rollback path agreed with its business owner before the move. Acceptable downtime and data-loss limits are set per application in that plan.
If you have a set of applications to move and a deadline to meet, book a migration assessment call. We will tell you what discovery would need to cover.
Contact us
Send an enquiry about a cloud, platform, data, or reliability engagement. Marketing email is a separate choice on the form.