.NET Framework to .NET 8/9 Cloud Migration Nordic & EU delivery Direct email access

Move Legacy .NET Framework to Cloud-Native .NET 8/9 — Without a Big-Bang Rewrite

DevNord migrates business-critical .NET Framework, WebForms and WCF applications to supported .NET 8/9 on modern cloud infrastructure. AI-assisted dependency mapping, strangler-fig extraction and automated Playwright QA make every step reversible.

.NET 8/9Supported LTS target runtime
99.99%Target platform availability
90%+Automated regression coverage
System architecture

Input layers → DevNord pipeline → multi-cloud infrastructure → security & observability

This is the service-specific architecture we design and operate. Inspect any node to see its role, the engineering or QA control around it, and how risk is contained.

01 / INPUT & CURRENT STATE02 / DEVNORD ENGINEERING + QA PIPELINE03 / MULTI-CLOUD INFRASTRUCTURE04 / SECURITY & OBSERVABILITYWebForms UI — Legacy WebForms pages carry view-state and business logic in code-behind. We catalogue every page and its real usage before touching it.WebForms UI.NET Framework 4.xWCF / SOAP — Synchronous WCF contracts hide implicit dependencies. Our anti-corruption layer translates them to versioned REST/gRPC contracts.WCF / SOAPTightly coupled servicesShared SQL Server — One schema serves every module. We map table ownership first so extracted services never share write boundaries.Shared SQL ServerMonolithic schemaAI Static Analysis — Our pipeline parses IL, config and deployment history into a dependency graph, ranking modules by value and migration risk.AI Static AnalysisAssembly + call-graph mappingStrangler-Fig Proxy — An edge proxy sends a single route at a time to the new service, with instant rollback if telemetry drifts.Strangler-Fig ProxyWeighted route + feature flagsPlaywright QA Gate — Real user journeys recorded against the monolith become executable acceptance tests for every extracted slice.Playwright QA GateE2E + API characterisation.NET 8/9 Containers — Stateless, horizontally scaled services with health checks, secrets via managed identity and rolling deployments..NET 8/9 ContainersAzure Container Apps / AKS / EKSManaged Data Layer — Per-service data ownership, automated backups, point-in-time restore and EU-region residency by default.Managed Data LayerAzure SQL / Cosmos DB / AuroraAPI Gateway + CI/CD — A single governed entry point, OpenAPI contracts, and infrastructure reproduced from code in every environment.API Gateway + CI/CDVersioned APIs, Terraform/BicepIAM & Least Privilege — Role-based access, managed identities and short-lived credentials are applied to every environment in this engagement. This is applied to the .NET Framework to .NET 8/9 Cloud Migration delivery.IAM & Least PrivilegeAzure Entra ID / AWS IAMNIS2 & GDPR Controls — Encryption, residency, retention and evidence are encoded as controls so the architecture can be audited, not just described. This is applied to the .NET Framework to .NET 8/9 Cloud Migration delivery.NIS2 & GDPR ControlsPolicy as code · EU regionsObservability & Audit Trails — Dashboards and alerting cover the paths changed by this service, with immutable audit trails for release and access decisions. This is applied to the .NET Framework to .NET 8/9 Cloud Migration delivery.Observability & AuditTrailsLogs · metrics · traces · alerts
01 / INPUT & CURRENT STATE
02 / DEVNORD ENGINEERING + QA PIPELINE
03 / MULTI-CLOUD INFRASTRUCTURE
04 / SECURITY & OBSERVABILITY

Tap any node to inspect it.

Hover over a node to inspect it.

Node inspectorSelect any component to see what it does, which control protects it and how we hand it over.

Development plan

Week-by-week roadmap to production

An indicative 12-week cadence for a full engagement. The exact calendar, milestones and price are fixed in your EUR (€) or SEK (kr) proposal after discovery.

Indicative cadence — finalised in your fixed-scope proposal

01
Week 1–2

Phase 1: Discovery, Requirements & Architecture Blueprint

Assemblies, WebForms pages and WCF contracts are mapped into a dependency graph and migration risk register.

02
Week 3–6

Phase 2: Core Sprint Engineering & Iterative Milestones

An anti-corruption proxy is deployed and the first .NET 8/9 service takes traffic from one bounded context.

03
Week 7–9

Phase 3: Hybrid QA Validation (Manual UAT + Automated Regression)

Characterisation tests protect legacy behaviour while exploratory UAT and Playwright verify each extracted journey.

04
Week 10–12

Phase 4: Zero-Downtime Production Deployment & Handover

Weighted routing completes the cutover; IIS configuration, CI definitions and multi-cloud IaC are handed to your team.

How We Work

Delivery standards that make outcomes predictable

Every engagement runs with the same operating model: senior squads, transparent ownership and written evidence at every gate.

Two-week sprint cadence with demoable increments and a written decision log.

Transparent Git repository ownership — repositories land in your organisation from day one.

Infrastructure-as-code (Terraform or Bicep) for every environment, reviewed and reproducible.

Fixed-scope proposals in EUR (€) or SEK (kr), with capped B2B consulting retainers when scope is still emerging.

Bilateral NDA signed before source code, architecture data or credentials are shared.

Technical overview

What we actually engineer

The fastest safe route off .NET Framework is rarely a rewrite. DevNord maps assemblies and data ownership, then places a strangler-fig proxy in front of the monolith. Individual capabilities move to .NET 8/9 services in containers, each protected by characterisation tests before it receives production traffic.

For Nordic and European B2B teams we default to EU-region services across major cloud platforms, managed identity and infrastructure-as-code. Proposals are fixed scope in EUR (€) or SEK (kr) and include a rollback plan for every slice.

The bottleneck

Unsupported runtimes turn every release into a risk assessment

Your .NET Framework application still runs the business, but it is anchored to end-of-life runtimes, Windows-only hosts and a web of WCF/WebForms coupling. Hiring gets harder, dependencies age, and deployment windows grow longer each quarter.

  • End-of-support .NET Framework and IIS hosts with no security runway
  • WebForms page logic and WCF contracts tangled with domain rules
  • Manual release windows, long freezes and fragile rollback scripts
  • No automated regression safety net around business-critical flows
The DevNord approach

Extract module by module while the monolith keeps serving customers

We start with a two-week Blueprint Audit that maps assemblies, endpoints and data ownership. Then a strangler-fig proxy routes individual capabilities to new .NET 8/9 services running in containers, each protected by characterisation tests before it takes traffic.

  • Assembly-level dependency graph generated with AI-assisted static analysis
  • Anti-corruption layer bridging legacy WCF/SOAP to modern REST or gRPC
  • .NET 8/9 services on managed container platforms such as AKS, EKS, GKE or Container Apps
  • Playwright E2E and API contract gates on every pull request
Business outcome

What changes after this engagement

01

From end-of-life to supported

Move to .NET 8/9 LTS with a clear runway, current C# tooling and a hiring pool that still exists.

02

Reversible by design

Weighted routing and rehearsed rollback mean a bad release is a traffic shift back, not an incident.

03

40–50% faster delivery

Independent services, automated QA and self-serve environments collapse multi-week releases into days.

Deliverables checklist

Concrete artefacts you receive at handover

These are service-specific, reviewable assets — not status reports. Your team owns each one.

  • Assembly and endpoint dependency graph
  • Anti-corruption layer for WCF/SOAP to REST or gRPC
  • .NET 8/9 services with clean Git history
  • Azure Container Apps, AKS or AWS ECS/EKS configuration
  • Characterisation, unit and Playwright test suites
  • Rollback runbook and 30-day hypercare plan
Questions, answered

The things decision-makers ask us first

Still unsure? Write to us at [email protected] — we reply in plain language, without a sales script.

Can you migrate WebForms without rewriting the user interface?

Yes. We commonly keep the WebForms front end behind the strangler proxy while replacing backend capabilities first, then migrate screens incrementally to React or Razor once the API layer is stable.

How do you handle WCF contracts that cannot be changed?

We wrap them in an anti-corruption layer that exposes a clean, versioned API to new services. The legacy contract stays untouched until its consumers have moved.

Will we need to pause feature development?

No. The strangler approach runs modernisation in parallel with your roadmap. We agree a small, protected slice of capacity and sequence extractions around your release calendar.

Which cloud do you recommend for .NET?

Microsoft Azure is often a short path for deep .NET estates, but we design target architectures across Azure, AWS, Google Cloud, and private cloud environments based on your existing contracts, data residency needs and skills — never on licence preference alone.

Next step

Get a de-risked .NET 8/9 migration plan

Start with the 2-week Blueprint Audit. You receive a dependency map, target architecture and sequenced extraction plan you can act on — whether or not you continue with DevNord.