Modernisation Guides
without shutting the business down for it.
Practical guides to legacy system modernisation, Access database replacement and moving a desktop application to the web. Fix the part that is hurting first, keep the rest running, and replace it in stages you can afford.
Rebuild vs Modernise vs Patch: A Practical Guide
Decision framework for what to do with ageing software, with cost comparisons and risk factors.
Access Database Replacement Planning Guide
How to plan a migration from Access to a modern web-based system without losing your data or your mind.
Desktop to Web App Conversion Guide
What to expect when converting a desktop application to a web-based system.
How to Approach Legacy Software Modernisation
A practical roadmap for modernising systems that are too important to replace overnight.
Signs Your Current System Is Costing More Than It's Saving
How to identify when a legacy system has become a liability rather than an asset.
Legacy System Migration Guide
How to move off an ageing system in stages, without a big-bang cutover.
Technical Debt Assessment
How to work out what your accumulated shortcuts are actually costing, and what to fix first.
Btrieve and Pervasive PSQL: identify it and get your data out
The files, DLLs and services that tell you Btrieve is underneath, and the four ways to extract the data.
Visual FoxPro: reading .dbf, .scx and .frx after end of support
What each file extension holds, and the traps that silently corrupt a careless migration.
PFXplus and POWERflex: reading a 1993 4GL
What the .PTC, .PFI and .FD files mean, and why the data comes out even when the source is gone.
AS/400 and IBM i: what to modernise and what to leave alone
Why replacing the platform is usually the wrong project, and what to do instead.
Crystal Reports: inventory hundreds of .rpt files before a migration
Why reporting breaks late in a migration, and the inventory that usually shrinks the project.
Ready to discuss your project?
Tell us what you're working on. We'll come back with a practical recommendation and clear next steps.
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.