Replace outdated software
Legacy software modernisation and replacement.
01Overview
Old systems carry your data, your processes, and the expertise of the people who built them. We rebuild on a modern foundation without losing any of that, whether it is an ageing PHP application, an Access database, or a desktop tool nobody can update any more. GIMLabs is our own proof: we built it to replace tools that had been the industry standard for twenty years.
- Preserving your historical data
- Rebuilding with workflows your team already knows
- Running old and new side-by-side during the transition
- Training for the team
- Phased rollouts, one part at a time
Technologies
- Data migration
- PHP
- Microsoft Access
- AGS 4
02Situations
Where we usually come in.
The software your business depends on was built ten or fifteen years ago, and the people who built it have moved on.
It only runs on one old machine or one version of Windows, and everyone is nervous about touching it.
Your data is locked in a database or file format nothing else can read.
Your team works around it with spreadsheets, paper forms, and copy-paste.
The vendor has stopped updating it, or wants a fortune for the next version.
03How it works
How a project runs.
- 01
Understand what it really does
We sit with the people who use it, read the data, and write down the rules that only live in the old code and in people's heads. Nothing gets rebuilt until we know why it works the way it does.
- 02
Plan the move
Decide what to keep, what to improve, and what to drop. Map every piece of historical data to its new home, and agree the order things will move in.
- 03
Build in phases
Start with the part that hurts most. Each phase ships something your team uses, rather than one big launch at the end.
- 04
Run old and new side by side
The team checks the new system against the old one on real work. Nothing is switched off until the replacement has proven itself.
- 05
Switch over and support
Final data migration, training for the team, and support while everyone settles in. Then the system keeps improving rather than ageing.
04Questions
Common questions.
- Will we lose our historical data?
- No. Moving your data is part of the job from day one. We run the migration against your real data repeatedly before the final switch, so the switch-over is uneventful.
- Can we keep using the old system while you build?
- Yes. Your business keeps running on the old system until the new one has proven itself on real work.
- Do we have to replace everything at once?
- No, and we would usually advise against it. Phased replacement costs less up front, lowers the risk, and gets something useful in front of your team sooner.
- Nobody fully understands how the old system works. Is that a problem?
- It is common, and it is where we start. We work it out from the data, the code where it exists, and the people who use it every day.
- Who owns the code?
- You do, once it is paid for. The code, hosting, and domains sit in accounts you control, so if you ever move on from us you take everything with you. The only exception is our own general-purpose tooling, which you get a permanent licence to use.
05Related services
Sounds like your situation?
The project planner takes about five minutes. A quick message also works. Either way, we reply within two working days.