FPT SoftwareFHNCertificationsReference architectures
Talk to NGT
Cloud Transformation · 01 of 6

Migration

The migration factory, assessment, 7R decisions and FleziLift.

Server Migration Factory
01

How servers move, wave after wave

Replicate, test, cut over, keep the source for rollback. Switch the cloud to see each provider's own tools.

Server Migration Factory
inventory, usagecutoverexportswavesrunbookgo / no-goOn premises · kept for rollbackAWS CloudDiscover and assessOperate · every launched serverStaging area subnetTest networkVPC · a private subnet per zoneAvailability Zone 1Availability Zone 2FleziLift plansHypervisor hostsVMware, Hyper-V, NutanixPhysical serversReplication agenton each serverAWS Direct ConnectMigration Evaluator/ AWS TransformAWS Systems ManagerAmazon CloudWatchAWS BackupAWS ApplicationMigration Servicereplicates, then launchesAmazon EC2test launchAmazon EC2cutover launchAmazon EC2cutover launchAmazon Route 53switched at cutoverAS-IS assessmentevidence L0–L37R strategya rule tree per serverWave Planmove groups kept wholeMigration playbooka cloud tool for each taskGo / No-Goeight written rulesCutover gates−28 to +3 days

Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.

Point at a component to see what it does; select it for the best practice.Open the architecture
02

Assessment: from inventory to roadmap

Three views: financial, technical and operational. Each step ends at a gate where the customer reviews and agrees.

  1. 01Understand
    • Vision, motivations, outcomes
    • Pain points, skills, processes
    • Apps, data, infrastructure, security, operations
    Agreed scopeReview – adjust – align – consent
  2. 02Analyse
    • Current state and dependencies
    • Criticality and business impact
    • Gap analysis
    Dependency and risk mapReview – adjust – align – consent
  3. 03Identify
    • Scorecard per application
    • Transformation priority
    • One 7R path per application
    Portfolio decisionsReview – adjust – align – consent
  4. 04Design
    • Landing zone and target landscape
    • Reference architecture per pattern
    Target architectureReview – adjust – align – consent
  5. 05Establish
    • Roadmap and wave plan
    • Pilot candidate
    • Project organisation
    • TCO cost model
    Roadmap ready to start
What the assessment hands over

An inventory with logical and physical maps, a report per application with migration and run costs, and a roadmap with business cases.

03

Seven paths, one decision per workload

Signed by an architect. Modernise where the case is clear; rehost first when a deadline, such as a data-centre exit, matters more.

PathWhat changesWhen it fitsTypical tools
RetireSwitched offNobody uses it, or another system does the jobUsage data, owner sign-off
RetainNothing, for nowHardware, licence or regulatory constraints; a planned replacementRevisit at the next wave
RelocateThe hosting platform onlyVMware or container estates that move as they areVMware-based cloud services
RehostInfrastructure onlySpeed matters most; end of support; data-centre exitsApplication Migration Service, Azure Migrate, Migrate to Virtual Machines
ReplatformRuntime and managed servicesDatabases, caches and queues a managed service can runAWS DMS and SCT, Azure DMS, containers
RepurchaseReplaced by SaaS or COTSCommodity functions: wikis, BI, ticketingData export and integration
RefactorArchitecture and codeSystems that must scale, change fast or leave a monolithKubernetes, serverless, events
04

FleziLift: NGT's assessment accelerator

Code counts and checks, written rules decide, AI drafts and cross-checks. An FPT architect signs every step.

  • Reads what you shareRFP, discovery exports such as RVTools and CMDB, diagrams and, where shared, source code.
  • One AS-IS baselineEvery value cited to its file and row, graded L0 to L3; gaps become 15 ranked questions.
  • 7R by written rulesA rule tree per server; an architect can override any path, with a written reason.
  • Go / No-Go by code8 written rules per server, wave and project; 7 dated gates from T−28 to T+3.
FleziLift's Go / No-Go screen on a simulated project: a recommendation made by written rules, then each wave with its status
Experts decide; the clouds' own tools do the moving

Customers never log in to FleziLift, and it moves nothing. The migration runs on AWS, Azure and Google Cloud tooling.

05

Who does what in a migration

People decide, the providers' tools move the data, and FleziLift speeds up the reading and drafting in between.

Stage
Architects, engineers and app owners
Cloud migration tools
FleziLift accelerator
01Assess
Architects, engineers and app owners
  • Interview app owners; agree scope
  • Check the inventory with the business
Cloud migration tools
  • AWS Application Discovery Service, Migration Hub
  • Azure Migrate appliance
  • CMDB and RVTools exports
FleziLift accelerator
  • One inventory, each value cited and graded L0–L3
  • Gaps become 15 ranked questions
  • Three independent readings, majority vote
02Decide
Architects, engineers and app owners
  • Architect signs the 7R path
  • Overrides need a written reason
Cloud migration tools
  • TCO data from AWS Migration Evaluator and discovery tools
FleziLift accelerator
  • Applies the written 7R rule tree
  • Risk as probability × impact
03Plan waves
Architects, engineers and app owners
  • Wave order, freeze windows, owners
  • A client captain per stream
Cloud migration tools
  • Dependency maps from discovery data
FleziLift accelerator
  • Move groups from real dependencies
  • Pilot up to 5 servers; early waves 10, later 15
  • Person-day estimate per work package
04Migrate
Architects, engineers and app owners
  • Parallel five-person streams, one runbook
  • Functional, network and performance tests
Cloud migration tools
  • Servers: Application Migration Service, Azure Migrate, Migrate to Virtual Machines
  • Databases: AWS DMS and SCT, Azure DMS, Google Cloud DMS
  • Files: AWS DataSync
FleziLift accelerator
  • No role: the providers' tools move the data
05Cut over
Architects, engineers and app owners
  • Architecture and security review
  • Go-live on a green flag; rollback agreed
Cloud migration tools
  • Monitoring and automated tests on the target
FleziLift accelerator
  • 8 Go/No-Go rules and 7 dated gates, T−28 to T+3
06Hyper-care
Architects, engineers and app owners
  • Two weeks of close watch with owners
  • Handover to operations
Cloud migration tools
  • Dashboards and alerts for the new estate
FleziLift accelerator
  • Playbook and handover pack drafted for review
SourcesNGT Service Offering v2.0 (Mar 2025)NGT Service Offering v3.2 (Jul 2026)NGT DevOps–AI Service Offering (Oct 2026)NGT Azure Service Offering v1.0 (Dec 2024)NGT Google Cloud Service Offering v0.1NGT Cloud Operation Service Offering v0.2 (Jan 2025)FPT Software AWS Cloud Journey Service Offering V3FPT Software Cloud Transformation Capabilities (2024)FleziLift method and runbook (Oct 2026)