Skip to content
Architecture26 Sept 20269 min read

Migrating .NET Framework to .NET 8 without a feature freeze

A rewrite that stops the roadmap for a year is a failed rewrite. Here is the routing layer, the reconciliation strategy and the rollback discipline we use instead.

Every legacy migration proposal we review contains the same optimistic sentence: we will pause new features for one quarter and come back on the new stack. In eleven years we have never seen that quarter stay a quarter.

Why big-bang rewrites fail

The old system keeps changing. Regulators publish new requirements, sales promises a feature, a bug needs fixing in production. Every one of those changes has to be applied twice — once in the system you are trying to abandon and once in the one you are building. The gap widens, the cutover date moves, and eventually somebody proposes a third system.

The routing layer

We put a thin routing layer in front of both systems. It is not a service mesh and not an API gateway product; in most cases it is 300 lines of code that reads a route table from configuration.

Every route has three states: legacy, shadow and new. In shadow mode, the request goes to the legacy system and returns its response, but a copy is sent to the new implementation and both outputs are compared asynchronously. Differences are logged with the full request payload.

Reconciliation before cutover

A route only moves from shadow to new when the comparison has been clean for a defined period — usually 30 consecutive days of production traffic. On the Perenna engagement that meant 2.1 million policies reconciled daily against a mainframe until the numbers matched for a full month.

What this costs

Dual-running is not free. You pay for two systems, and you pay for the comparison infrastructure. On a typical engagement this adds 12–18% to the delivery budget.

What you get for it: no feature freeze, a rollback that takes seconds rather than a weekend, and a migration that can be paused at any route boundary if priorities change.

The rule we do not break

No route moves to the new system until somebody can explain, in writing, how it moves back. If the rollback path is not documented and tested, the route stays in shadow.

Tell us what you are building

Send a brief and a solution architect replies within one business day — with questions, not with a template.