Skip to content
digitapulia.com
Fixed-price engagements

Staged .NET migration

We have the plan; what we lack is someone to carry it out without stopping the business.
What we do
We carry out the plan stage by stage, and each stage has its own price and date in writing.
How we do it
We start from your plan, or from the one produced by the .NET modernisation roadmap, and before starting we write down the first stage: which part of the application moves to modern .NET, how it is tested, its price and its date. We work on a separate copy, without touching the application the business uses. When the stage is ready, we test it with your team on real cases and switch it on at the agreed moment, with a plan to go back to the previous version, data included, if anything goes wrong. Then, and not before, we write the next stage, with what the previous one has taught us.
What you receive
The application migrated stage by stage, with the tests of each stage.
What changes for you
The migration stops being a leap in the dark: the business keeps working while the application changes piece by piece, and each piece arrives tested. Before each stage you know what it includes, what it costs and when it ends, and you can stop after any of them with the application working.
What we need from you
The plan, if you already have one; access to the code and to a test environment, and to where the application runs for each switch-over; someone on your team to test each stage on real cases; and an agreed moment for each switch-over.
Who it is for
Technical lead
How you buy it
At a fixed price per stage: the price of each stage is written down before it starts and we give it to you when you ask.

Example use cases

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

  • A furniture retail chain in Spain, also present in Portugal, whose ordering system already has its roadmap

    The situation

    The company has a written plan to move its ordering system to modern .NET. The in-house team has no time to carry it out while handling day-to-day work, and the system cannot be stopped: the stores in both countries use it from opening to closing time.

    What we do

    We review the plan and write down the first stage: the calculation of home deliveries, which is the part that changes most. We migrate it on a separate copy, test it with the store team on real orders from Spain and Portugal, and switch it on before the stores open, with a plan to go back to the previous version if anything goes wrong. With what we learned we write the second stage, with its price and its date.

  • An automotive parts maker in Italy with a plant in Mexico, whose quality system is written in an old version of .NET

    The situation

    The system records the quality checks of both plants and produces the certificates customers ask for. It is written in an old version of .NET and depends on components that are no longer updated. Between the plant in Italy and the one in Mexico, which works in shifts, the system is in use at all hours. The company already has the roadmap: first the certificates, then the recording of the checks, and the screens last.

    What we do

    We start from the roadmap and write each stage so that it never stops a shift. Each stage is tested with the quality staff of both plants, on real checks copied from the system in use, and switched on at the agreed change of shift. Plant management knows before each stage what it includes, what it costs and on what date it ends.

Frequently asked questions

Do I need the roadmap first?

A written plan is needed. If you already have one, we review it before writing down the first stage; if you do not, the .NET modernisation roadmap is the first step.

What happens if a stage goes wrong?

Each switch-over has a plan to go back to the previous version, data included, until the new one works on real cases. If anything goes wrong when it is switched on, we go back to the previous one and fix it before trying again.

Can I stop after one stage?

Yes. Each stage leaves the application working and is bought separately: the next one is written down and agreed before it starts.