The move from Microsoft Dynamics AX to 365: Building a business case for the future

When I joined Element Material Technologies two-and-a-half years ago, the company had gone live on Dynamics AX 2009 fairly recently, in 2010. So when Dynamics AX 2012 came along, there just wasn't much of an appetite for an upgrade.

The task became to maximize AX 2009's capabilities and future-proof it, and we developed a lot of extra functionality for it, between internal developers and our Dynamics partner.

We are now at the point of moving forward, if for no other reason than heading off the expense of extended support for Dynamics AX 2009. But alongside that there are a ton of really good new features in Dynamics 365 for Operations that we could take advantage of, and that is the version we'll migrate to.


Requires FREE Membership to View

Become a Member Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About James Fleming

James is currently an Executive Vice President and CIO for Element Material Technologies. He started working with Dynamics AX (Axapta) in 2006 using version 3, and has implemented the product numerous times, in different organisations, over the ensuing years. Having been CIO for a number of FTSE250 organisations, James is an expert at guiding an organisation through selection and implementation of ERP and CRM systems, alongside managing multi-million pound IT organisations. He talks at numerous Microsoft events, alongside chairing the UK chapter of the AXUG, and was a founding member of the UK Dynamics Advisory Board. He was also the recipient of the Business Visionary Leader of the year award at the Microsoft Convergence EMEA conference in 2014.

Read full bio...