Is our source code safe with you?
We sign an NDA before seeing any code, and we only need read-only access. Code is processed with a commercial AI service under terms that do not allow training on your data. If your policies require it, we can run the tooling under your own accounts.
Do we have to stop using the current app during the migration?
No. The old and new apps run side by side and pages move over in phases. Your team keeps working the whole time.
Will our database change?
No. We keep your SQL Server schema, stored procedures and data as they are. Any database improvements are a separate decision for later.
Our app is VB.NET. Is that a problem?
Not at all. VB.NET Web Forms is a core part of what we do. The new app is written in C#, and the assessment shows exactly how each VB page maps over.
We use Telerik, DevExpress or Crystal Reports controls.
The assessment finds every third-party control and prices its replacement, so there are no surprises later.
Why Blazor?
Blazor is Microsoft's component-based web framework for modern .NET. Its model is the closest to Web Forms, so pages map over cleanly, and .NET 10 is a long-term support release.
How long does a migration take?
A small app with a handful of pages can be done in a few weeks; large apps take months. Your assessment includes a phased timeline.
What if the work takes longer than estimated?
That's our risk. The price is fixed for the agreed scope. If you want to add or change scope, we agree the change in writing before doing it.