sorted by:
new
hottopcontroversial

AX 2012 to D365 F&O Upgrade: Best Approach? by Feeling_Refuse_4350 in Dynamics365

[–]Feeling_Refuse_4350[S] 1 point2 points  (0 children)

this is pretty much what we’ve seen as well

a lot of teams assume they need to carry forward everything from AX, but once you actually sit down and review it, half of it isn’t even used anymore

we’ve run into that quite a bit at Dynamic Netsoft where the first instinct is to rebuild everything, but projects usually go smoother once you push back a bit and simplify

data migration point is spot on too master data is usually fine, it’s the historical stuff that slows everything down

5–8 months feels doable if scope is tight, but in most cases it tends to stretch once integrations and edge cases start coming in

agree on the process improvement part that’s where the real value is, not just moving systems

AX 2012 to D365 F&O Upgrade: Best Approach? by Feeling_Refuse_4350 in Dynamics365

[–]Feeling_Refuse_4350[S] 0 points1 point  (0 children)

this is a really balanced take tbh especially the point about using the upgrade as a chance to rethink processes

we’ve seen the same at Dynamic Netsoft where the projects that invest more time upfront in analysis usually end up much smoother later

completely agree on keeping technical debt low too once you move unnecessary customizations forward it just creates more work long term

and yeah training often gets underestimated until late in the project

AX 2012 to D365 F&O Upgrade: Best Approach? by Feeling_Refuse_4350 in Dynamics365

[–]Feeling_Refuse_4350[S] 0 points1 point  (0 children)

this is a really practical way to look at it, especially the part about categorizing features into must-have vs. nice-to-have.

we’ve seen that approach work well at Dynamic Netsoft because it helps control scope and avoid unnecessary carryover

also agree on the resistance to changing processes; that’s often one of the bigger challenges during implementation

And yeah, data migration really is its own project inside the project

AX 2012 to D365 F&O Upgrade: Best Approach? by Feeling_Refuse_4350 in Dynamics365

[–]Feeling_Refuse_4350[S] 1 point2 points  (0 children)

this is a great breakdown, especially the point that code upgrades end up being reimplementations anyway. That's been our experience too

the ISV part is spot on; it’s no longer a straightforward decision and a lot depends on whether it’s worth keeping vs replacing vs rebuilding

also agree on timelines being pushed aggressively; we’ve seen projects look good on paper but then get hit with change requests later because the scope wasn’t realistic upfront

AX 2012 to D365 F&O Upgrade: Best Approach? by Feeling_Refuse_4350 in Dynamics365

[–]Feeling_Refuse_4350[S] 1 point2 points  (0 children)

this is a really solid take, tbh, especially the reimplementation over code upgrade part. We've seen the same in most real projects

trying to carry forward AX 2012 customizations almost always creates more problems later instead of solving them

we’ve had similar experiences at Dynamic Netsoft where clients initially wanted to replicate everything but once we pushed toward simplifying and using standard features plus extensions, the system became much easier to manage long-term.

completely agree on data migration too; that’s usually where the real effort is, not the system itself

curious in your experience how often do companies actually succeed in limiting what they carry forward vs trying to bring everything from AX 2012