No. D365 is available on three different deployment models:
Cloud – Azure hosted by Microsoft
Cloud is the flagship deployment option for D365. Subscription-based SAAS, allowing fully automated updates through Lifecycle Services (LCS) potentially reducing costs for hardware, infrastructure maintenance and implementation.
Cloud & Edge allows data to be stored locally for those vital processes that need the fastest responses while taking advantage of the Cloud services like automatic updates. Data synchronisation options are available to synchronise local data to the Cloud.
Local Business Data is particularly attractive to businesses who need to ensure, for geographical or political reasons that their data is stored entirely locally and within their control.
The time-frame will vary from customer to customer. No one implementation will be the same.
That said, there are some general timescales you can apply based on evaluating your current solution as indicated below. These ballpark timelines can be ratified by working with your implementation partner on an Analyse project.
Following the Microsoft approved upgrade process, this should take between 8 and 12 weeks.
Depending on the true size and need for the modifications between 12 and 24 weeks.
You should evaluate the need for the quantity and type of modifications you have and should be pushing for standard solution wherever possible. This project starts at 36 weeks.
It should be noted that the upgrade routines, as standard, work from the latest versions of the software (with a couple of exceptions). There are upgrade paths available from both AX2009 & AX2012. The ability and completeness of these paths are directly related to which of the type of previous implementation you have gone through based on the options listed in the answer above.
There is such a wealth of additional functionality between older solutions and D365 that you should take an Analyse phase to assess your true requirement. Upgrade models will then become clearer, whether that be a code upgrade or a recommendation for a re-implementation.
The more preparation you can do the smoother and simpler the upgrade will be. Key considerations should be:
Using a business process modelling tool such as Columbus Rapid Value will give you a real head start on understanding your key business processes, how they link and areas where you will be able to take standard solution rather than modifications.
Your partner should work with you to help you see how your current licence will transition across versions.
You will need their support throughout the process, ensure they are on board and supportive from the very beginning. Awareness workshops work wonders.
There are 4 phases to any upgrade plan; Analyse, Execute, Validate and Go Live, with key stages to each phase.
Every Columbus upgrade has its own project plan and team. Each customer’s requirements will vary therefore the size of each phase will flex.
The best way to do upgrade and implement a new solution is through the right partnership.
We know how to make your investment in Microsoft Dynamics 365 work for you, today and tomorrow, whichever version you choose.