Case study · ERP & distribution

Thirty years of trading history, moved without losing a record

Migrating a VB5-era system on MySQL 3.21 into a modern ERP — suppliers, purchases and decades of transactions.

Sector Pharmaceutical distribution
Working together since 2026
What we built Legacy data migration

The problem

The business had been running since the 1990s on a Visual Basic system over MySQL 3.21 — a database version released before most of the current team started working. It still ran. Nobody dared touch it, and nobody could get a useful report out of it.

Replacing it meant bringing every supplier, product, purchase and transaction across without losing history, because that history is what the accounts are built on.

What this involves

  • Reverse-engineering a schema with no documentation and no original developer to ask
  • Mapping old structures onto a modern ERP’s tables without distorting what the records actually mean
  • Reconciling totals at every stage, so the migrated figures match the old system exactly
  • Handling decades of inconsistency — codes reused, fields repurposed, conventions changed midway

Why it is worth saying

Most software firms will quote you for a new system and quietly suggest you start fresh. Starting fresh means losing the history that tells you what a customer has bought for fifteen years.

If you are sitting on an old system that works but tells you nothing, this is the kind of work that gets you out of it.

Have a process that works like this one used to?

Send us a photo of the sheet you fill in by hand.