Modernizing Intelliflo’s .NET Stack Using AWS Transform

About Intelliflo

Intelliflo, a leading financial technology company, equips over 30,000 financial advisors worldwide with innovative solutions to streamline their work and elevate client experiences. The Intelliflo platform simplifies the digital landscape, enabling advisors to deliver exceptional financial advice with ease. 

Since March 2021, Intelliflo has focused on transforming the advisory process through flexible, cutting-edge technology that supports every stage of financial planning.

Problem

Intelliflo’s advisory platform relied on a legacy .NET Framework 4.7.2 codebase packaged into a single Visual Studio solution with more than 35+ interdependent projects. While this monolithic setup had supported the business for years, it was becoming increasingly hard to maintain and update without causing major delays and additional risk.

Slow development cycles

Because every project was tightly linked, even the smallest code change forced a full rebuild of the entire solution. Engineers routinely waited hours before they could test a simple bug fix or new feature, shattering their focus and slowing day-to-day work. These long build times also clogged the continuous integration pipeline, leading to merge queues and unpredictable delivery schedules. Over time, the backlog of fixes and improvements grew, making it difficult to respond quickly to advisor needs.

Risky migration path

AWS Transform at the time only supported an all-at-once migration straight from .NET 4.7.2 to .NET 8, with no intermediate step for .NET Standard 2.0. Attempting a big-bang rewrite would have taken months and risked breaking critical partner integrations and third-party plugins. Without a safe way to run old and new code side 

by side, Intelliflo faced a painful choice: pause feature work for a massive rewrite or stay stuck on outdated technology—neither of which was acceptable.

Manual compliance bottlenecks

As a financial technology company, Intelliflo must meet strict security, audit, and regulatory requirements for every new microservice or AI feature. Under the existing process, each pipeline paused for manual reviews, formal sign-offs, and documentation checks. That back-and-forth often added days or even weeks to releases, delaying urgent patches and frustrating both engineering and compliance teams. Engineers found themselves spending more time chasing approvals than writing code.

High hosting costs

Intelliflo’s applications and services ran on Windows EC2 instances, which cost roughly twice as much as comparable Linux servers. As usage scaled, those higher rates took a growing bite out of the cloud budget, limiting resources for innovation and other priorities. Shifting workloads to Linux became a financial imperative to keep operating costs under control.

Talent acquisition challenges

Developers with deep expertise in legacy .NET Framework are now hard to find, making hiring and onboarding both slow and expensive. In contrast, skills in modern .NET Core and .NET 8 are widespread among new graduates and mid-level engineers. Continuing to build on an outdated platform risked creating a talent bottleneck, whereas moving to a current .NET ecosystem would open access to a larger, more active developer community.