Skip to content
digitapulia.com
Fixed-price engagements

.NET modernisation roadmap

Our in-house ERP is old but it works, and no one dares touch it.
What we do
We read your application's code and design its move to modern .NET in stages.
How we do it
We start by talking to the people who use the application every day and to whoever maintains it, if anyone still does, to learn what it does, which parts are critical and which ones people are afraid to touch. Then we read the code to learn what parts the application is made of, which version of .NET it is written in, which libraries and services it depends on, where it keeps its data and which parts have no direct equivalent in modern .NET. With that we split the move into stages: each stage leaves the application working, and none forces you to change everything at once. For every task of every stage we write a low and a high estimate. Finally we present the plan to your team in a session and answer their questions.
What you receive
A report, the list of tasks with a low and a high estimate for each, and a closing session with your team.
What changes for you
The application stops being something no one dares touch: you know what it is made of, where its risks lie and in what order it can be renewed. Decisions about it are taken with a written plan, not when something stops working, and the budget for the renewal is built from an estimate per task, not from a guess.
What we need from you
Read access to the code and to its change history, if there is one; the structure of the database, without the data; and conversations with the people who use the application and with whoever maintains it.
Who it is for
Senior management and technical lead
How you buy it
At a fixed price: the price is written down before we start and we give it to you when you ask.

Example use cases

These are examples: they do not describe a real client.

  • A distributor of hardware-store supplies in Spain with a subsidiary in Colombia, whose orders go through an application of its own

    The situation

    The ordering application was written many years ago by someone in IT who no longer works at the company. It works, but it runs on a server no one wants to restart, and every change the Colombian subsidiary asks for is put off because no one knows what it might break. One supplier has looked at it and proposes rebuilding it from scratch; another will not commit to anything.

    What we do

    We read the code and talk to the people who use it in Spain and in Colombia. We separate what the application really does from what no one uses any more, and point out the parts that depend on components with no direct equivalent in modern .NET. The plan proposes starting with the part that calculates prices for Colombia, which is the one with the most changes pending, and leaves the warehouse screen for last. Each stage has its list of tasks with a low and a high estimate, and management decides with the plan in hand.

  • A packaging maker in Italy with a subsidiary in Argentina, whose production planning lives in a desktop program

    The situation

    The planning program is installed on each computer and keeps its data in a shared database. It is written in an old version of .NET and depends on components that need an old version of Windows, so both offices keep old computers just to be able to open it. The company wants the Argentine subsidiary to use it from a browser, but does not know whether that means starting from zero.

    What we do

    We read the code and the structure of the database, and separate the planning logic, which is worth keeping, from the screens, which depend on the Windows desktop. The plan proposes moving the logic to modern .NET first without changing anything its users see, and then building the screens for the browser, one by one. In the closing session we go over the order of the stages with the office in Italy and the one in Argentina, and what each stage leaves working.

Frequently asked questions

Does the application have to be rebuilt from scratch?

Not necessarily. The plan says, part by part, what can be moved to modern .NET almost as it is, what has to be adapted and what is better rewritten. If a part has to be rewritten, the plan explains why.

Who carries out the migration afterwards?

You decide. The plan is yours and is written so that any team that works with .NET can follow it: yours, another supplier, or us, with the staged .NET migration.

Does the application stop while the code is being read?

No. We work on a copy of the code and on the structure of the database; the application keeps running as usual.