Logistics and warehousing AWH

AWH's operational data brought across from the AS400, with every record accounted for.

We carried out the migration of AWH's operational data from its AS400 platform, a mainframe-class system, into its new platform: mapped, cleansed, rehearsed and cut over with every record accounted for. After the original prime contractor left, AWH kept us on through retained services.

At a glance

Client
AWH
Sector
Logistics and warehousing
Solution
Migration from the AS400 (DB2) into AWH's new platform, with a migration and sync engine so both systems ran side by side
Engagement
2022 to 2026, first under a prime contractor, then directly with AWH through retained services
Services
First module: container imports, with shipment advice, a container tracker, handheld receiving and a CargoWise connection

Context

AWH is the largest independent logistics services provider to Australia's wool and cotton industries. It stores, handles and moves wool, cotton and containers for import, export and domestic distribution, with more than 700,000 square metres of warehouse space and over 400 people.

The challenge

AWH's operations ran on custom software on an IBM AS400, a mainframe-class platform, written in SYNON and COBOL with its data in DB2. The data was the hardest part: tables with no unique identifiers, relationships that existed only in the application code, and records that had never been timestamped. And the warehouse couldn't stop, so the AS400 had to keep running while the new platform took over one module at a time.

What we did

Mapping the data

We worked through the AS400's table definitions, found the hidden keys in tables that had no unique identifier and rebuilt the relationships between them, so every table had a clear home in the new platform.

Cleansing and moving it

We built the migration and sync engine that brings AWH's data across and keeps both systems in step, including a DB2 driver we wrote ourselves after the standard drivers proved too slow and too hard to diagnose. Where records had never been timestamped, the engine works out what has changed, so updates still flow across.

Rehearsals and cutover

Loads were rehearsed and checked record for record, with random spot checks against the AS400, and AWH's people tested the result before it went near production. Each cutover accounted for every record before the business switched across.

Staying on

The program started in 2022 under a prime contractor. When that contractor left, AWH kept us on through retained services, and our engineers worked inside AWH's own team until mid-2026.

The result

  • AWH's container imports run on the new platform, in production.
  • AS400 data moves across and stays in sync, so both systems run side by side while the remaining modules move over.
  • Every record accounted for at cutover.
  • More than four years with AWH, from discovery in 2022 to mid-2026.

A migration isn't finished until every record is accounted for.

Related services

Related