In a recent article, the co-host of today's podcast, Peter Joeckel, shared his perspective that the Dynamics AX user base falls into one of three categories as it relates to their Dynamics 365 for Finance and Operations (D365FO) upgrade prospects:
That last cohort, the constrained mid-market customer with complex customizations, is staffed with tense IT managers harboring the legitimate fear that the financial losses tie to an upgrade-gone-wrong could do real harm to the business overall.
In this episode of our Dynamics AX to D365FO Upgrade Journeys podcast series, we meet Irene, an IT director at a manufacturer running a not-so-successful AX 2012 system (she preferred to leave her company out of the discussion). Their AX implementation began in 2012 RTM and "it was not an easy implementation," she says. They faced many of the hurdles you hope not to find when executing an ERP project: the lack of a change mindset, a conservative (and seemingly un-engaged) executive team, and some technical deployment problems. Since their less-than-satisfying go—live, they have been working to steadily bring back features and functions that should have been there from the start.
Now they face the prospect of an upgrade of some sort. Irene explains how she evaluated the two primary choices: upgrading to D365FO in the cloud or upgrading to AX 2012 R3. It's not a scenario (or an outcome) that will earn itself a flashy video at the next Microsoft conference, but it's one that might seem more believable for a certain set of AX customers weighing their options today.