Home / What’s possible / Modernizing legacy software
Modernizing legacy software
The program still does the job, but it may be tied to a single computer, the person who built it may be out of reach, or something may break with every update.
Your data and your habits are kept
The records built up over the years move to the new system, and the workflow your team is used to is taken into account. The program moves to a setup that opens in a browser and on a phone. We first study the current program and how you use it, then plan the modernization around that.
Who is it for?
Businesses working with an old desktop program or with Access or Excel files, those who can no longer reach the person or company that wrote their program, teams that want to stop depending on a single computer, and those who want access from outside the office.
What can modernization include?
- A new web-based interface
- Use on phones and tablets
- Moving old records over
- Users and permissions
- Automatic backups
- Reports
- Connections to other systems
- Adding missing features
- A step-by-step transition
- Team training
Modernize, or switch to off-the-shelf software?
If your work follows a common pattern, switching to suitable off-the-shelf software can be faster and cheaper. Your records still need to be moved over.
If your workflow is specific to you and doesn’t fit off-the-shelf software, modernizing the program is the better choice. We look at which one suits you together, before you decide.
How does the transition work?
Your old program keeps running while the new system is being prepared. First we do a trial migration with a copy of your records. Once your team has tried the new system, we set the switch-over date together. If the work allows it, you can also switch over one section at a time.
What affects the price?
The price depends on the size of the program, the amount and structure of the data, connections, users and permissions, and the features to be added. Once we’ve studied the program, we send a quote with a clear scope.
Frequently asked questions
Will my old data be lost?
We first test the migration with a copy of your records and check the results together. We keep your old data as it is until the transition is complete.
What if we don’t have the program’s source code?
In most cases it can still be modernized. We work out how it works from the way it’s used, and read the data from where the records are stored. We check together at the start that the data can be accessed.
I can’t reach the person who wrote the program. Is that a problem?
Reaching them makes the work easier, but it isn’t required. In that case we study the program and the records directly.
Will my work stop during the transition?
You keep using the old program until the new system is ready. The final migration may need a short break; we pick the time together.
Will my team have to learn everything again?
We keep the workflow you’re used to as much as possible. We hand it over after teaching your team what has changed.
Can Excel or Access files be moved over too?
Yes, if they’re structured suitably. Scattered records may need tidying before they’re moved; we review this together when defining the scope.
Can we modernize just one part first?
That depends on how the program is built. If it allows, we can start with the part you need most.
Will it work with my accounting or e-invoicing software?
We set up connections based on the software you use. We confirm this when defining the scope.
Can it be used from a phone?
The new system is designed to open in a browser and on a phone. If you need a separate mobile app, we can add it to the scope.
Where is our data stored?
We decide together where the data will be stored and who can see it, in line with GDPR, Turkey’s KVKK or whichever rules apply to you. You stay in control of it.
Are there monthly costs after setup?
For most setups, yes. Server fees, and fees for any services used, vary with the setup. We list them separately in the quote.
How long does modernization take?
It depends on the size of the program and the state of the data. After reviewing it, we share a clear timeline with the quote.
Who owns the code?
We discuss code ownership based on the scope of the work and put it in the agreement.
How is the system handed over to us?
We agree on how the handover will work at the start of the project. We hand it over after teaching your team how to use it.
How long is support provided?
We provide support for bugs and issues for the first six months after delivery. After that, it depends on the contract.