Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
we are trying to upgrade our existing CRM which is on v8.2 and wanted to do Parallel upgrade to v9.1.
Before we can start our upgradation would like to know, can i directly export the organization from 8.2 and restore it on v9.1 server and Run in Import organization ?
Requesting your immediate feedback.
No, when you apply 9.1 on 8.2 version it will prompt an error message as the base version(9.x) is not applied.
Best practice, is to apply the cumulative update first for 8.2 then upgrade to 9.0 also apply the cumulative updates for 9.0 post which you can apply 9.1-
Microsoft Dynamics 365 On-Premises Cumulative Updates
In this way, it will have all the fixes and updates required for the application.
We are not doing inplace upgrade our approach is to do Parallel upgrade which will be follow as below.
1) Restore the DB from v8.2 to directly v9.1 and run the import organization on v9.1 Server.
Requesting your expert opinion on this.
we can do that but make sure all the cumulative updates are installed in 8.2 and 9.1 servers.
NOTE: cumulative update are recommended to be installed because there are some known issues while importing which are resolved.
We are currently upgrading several 8.2 organizations for a customer.
You most likely cannot go directly from 8.2 to 9.1, in fact we discovered we could not even go from 8.2 to 9.0 Update 10 directly.
The route we have taken(and we tested several different upgrade paths) was to upgrade 8.2.x -> 9.0 Update 0.9 -> Update 0.27.
We do not know yet if it's possible to jump to 9.1 as this was not the goal of this upgrade project but we couldn't upgrade any of the 7 organizations(8.2) on the platform directly to 22.214.171.124 which at the of the project planning/decision was the latest version/update available.
This at least will help you get to 9.0.x and closer to moving to 9.1.x.
Best regards. /Philip
As an addition to our upgrade process on these 8.2 organizations(one of the db's upgraded all the way from CRM 4.0) with various of customizations done on them:
1. On the 8.2 DB's we have always needed to run the following SQL script on the DB prior to the upgrade to v9.0:
SET IsOfflineInMobileClient = 1
WHERE ObjectTypeCode IN (953, 954) AND IsOfflineInMobileClient = 0
2. One of the organization kept failing to upgrade which was due to Full text search.Solution is to disable Full text search via Settings - Administration - System Settings and wait 24h as there is a job run within that time.(confirmed via MS Support ticket)You can probably force this via script as the FT search is manageable via SSMS.3. If having issues with Updates 0.9+ , like SalesPatch, the best approach is by commenting out the "salespatch" from the solutions.xml of the that update package(described as a workaround in other posts with issue to SalesPatch/MarketingPatch), Update the org without it and then try manually to import the solution e.g. salespatch via GUI on the faling org as this will give you the real issue(opposed to the Update wrapper logs).In our case we found 2 organizations that in some way during their journey had modified "out of the box) security roles, Saleperson, Salesmanager e.g.With the above method we could clearly see that these roles was the cause of why the SalesPatch failed to apply.Our solution was to actually remove these roles in the source v8.2 source DB as the upgrade to v126.96.36.199 re-created them, and then the upgrade to Update 0.10+ (U0.27 in our case) went without a problem.
Business Applications communities