Services
Excel to app
An internal application instead of shared spreadsheets. Stock, orders, attendance or approvals in one tool, accessible over the web.
Services · Legacy system rescue
For companies whose operations run on MS Access, Excel macros or old PHP, and the person who built it is no longer around.
The Access database or Excel macros were written years ago by a colleague or contractor. Today nobody wants to touch them.
Fixing one thing breaks another. Changes take a long time and nobody can say what else they will affect.
It does not work over the web, cannot handle several users at once, runs on an unsupported version, and backups are a matter of luck.
Most often these are tools that were once built quickly and then became the core of the business:
Rewriting the whole system at once and switching over one day is the riskiest possible route. If something is forgotten, you find out only in live operation. That is why we split the system into parts. We migrate each part, verify it with the people who work with it daily, and only then switch off the original version.
Before rewriting each part, we prepare tests that compare the results of the old and new systems on the same data. That way you can be sure the calculations, totals and reports match.
Throughout the migration you know which phase the project is in, which part already runs in the new system and what is left. Users get the new system in smaller batches, so they do not have to learn everything at once and have time to point out things the old system did “on the side” that nobody ever wrote down.
If your system is mainly a spreadsheet you want to turn into an application, take a look at our Excel to app service as well.
weeks 1–2
We go through the code, database, macros and dependencies, and talk to the people who use the system every day.
week 3
We plan the order of stages so that operations keep running. The old and new systems can run side by side for a while.
in stages, usually weeks to months
Each stage is deployed and verified with users, and only then do we switch off the matching part of the old system.
final week
We hand over the code, documentation and operating procedures. Someone other than the author will be able to understand the system.
Michal Czerník manages the full SDLC from analysis to operations. He can read the old system, design the new one and make sure no data or logic is lost along the way.
Experience leading development teams and in the CTO role means a staged plan, verification with users and no big overnight switch.
With AI-assisted development in Claude Code we map unfamiliar code faster and prepare tests that confirm the new system calculates the same way as the old one.
No, we plan the migration in stages so that operations keep running. The old and new systems can run in parallel for a while.
The audit and plan usually take three weeks. The length of the rewrite depends on the size of the system and is set based on the audit.
No, data transfer is part of every stage. After the transfer, we check the data against the original system.
Yes, that is exactly what we expect with legacy systems. We create the documentation from the code, the data and interviews with users.
Sometimes yes, and the audit will show it. If a fix is the cheaper and safer route, we recommend it.
VBA (Visual Basic for Applications) is the macro programming language in Excel and Access. Many internal business tools still run on it.
Services
An internal application instead of shared spreadsheets. Stock, orders, attendance or approvals in one tool, accessible over the web.
Services
Independent assessment of software and the development team for investors, acquisitions and refinancing. Discreet, under NDA, within weeks.
Services
Part-time technology leadership for companies that need a CTO, but not a full-time one. Strategy, team, vendors and AI.
Tell us what you are working on. We will get back to you and arrange a short call to see whether and how we can help.