Cloud Transformation
Assess, land, migrate and run on any major cloud, with every decision made by an architect on evidence.
At a glance
NGT moves workloads from the data centre to AWS, Microsoft Azure or Google Cloud, and runs them there. Every move starts from evidence and a landing zone as code, runs in waves, and ends in a planned handover.
Discovery data and the customer's own files; one 7R path per workload, signed by an architect.
Landing zone first, then a pilot and parallel waves with go/no-go gates and two weeks of hyper-care.
Monitoring, ITSM, backup and DR, security operations and cost reviews under an agreed SLA.
The cloud journey, end to end
The same arc every time. Start anywhere: an assessment, a landing zone, or operations for an estate already in the cloud.
- 01Assess
- Inventory and dependencies
- End-of-support findings
- TCO and business case
- 02Land
- Accounts per team and environment
- Identity, network, logs and policy as code
- 03Pilot
- One low-risk workload, end to end
- Performance, stability and cost checked
- Lessons back into the runbook
- 04Migrate in waves
- Parallel streams of small teams
- One 7R path per workload
- Cutover with a rollback plan
- 05Hyper-care
- Two weeks of close watch per go-live
- Tuning with application owners
- 06Run and optimise
- Managed service under an agreed SLA
- Security and cost reviews
- Modernise when the case is there
From data centre to a cloud you can run
A whole programme in one picture. Select any component for what it does and the practice behind it.
- Assess on evidenceDiscovery exports and the customer's files in one inventory; an architect signs every decision.
- Land on a foundationA landing zone as code is Wave 0: accounts, network, identity, guardrails and logs.
- Move in wavesThe cloud's own tools replicate, test and cut over, wave by wave, behind a go/no-go gate.
- Run from day oneMonitoring, backup, patching and cost reports are on before the first cutover.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
Problems we solve
Six situations customers bring us, each with the architecture we use. Select one.
Hundreds of applications to move, against a deadline
A data-centre contract ends. Hundreds of interdependent applications, licences tied to hardware and owners in several time zones all have to move.
- Landing zone and pilot first, then parallel five-person streams
- A 7R decision per workload, scored for complexity
- A green flag before go-live, two weeks of hyper-care after
Every application moved, replaced or retired by a signed decision, wave after wave, with a rollback path.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
Three service lines
One of NGT's five service pillars. Customers buy one line or all three.
Explore Cloud Transformation
6 pages, each a few minutes to read.
Frequently asked questions
What customers ask first.
Mostly AWS, Microsoft Azure and Google Cloud, with delivery experience on Huawei Cloud and Alibaba Cloud too.
FPT Software is a partner of all five. The method is the same on each: a landing zone as code, a 7R decision per workload, waves, then operations.
Not always. For a handful of servers ready to rehost, a short express path is enough: replicate, test, cut over.
For a portfolio, the assessment pays for itself: dependencies, end-of-support items and applications to retire, ending in a roadmap, a TCO and a first wave.
Both, decided per workload by written rules and signed by an architect.
We modernise where the case is clear and rehost first where a deadline matters more, then modernise once the workload is in the cloud.
The pace comes from parallel streams, not heroics: several five-person teams on one runbook, each moving its own wave.
Every go-live is followed by two weeks of hyper-care before handover to operations.
NGT's assessment accelerator. Our architects run it on the files you share; you receive the reports, the 7R decisions and the wave plan, each signed by an architect.
You never log in and it moves nothing. Its connectors are read-only, every file version is checked by hash, and project data is purged 7 days after the project is deleted.
AI reads and drafts: it reads discovery files and documents, drafts the assessment and cross-checks every statement against its source. Every AI answer is recorded and can be replayed.
Decisions do not come from AI. 7R paths follow written rules, Go/No-Go checks are code, and an architect signs each step.
