Dynamics GP to BC Upgrades Thoughts

Consider ALL of your Options
Having spent the better part of two years deeply immersed in the Microsoft Dynamics AX to D365 F&O conversation, I have had very little visibility into the effort to migrate from Dynamics GP users to Dynamics 365 Business Central (BC). That changed dramatically during a series of conversations with my new favorite Dynamics GP partner, Karen Riordan, the VP Sales & Marketing for Menlo Technologies.
What I found fascinating were the alternative views we brought to the GP to BC discussion, and how our individual Dynamics GP histories shaped our thinking in several critical areas:
- What does the future hold for GP customers and the GP partner channel?
- What are the critical factors to consider when deciding your companies ERP future?
- What are the critical factors that go into the decision making process for a GP customer planning their future?
In summary, we are both Great Plains OGs whose companies took different paths. Karen is more of a traditional GP partner that stayed the course and is now helping companies make the transition to BC. My Great Plains adventure took a different route, moving me first to Dynamics AX and now Dynamics D365 F&O.
The discussion regarding GP to BC upgrades came up casually at first. The tone of the conversation changed as we discussed the considerations and options that we do not see in the current migration marketing push.
Here are our key takeaways distilled from conversations that spanned several hours:
- Upgrades from Dynamics GP to BC are not a one size fits all proposition. There are dramatic and nuanced factors that we do not see discussed in the general messaging.
- GP customers would be best served if educated on a broader set of options presented to them when considering an .
Our guidance suggests that the first question a Dynamics GP customer should ask is, “why am I upgrading”? The answer could be one or more of the following:
- I have outgrown my GP software, and it is hindering the growth of my business.
- I want to move my ERP solution to the cloud.
- I am following Microsoft’s or my GP partner’s messaging.
Next, the following are essential upgrade factors to consider:
- There are no upgrades to a new ERP platform. With today’s complex ERP systems, “upgrade” is more of a marketing term than an exact technical definition. Even within product lines themselves, upgrades are now re-implementations. Also, upgrade toolsets are, in reality, often just generic spreadsheets and mostly marketing hype with no real technical substance.
- There are significant functional and technical reasons why companies outgrow GP. If that is the case, then it is critical not to make an incremental ERP move that does not address all of those technical and functional issues.
- If the primary motivation for a GP upgrade to move your on-premise implementation to the cloud, then a better solution may be to host your existing GP system. This solution can buy critical time before making a move to a new ERP system or be a permanent solution if the proposed Microsoft life span for GP fits your requirements.
The most important takeaway is that all upgrades are complicated and expensive. The real cost of the upgrade is never the cost of the new software, that is just the tip of the iceberg. In making that decision for your company, consider all of your options carefully and do not base that critical business decision on marketing materials promoting the latest shiny toy.
Karen Riordan, VP Sales & Marketing for Menlo Technologies, a Quisitive Information Technology & Services company.
Peter Joeckel, President of
TurnOnDynamics, a Microsoft Dynamics consultancy specializing in providing senior functional and technical resources for Microsoft Dynamics AX/D365 upgrade and rescue projects.
The post Dynamics GP to BC Upgrades Thoughts appeared first on turnondynamics.com.


