Migrating a distributor's ERP from an aging server room

The system that runs ordering, the warehouse and accounting needs a new home. The software vendor's own hosted version, moved in careful stages, beats building it ourselves in the cloud.

2 min readMade-up stories, not client work

Cloud Migration: story 5 of 15

A made-up story

Picture a food distributor whose ordering, warehouse and accounting all run on one business system, on servers in a back room.

What's going wrong

The servers are near the end of their life, and the system can't be down. A bad move would stop orders and shipments.

What they have today

  • One business system running the whole company
  • Ageing servers in a back room
  • Links to the warehouse scanners and the bank

What we can't ignore

  • Orders can't stop during the move
  • The vendor must support whatever we choose
  • Staff need training time

The choices

  • Worth a look

    Copy the servers into the cloud

    Possible, but we'd still be running and patching the servers ourselves.

  • Our pick

    The vendor's own hosted version

    The people who know the software best run it for you.

  • Maybe later

    Replace it with a different product

    A much bigger project. Worth considering only when the current system stops fitting.

  • Worth a look

    New servers in the back room

    Familiar, but it means repeating this whole problem in a few years.

What we'd do

Move to the vendor's hosted version in stages: test a copy with real users, rehearse the switch including the scanner and bank links, then switch on a quiet weekend with a written plan to go back if needed. Keep the old servers read-only for a few weeks afterwards.

Why

  • The vendor supports and updates its own hosted version
  • Testing and rehearsal catch problems before go-live
  • A written way back keeps the risk low

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

The hosted version is a subscription, while new servers are a one-time cost. Once upkeep, backups and the next replacement are counted, the subscription is usually the steadier choice.

Hosting
Hosted: a subscription. Back room: servers, power and space.
Upkeep
Hosted: the vendor's job. Back room: ours.
The move
Planning, testing and staff training either way.

Running, growing, and staying safe

If something breaks

The vendor runs backups and standby copies, and the old servers stay available as a fallback for a few weeks.

When it grows

New warehouses or users are a plan change, not a hardware purchase.

Keeping it safe

The vendor keeps the system patched, and access is limited by role.

What the business gets

  • No ageing servers holding up the business
  • Updates and backups handled by the experts
  • A move with a safety net

These are the kinds of results the approach aims for, not measured results.

When we'd look again

If the hosted version blocks connections the business depends on, we'd fall back to running the system in the cloud with the vendor's approval.

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: Moving a software product between cloud providers

A startup's free cloud credits are running out, and another provider is offering new ones. We count the full cost of moving, including the team's time, before recommending it.

Read the next story