In short
- A simple tool (e.g. an Access database or a macro workbook used by a few people) moved to a web app usually costs PLN 15,000-40,000 net and takes 3-6 weeks.
- A system with many users, roles, reports and one or two integrations is usually PLN 40,000-120,000 and 1.5-3 months; a large company system PLN 120,000-300,000 or more.
- The usual reasons: one person knows the system, it does not work remotely, the vendor no longer supports it, data is unprotected and every change is risky.
- The safe route: list the features, migrate data as a trial, run old and new in parallel for a short time, switch over in stages.
- Do not copy everything 1:1 - some features nobody uses any more, and some processes are worth simplifying along the way.
When it is worth moving an old system
- Only one person knows the program, or the company that wrote it no longer exists.
- It runs on one computer or the office network, but people need remote and phone access.
- The database file breaks with several users at once, and backups are manual, if they happen at all.
- The system needs an old version of Windows, Office or libraries that no longer get security fixes.
- Data has to be retyped into the ERP or other systems because the old program has no integrations.
What it costs
| Starting point | Typical scope of the new app | Cost (net) | Time |
|---|---|---|---|
| Excel workbook with macros or a small Access database | A few screens, sign-in, database, export to Excel | PLN 15-40k (EUR 3.5-9.5k) | 3-6 weeks |
| Desktop program for a department (a dozen to several dozen people) | Roles, reports, change history, 1-2 integrations, browser access | PLN 40-120k (EUR 9.5-28k) | 1.5-3 months |
| Main company system with many modules | Several processes, many integrations, migrating a long data history, replacement in stages | PLN 120-300k+ (EUR 28-70k+) | 3-12 months |
Net amounts, indicative - on the Polish market and in our own quotes; EUR approximate. The price depends mostly on how many features really have to stay, the quality of the data in the old system and the number of integrations.
How to move a system without stopping work
- Feature list: what the system does, who uses what, which reports are really used. Best done at the screen with the people who work in it every day.
- Data analysis: structure, duplicates, empty fields, hidden rules in macros and formulas.
- Design of the new app, simplifying wherever the old process only existed because of the program's limits.
- Trial migration: moving a copy of the data and comparing results (totals, reports) with the old system.
- A short parallel run, or switching over one process or department at a time.
- Switching off the old system, keeping a read-only archive of the data if needed.
The most common risks
- Hidden logic: rules stored in macros, formulas or one person's head. They have to be written down before the migration.
- Bad data: years of manual entry leave duplicates and inconsistencies - cleaning the data is a separate step.
- A 1:1 copy: recreating every screen of the old program raises the cost and carries over the old problems.
- An overnight switch with no parallel run and no fallback plan.
How 2Simple does it
2Simple is a Polish software house based in Piotrków Trybunalski that builds web apps in TypeScript, React, Node.js and Rust, takes over development of existing systems and connects them to the ERP. We start with a review of the old system and its data, then propose the scope of the new app and a plan to switch over in stages.
We bill hours worked, show a working version on your data every 2-3 weeks, and hand over the source code, documentation and copyright at acceptance.