Legacy Modernization
We modernise old systems, websites and apps in small steps, with the old version kept ready as a fallback.
danadresse.dk: Danish addresses after DAWA
A REST API for Danish addresses built to answer like DAWA, with the same address identifiers, autocomplete, validation and bulk cleansing. Made for systems that lost their address source when DAWA closed.
Old software rarely fails all at once. It gets slower, the person who wrote it leaves, a library stops receiving security fixes, or a service it depends on closes. The business keeps running on it because a rewrite feels too risky, and that feeling is often right: the big rewrite that replaces everything on one weekend is how modernisation projects go wrong.
We work the other way. The new part runs next to the old one, takes over one piece at a time, and the old version stays ready as a fallback until the new one has proven itself. Data is moved in counted steps and checked by reading it back, not by trusting the import log. The same applies to old phone apps that no longer meet store requirements: we decide what to keep, what to rebuild, and release the new version in phases.
Some real examples. When Denmark's DAWA address service closed on 1 October 2026, every system using it needed a new source. We built danadresse.dk to answer like DAWA, using the same address identifiers, and ran 85 test cases against the live DAWA before it closed: 74 of them gave identical answers. We froze 79 of DAWA's real responses as test files, so compatibility can still be tested after the service is gone, and moved our own time registration product over when DAWA started returning errors. For our SMS gateway we mounted a new FastAPI application inside the old one and moved features over gradually; the new application went live in August 2026 inside the running service, with no separate switch-over. When Oksana Kolesnyk Beauty Studio moved to a new website on 6 November 2026, online booking paused for about four minutes, the transferred records matched production by checksum, and the old site stayed untouched as a two-minute rollback. We upgraded our own Odoo from version 18 to 19 in October 2026 and removed the old version only after its backups were verified.
Modernisation is priced by what we find. A technical audit from 3,000 DKK maps the code, data, dependencies and risks, and tells you which steps pay off first. After that, work is billed at 500 DKK per hour, and urgent support for a failing old system is 1,000 DKK per hour.
Do not modernise just because the code is old. If the system is stable, nobody needs changes, and its dependencies are still supported, the cheaper choice is backups, monitoring and leaving it alone. Modernise when change has become slow, risky or impossible.
Key Features
Old and new side by side
The new code runs next to the old system and takes over feature by feature. Users keep working while the move happens, and nothing depends on one big switch-over.
Fallback until proven
The old version stays untouched and ready, so going back takes minutes. We remove it only after the new one has run in production and backups are verified.
Data moved in counted steps
Count, back up, try on a few records, move in batches, then compare against the source. Every step is checked by reading the result, not by a green log line.
Replacement for closed services
When an external service shuts down, as DAWA did, we connect you to a compatible replacement or build one, and test it against recorded answers from the old service.
Old apps brought up to date
Apps that fail new store requirements or crash on new phones are audited, updated or partly rebuilt, then released in phases so a problem reaches few users.
Performance where it hurts
We measure the slowest jobs first. Rewriting one nightly query in danadresse.dk cut its reindex from about 7.7 hours to 12 minutes.
Why Choose This Service
Changes arrive one piece at a time, so staff and customers barely notice the move, apart from things getting faster.
Backups before each step and the old version kept ready mean a mistake costs minutes, not a lost weekend.
Recorded answers and side-by-side comparisons turn hidden behaviour into tests the new system must pass.
The audit ranks problems by risk and cost, so you fix what blocks the business before what merely looks old.
How We Deliver
Our proven process ensures quality at every step
Audit what exists
Code, data, servers, dependencies, accounts and the people who know how it works. We write down what the system does, including the parts nobody remembers asking for.
Record today's behaviour
We capture real inputs and outputs of the old system and turn them into tests, so the new version must answer the same way before it takes over.
Build the first slice beside it
One feature moves to the new code while the rest stays on the old system. Traffic or users switch over gradually, with the fallback ready.
Move data and switch over
Data is moved in batches with backups and checks against the source. The switch itself is planned for minutes of downtime, with the rollback steps written beforehand.
Retire the old system
After a period in production, verified backups and a final archive, the old system is removed so you stop paying for two of everything.
Frequently Asked Questions
Should we rewrite from scratch or improve what we have?
Rarely from scratch. A rewrite has to rediscover everything the old system does, including rules nobody wrote down. We prefer moving piece by piece. A rebuild makes sense when the old code is a short-lived prototype: we archived an early booking prototype with many known vulnerabilities rather than patch it; its successor, bkg.dk, was built as a new platform.
Our system depended on DAWA. What now?
DAWA closed on 1 October 2026, so address lookups and validation need a new source. Our own danadresse.dk was built to answer like DAWA with the same address identifiers, which makes the switch mostly a change of address and key. If you prefer the official Datafordeler services, we can connect you to those instead.
How long will the old and new systems run side by side?
Until the new one has handled real work without surprises, which depends on how often the system is used and how many edge cases it has. For a website move it can be days; for a business system with monthly runs, at least one full cycle. You decide when to retire the old one.
Can you modernise an old mobile app?
Yes. We check whether the app still builds with current tools, whether it meets Apple's and Google's current requirements, and whether its backend is still alive. Then we update it in place or rebuild the screens that fail, keeping the store listing, reviews and users. New versions go out in phases.
What happens to our data during the move?
It is counted, backed up and moved in batches, and the backup is checked before anything changes. After each batch we compare the new system with the source. On one website move we found that two upload folders had been missed, which broke eight staff photos; since then we check every file reference in the database against the disk.
Ready to Cross the Bridge?
Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.