If you are an existing user of one of Microsoft’s ERP solutions, you’re probably already aware of their plan to shift customers away from their current platform to its new D365 Central application. It’s estimated that approximately 50,000 customers will be affected and forced to upgrade their solution to either the D365 on-premise or cloud option.
Users may have initially welcomed the move to upgrade their legacy system to a newly developed ERP solution. However, when you scratch the surface, everything isn’t a clear as it may seem. You see, if you are currently running Dynamics Soloman (DL), Dynamics Great Plains (GP), or Dynamics Axapta (AX), then the simple upgrade you may have expected isn’t included in the project plan. Interestingly, D365 Central isn’t new technology either. It’s just clever marketing.
Upgrading to Microsoft Dynamics D365 Central
As with any legacy software, updates will dry up, new versions will no longer be developed, and support will eventually cease. But upgrading to D365 from any other Microsoft solution is essentially the same process as implementing a new ERP solution. Taking Microsoft up on their offer to adopt D365 Central is a lengthy and expensive process.
It’s no secret that Microsoft acquired DL, GP and AX after they had already been initially developed. Once purchased, they were re-branded, repackaged and tools added along the way to match either evolving business requirements or new legal regulations. This means it’s not a straightforward move from one solution to the other because of the different architecture within each solution.
Migrating to Dynamics 365
To upgrade to D365 Central there’s a 12-step process required to complete any migration. This means you’re basically starting back at square one. Businesses will have to go through the tiresome process of doing a stock take again, devising a new upgrade scoping plan, creating a staging environment to host and then testing the upgrade – and that’s before any customisation comes into consideration.
It’s estimated that even a vanilla migration is expected to last between nine and 12 weeks. If your solution is customised, you can expect the process to take up to 24 weeks. Any organisation that requires a complete overhaul of their ERP solution can expect the process to take up to nine months! That’s a serious amount of work and resources that an SME will have to allocate to the project, simply to upgrade their solution.
Microsoft Dynamics D365 Costs
Another important factor that SMEs will have to consider is cost. If you are an SAP Business One user and wish to upgrade to the latest version, all you pay is the consultancy charges from your partner – assuming there’s an existing contract in place. However, with Microsoft things are more complex.
First, you need to pay for every module you require in the solution. It’s not an all-in-one tool you can access under a single license like SAP Business One. Then, there’s a license type per module that also needs to be factored in. On top of that are other costs which are not always clear, such as the pricing structure in the marketing module which is priced per contact, rather than a per user. As you can see, the costs quickly add up.
Moving to SAP Business One from Dynamics
There is an easier and more cost-effective option for any user of a Microsoft ERP solution that wants to avoid a prolonged and costly overhaul of their solution. That’s moving to SAP Business One. With SAP Business One you can enjoy lower total cost of ownership. You won’t be forced to migrate away from your on-premise solution either. Your business will be more efficient by using a true ERP solution with technology that isn’t simply connected but genuinely integrated.
There’s never been a better opportunity to move away from a repackaged business management solution to an ERP solution with a clear future and direction for its customers. You can find out more about moving to SAP Business One and future-proofing your business by getting in touch with me at email@example.com or a member of our team at 01932 212 777.