5 Reasons Your Second ERP Migration Is Easier Than Your First

Think back to your first ERP go-live. If you just winced, this episode's for you.

Every prospect meeting has that one person — arms folded, thousand-yard stare, still processing something that happened fifteen years ago. They know the current system is failing. Everyone hates it. And they've quietly decided they are not going through that again.

Here's the argument Pete and Nirav make this week: the project that person is dreading no longer exists. Your second ERP migration isn't your first one repeated — it's a different project that happens to share a name. The integrations are APIs now, not custom code. The data comes out of a real database, not off a spike with the tickets still on it. Round two is genuinely easier… but there are new ways to squander that advantage, and they walk through all of them. (Emily's off this week, so it's two seats today — the partner and the data side, which for a topic this data-heavy is convenient.)

What you'll take away:

• Why the second migration is a schema-to-schema shift, not the paper-and-spreadsheets-to-data slog you remember — and why that changes everything
• What modern migration tooling — and the first "migration agents" — actually change about moving data between systems
• The asset nobody puts on the project plan: your team already knows what they want, including the 21-click reprint they'll never mention unless you ask
• Integrations that used to mean a developer and a custom build, and are now a configuration screen or a single checkbox
• The cloud maths — the whole infrastructure project that simply disappears, and why your support costs usually fall through the floor
• The four ways to blow it: like-for-like customisations, complacency, second-system syndrome, and data hoarding
• Why fifteen years of history belongs in a read-only data warehouse, not your shiny new ERP
• What to actually do in the next 90 days if your ERP genuinely does suck

Whether you're staring down an end-of-life system like Dynamics GP or classic NAV, or you're just tired of a platform that's quietly holding the business back, this one's about doing it again — and doing it better.

Key moments

• (01:35) Same name, different project
• (06:11) Paper-to-data vs data-to-data: the schema shift
• (07:03) The end-of-life wave — GP and classic NAV are on the clock
• (13:00) Data migration is a different sport now
• (17:19) 21 clicks to reprint a work order (and why only your people know)
• (19:28) Integrations: from custom code to a configuration screen
• (22:33) The infrastructure project that just vanished
• (33:15) Every customisation has to re-justify itself from zero
• (38:02) Data hoarding, and the read-only warehouse that fixes it
• (41:41) The 90-day plan: start with a town hall, not a shopping list

Resources & links

• Nirav Shah and the team do these migrations for a living — AdCirrus ERP · nirav.shah@adcirruserp.com
• Pete writes (and moans) about ERP, data and governance at petenicholson.co.uk · info@petenicholson.co.uk
• Related listening: Upgrade or Migrate? (S4E12), ERP Data Migration: Best Practices & Common Mistakes (S1E18), and Why You Should NOT Customize Your ERP (S3E14).

Follow the show on Spotify, Apple Podcasts or YouTube, and leave a review if it was useful — it genuinely helps. No ads, no sponsorship, just two people who like ERP a bit more than is strictly healthy.

Hosted by Peter Nicholson and Nirav Shah (AdCirrus ERP). Emily Browning is off this week.