Upgrade Options To Dynamics 365 Server, Version 9.0 (On-Premises)

There are three main upgrade options when upgrading to Dynamics 365 Server, version 9.0 (on-premises). Migrating by using a new instance of SQL Server, Migrating by using the same instance of SQL Server, and In-place upgrade. This blog post explains the benefits, drawbacks, and differences between the three approaches and ranks the upgrade options accordingly.

I consider migrating by using a new instance of SQL Server to be the best option for upgrading to Dynamics 365 Server, version 9.0 (on-premises) as it results in the least amount of downtime for users. The existing deployment can remain fully functional until the upgrade is completed and verified. A separate computer for Dynamics 365 Server, version 9.0 and a different instance of SQL Server are required, but these are worth having as they help the upgrade process run smoothly.

Migrating by using the same instance of SQL Server is the second best upgrade option. This option requires a separate computer for Dynamics 365 Server, version 9.0, but will upgrade in-place the configuration and default organisation databases using the same instance of SQL Server. If issues occur during the upgrade, you may need to roll back to the previous version to avoid significant downtime. This approach serves as a middle ground between the two other upgrade options.

I consider an In-place upgrade to be the worst and riskiest upgrade option. This option has the benefit of not requiring a separate computer for Dynamics 365 Server, version 9.0 or a different instance of SQL Server, but it poses great risk if upgrade issues occur as a rollback and reinstall of the previous version of Dynamics 365 Server will be required to avoid downtime. In-place upgrades also only upgrade the specified organisation and all additional organisations will be disabled and not upgraded until you run the Import-CrmOrganization Windows PowerShell command or the Deployment Manager. I do not recommend taking this upgrade path unless the other approaches are not available.

It is important to always backup your Dynamics 365 data before you upgrade to a new version of the product. Where possible, always migrate by using a new instance of SQL Server to minimise system downtime and ensure a successful upgrade. Only migrate by using the same instance of SQL Server or perform an In-place upgrade when this is not an option.