In this chapter, you learned various considerations when taking an upgrade project. These considerations include preparing a strong business case and combining with the deployment choices and accordingly making an informed upgrade decision. 

It's crucial to understand what exact process is intended to be followed based upon on the decision which is often between update, upgrade, or migrate.

We also shared insights on various kinds of updates available and how to apply them through the upgrade processes involving code upgrade and data upgrade. We also covered various phases of an upgrade project. In the planning phase, we covered the importance of managing customization, managing scope, business engagement, and impact analysis.

As highlighted in best practices and recommendations shared throughout the chapter, we would like to you to consider while moving to the latest version. According to us, the upgrade is a must and the deciding factor is the timing of such an initiative. It's best to keep upgrade plan as isolated as possible with other ongoing initiatives so that dedicated and committed resources are leveraged to achieve the goal.

One should always factor that Dynamics 365 upgrades are not like any Windows or legacy application upgrade, where you will start the upgrade and your system will back up on the new platform in a few hours. Here, extensive planning, preparation, and resources are required and often the need to engage experts/advisers from the field.