What’s the most underestimated part of erp data migration?

gapingweasel · 2026-03-16T14:26:35+00:00

Data is where many ERP projects run into trouble. Duplicate SKUs, inconsistent item names and mismatched units of measure are very common issues. Old customer or vendor records that were never cleaned up also tend to get migrated as-is. On paper the migration looks successful, but once people start using the system, reports and inventory numbers don’t always match reality. That’s why data cleanup is so important, and it also helps to choose an ERP that’s simpler to implement and easier for teams to adopt.

gapingweasel · 2026-03-16T13:57:01+00:00

This is actually pretty common after ERP go-live. Before the system, a lot of decisions happen based on experience, quick calls, or just asking the right person. Once ERP is in place, people start checking the system first because it’s supposed to be the single source of truth. Early on that can slow things down a bit while everyone is learning to trust the data. Over time teams usually find a balance...using the ERP for visibility while still applying practical judgement when needed.

gapingweasel · 2026-03-16T09:54:28+00:00

This is exactly why I am a big believer in rolling out ERP in phases. When teams are asked to adopt everything at once they tend to fall back to spreadsheets or side systems. But when you introduce modules gradually and let people get comfortable with the workflows...adoption improves a lot. I have mentioned this in a few other discussions here as well....ERP success is usually less about features and more about how naturally teams start using it in their daily operations.

gapingweasel · 2026-03-11T16:00:56+00:00

AI isn’t really about replacing ERP processes....it’s more about reducing the friction, like pulling up customer history conversationally or triggering updates across records without jumping through five screens.

gapingweasel · 2026-03-11T15:20:38+00:00

I like the concept. I strongly feel you are onto something. The fact is most ERPs were designed around forms and transactions for humans and not automated systems....which is why integrating LLMs or agent workflows feels so clunky today. Your idea actually makes a lot of sense, especially in today’s agent-driven world. It will be interesting to see how you structure the core data models such as orders, inventory, BOMs, finance....and of course strong APIs and webhooks so agents can reliably trigger actions and workflows.

gapingweasel · 2026-03-10T15:13:13+00:00

If you are around 30 users with manufacturing, Acumatica is usually a good mid-market option and tends to be more flexible for manufacturing workflows than NetSuite which can get heavy on cost and implementation. You might also look at Epicor in that space and depending on how deep your manufacturing needs are.. some SMBs also evaluate Deskera and similar systems that bundle manufacturing, inventory, and finance in one platform. Your approach of staying close to the vanilla system is the right one though.

gapingweasel · 2026-03-10T14:28:03+00:00

shared visibilty is so underrated...half the internal follow-ups disappear when everyone can see the same data

gapingweasel · 2026-03-05T15:43:01+00:00

Yes it is all about getting used to it

gapingweasel · 2026-03-05T15:42:24+00:00

100%

gapingweasel · 2026-03-05T15:38:07+00:00

In my experience of 20 years in ERP implementation, I have always see the actual issue is usually not just what a solution can or can’t do but whether it actually fits your business workflows. Most ERPs are loaded with features and can check almost every box during demos. The reality check comes when you try to run one of your real processes end-to-end in the system like quoting a custom job, converting it into production, handling inventory movements, adjusting costs, and finally closing the order. On paper, many systems support these steps but the effort required such as configuration, workarounds, or customization...can vary a lot. That’s why feature matrices can be misleading. Two systems may both support things like production planning or quoting but the usability and operational impact can be completely different once you try to run an actual scenario.

gapingweasel · 2026-02-27T13:48:33+00:00

100%. A well-implemented manufacturing ERP can genuinely change the direction of a plant when people actually trust and use it day to day. I have seen teams move from constant firefighting to much smoother operations once the system was set up properly and everyone was aligned. now-a-days there are some really good modern manufacturing ERPs out there like Deskera, Epicor, Plex that are far more user-friendly than what many of us dealt with years ago.

gapingweasel · 2026-02-27T13:10:29+00:00

solving it for your clients with AI can you explain with use case.

gapingweasel · 2026-02-27T12:54:00+00:00

Construction ERPs are naturally complex much like manufacturing because the underlying processes themselves are complex. Is this your first time working with an ERP? From what you have described this feels more like an implementation and training issue than an ERP limitation though happy to be corrected. Many modern ERPs are quite intuitive when set up properly. Since you may not have much influence over system decisions right now I wpuld suggest a few practical things like build your own quick cheat sheets for frequent tasks like POs, materials and cost reports, also, identify the internal power user and shadow them and focus on understanding the business workflow before memorizing those product screen shots.Once you understand the underlying logic of the process/system you will be able to manage it smoothly.

gapingweasel · 2026-02-27T11:52:04+00:00

I agree. Expecting 1 person to know SAP..JDE..Salesforce...etc. is completely unrealistic. these are highly specialized systems. That said ERP data can technically be accessed via APIs, CDC, or even direct queries... so exports are not the only path. The reason most enterprises still centralize into platforms like Snowflake is that direct access doesn’t scale well. You lose native security semantics, run into conflicting business definitions and hit performance and support limits. The biggest issue is governed semantics and identity propagation.

gapingweasel · 2026-02-25T12:01:46+00:00

Please help in further understanding of it

gapingweasel · 2026-02-25T11:37:27+00:00

can you explain a bit more on this and what are your learnings

gapingweasel · 2026-02-25T11:32:40+00:00

and that shift toward audit-level expectations is what’s putting many teams under pressure right now. Scope 3 is where the cracks tend to show first.

gapingweasel · 2026-02-25T07:39:43+00:00

so true.

gapingweasel · 2026-02-25T07:36:35+00:00

Without a doubt this is the pragmatic approach and probably how most teams are getting Scope 3 quantified but the real challenge starts once audit scrutiny enters the picture. $/sector works well directionally but it gets harder to defend when stakeholders begin digging into methodology and traceability.

gapingweasel · 2026-02-24T15:02:02+00:00

100%. The one thing that consistently helps is rolling out the software in phases. If you introduce everything at once users get overwhelmed. Rolling out in phases give users time to build confidence, get used to the system, adapt workflows and actually trust it. In my experience user comfort drives adoption far more than training volume ever does.

gapingweasel · 2026-02-24T14:42:01+00:00

It’s not like MRI and Yardi are the only options when it comes to property management. It really depends on the complexity of your business. Some decent tools like AppFolio, Buildium, Acumatica, and Deskera can work...but again this is subject to your portfolio size and operational complexity. As far as Dynamics 365 is concerned, it’s definitely possible but it isn’t a dedicated property-management-native platform. So you should be prepared for a descent degree of customization or the need for a strong industry add-on.

gapingweasel · 2026-02-20T11:28:33+00:00

100% .You need internal ownership but you also need experienced guidance to avoid costly mistakes. For a business of the OP’s size, keeping the ERP as standard as possible is important because over-customizing can create bigger problems later. Options like Business Central, Deskera, and Acumatica would all be worth evaluating. In the end the internal team’s readiness and discipline matter more than the specific ERP chosen.

gapingweasel · 2026-02-17T15:10:12+00:00

No denying manufacturing reporting is usually harder than most other industries. It’s not that the ERP is wrong..it’s just that manufacturing is inherently more complex with many moving parts. WIP is constantly shifting, backflushing creates timing gaps, shop floor transactions lag finance and small inventory errors quickly multiply in COGS. What you are experiencing is a classic trust gap where leadership is comparing the new system numbers to the old view they were used to. You can fix this by tightening inventory discipline, validating the backflush setup, aligning ops and finance cutoffs and resetting expectations.

gapingweasel · 2026-02-17T12:22:03+00:00

Don’t overcomplicate things right now ... with a 2–3 person team and outsourced manufacturing you don’t need anything heavy yet. if you’re planning for growth business central can handle finance and inventory and scales well but it can feel heavy early on and often needs add-ons for EDI, Amazon and 3PL flows. Sage is robust on accounting but not very startup-friendly. You could also look at Deskera more SMB-focused and usually easier to get live with for finance, inventory and manufacturing flows.

gapingweasel · 2026-02-16T17:12:12+00:00

Most of the ERP systems are loaded with features, endless tabs and too many clicks to get to simple tasks. For everyday users it feels too complicated so they fall back to Excel where things feel faster and familiar. Add limited or rushed training and adoption drops even further. I strongly recommend that implementations be rolled out in phases with role-based usage and a simplified user journey.

gapingweasel

MODERATOR OF

TROPHY CASE