Upgrade or Migrate? How to Tell Which Your ERP Really Needs

Every ERP project starts with someone saying "we need to do something about our systems". The two real options on the table are usually upgrade or migrate — and most teams treat them as if they're the same kind of project at different scales. They aren't. They're different operating models, with different costs, different risks, and different reasons to choose them.

This is the first episode in our mini-series on the upgrade vs migrate question. Pete, Emily, and Nirav lay out the framing — what actually makes a project an upgrade versus a migration, why vendors keep mis-labelling one as the other, and how to do the cost comparison properly so you don't pick the wrong path on day one.

What we cover:

• Where the "we need to do something" conversation actually comes from — and why the trigger shapes the answer
• Why "do nothing" is also a decision (and the boiling frog problem that hides its cost)
• The real definition of an upgrade versus a migration — and the test that tells you which one you're actually doing
• Why most "upgrades" are migrations in disguise, especially anything with the word "cloud" bolted onto an existing product
• How to do the cost comparison properly — sticker price versus total cost of ownership versus the cost of doing nothing
• Why migration is sometimes the cheaper option, even though it never looks that way on the quote
• The hidden cost nobody puts on the spreadsheet — internal preparation

If you've been handed the "should we upgrade or migrate?" question — or you're about to be — this is the framing episode to start with. The rest of the mini-series will go deeper on each piece.