Two Modernization Paths

TL;DR

Every workload needs a deliberate path. Stabilize moves priority workloads onto Azure with lower disruption. Transform modernizes applications, data platforms, analytics foundations, and AI readiness where the business case justifies deeper change.

The assessment gave us the evidence. The next decision is not whether to modernize everything at once. The decision is which path each workload should follow so the customer gets value without unnecessary risk.

The Horizons model remains the planning method behind these two public paths: Stabilize maps to Horizon 1, and Transform maps to Horizon 2.

MCEM Stage 2 — Inspire and Design

Modernization path design is the second half of MCEM Stage 2: Inspire and Design. We take assessment findings, overlay the customer’s strategic priorities, and produce a concrete plan that balances fast movement with deeper transformation.

The Two Paths

%%{init: {'theme':'neutral'}}%%
graph TB
  classDef stabilize fill:#0078d4,stroke:#005a9e,color:#fff
  classDef transform fill:#038387,stroke:#025356,color:#fff
  classDef fabric    fill:#742774,stroke:#5a1e5a,color:#fff
  subgraph stabilizePath["Stabilize — move and optimize"]
    H1_VM(["VMs → Azure VMs"]):::stabilize
    H1_SQL[("SQL Server → SQL Managed Instance")]:::stabilize
    H1_FAB(["Supported SQL MI data → Fabric"]):::fabric
  end
  subgraph transformPath["Transform — modernize and scale"]
    H2_APP([".NET → Containerized services"]):::transform
    H2_SQL[("SQL Server → Azure SQL Database")]:::transform
    H2_FAB(["Supported Azure SQL data → Fabric"]):::fabric
  end
  H1_VM --> H1_SQL
  H1_SQL -.-> H1_FAB
  H2_APP --> H2_SQL
  H2_SQL -.-> H2_FAB
  style stabilizePath fill:#e6f3ff,stroke:#0078d4
  style transformPath fill:#e6fafa,stroke:#038387

Stabilize

Move workloads to Azure with minimal application changes. VMs migrate to Azure VMs. SQL Server databases migrate to Azure SQL Managed Instance when compatibility and operational continuity matter.

Choose Stabilize when the priority is to:

• reduce datacenter dependency quickly;
• lower application change risk;
• right-size infrastructure using assessment evidence;
• improve operations with managed patching, backup, monitoring, and resilience;
• enable Fabric mirroring for supported SQL MI tables when analytics is part of the strategy.

Transform

Re-architect applications and data platforms for cloud-native benefits. .NET Framework applications are upgraded where appropriate, containerized, and paired with managed Azure data services such as Azure SQL Database.

Choose Transform when the priority is to:

• increase product agility and release frequency;
• support elastic or unpredictable demand;
• reduce operational overhead where PaaS and serverless fit the workload;
• establish modern DevOps and deployment practices;
• build richer governed data products in Fabric when readiness checks pass.

Sequential, Parallel, or Both

The paths are not a rigid sequence. Strategy decides which pattern fits:

%%{init: {'theme':'neutral'}}%%
graph LR
  classDef stabilize fill:#0078d4,stroke:#005a9e,color:#fff
  classDef transform fill:#038387,stroke:#025356,color:#fff
  classDef phased    fill:#742774,stroke:#5a1e5a,color:#fff
  A{"Workload<br/>assessment"}
  A -->|"Stable, low-change"| S(["<b>Stabilize</b><br/>Move and optimize"]):::stabilize
  A -->|"High business value,<br/>needs agility"| T(["<b>Transform</b><br/>Modernize and scale"]):::transform
  A -->|"Move first,<br/>modernize later"| BOTH(["<b>Stabilize → Transform</b><br/>Phased"]):::phased

• Some workloads stay Stabilize because they are stable, well-understood, and do not need cloud-native change.
• Some workloads go directly to Transform because they are customer-facing, high-priority, or need capabilities that only a modern platform provides.
• Some workloads start Stabilize and evolve to Transform once the team is ready and the business case is clear.

Strategy decides, not technology

The worst modernization programs try to modernize everything at once. The best ones let business strategy determine the right path for each workload and accept that not every system needs to become cloud-native.

Deep Dives

Explore each path and its Fabric integration in detail:

• Stabilize Workloads
• Stabilize + Fabric
• Transform Platforms
• Transform + Fabric

← Back to Assessment · Skip to Execution →