From Excel and Access to a web system.
Once the spreadsheet has become the company's system, the risk is that everything depends on one file, one machine and the one person who understands the macros. We move it to a web application without stopping the business.
How this kind of project works
When it makes sense
When more than one person needs to enter data at the same time, when each person should only see their own part, when reports no longer match between files, or when only one person knows how the macros work. If one person uses the spreadsheet and it is enough, you do not need a system: we will tell you so in the first call.
What changes
People sign in from the browser, with nothing to install. Each user sees and edits what they are meant to. Data lives in a single database and reports always come from the same source, so file versions stop existing.
How we do it
We start by understanding what the spreadsheet calculates today, including the rules hidden in formulas and macros. We migrate module by module: each one is checked against the numbers of the old system before moving on, and the company keeps working as usual in the meantime.
What happens to the data
It is imported. We write the process that reads the current files, cleans up the data and loads it, so history is not lost and nobody has to retype anything.
What we need from you
Real files, someone who knows the business rules, and time to confirm the numbers match. That is what weighs most on the timeline.
How long it takes and how it is priced
It depends on scope. After a 30-minute call we send a proposal with scope, timeline and a fixed price. Work runs in two-week stages with a demo at the end of each one, and you can change direction between stages.
Frequently asked questions
Do we have to stop using Excel overnight?
No. The migration goes in parts and the spreadsheet stays in use until the new module gives the same results. Anything you want to analyse separately can still be exported to Excel.
Will the numbers match the spreadsheet?
That is the condition for moving forward: each module is compared against real cases from the old system. When a difference shows up, it is almost always a rule nobody had written down, and we decide with you how it should work.
Does it work if my system is in Access?
Yes. Access databases are read and migrated just like spreadsheets, and forms and queries are rebuilt as web screens.
Who owns the code?
You do. It lives in your repository, under your licence, from day one. We never reuse one client's code in another client's project.
What happens after delivery?
We leave documentation and include three months of support. After that we stay on only if you need us.