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
Please let us know.
Hi Chitrarasan, thanks for your inputs. So this is what we have to do:
1. Upgrade from CRM4 to CRM2011
3. Then, ensure - everything works fine in CRM 2011
4. Then migrate from CRM 2011 to 2013 - here nothing to be re-written
5. Then, ensure - everything works fine in CRM 2013
6. Then migrate from CRM 2013 to 2015 - here nothing to be re-written
7. Then, ensure - everything works fine in CRM 2015 - AND WE ARE DONE!
Are the above steps right?
if so, typically, how long do you think will this take?
You steps looks correct apart from script make sure all custom workflows and plugins also works as expected.
Ok, so in each version, I need to check if the Custom Workflows and Plugins have got upgraded properly and is working - right?
Just want to add, you may also want review old customization and want to map it with the new OOB features, so for example filtered lookups, quick views, business rules to replace some of the script validations etc.
Before upgrade, you can utilize Custom validation tool & legacy tool which will tell you which of the code is not supported any more
You missed the step of applying 2013 SP1 - you can't install this directly as a slipstreamed install, and you can't upgrade to 2015 except from sp1.
And when you upgrade to 2013 you can choose whether to merge the base and extension tables for each entity. When you upgrade to 2015, you no longer have the option so this will be done if it has not been done already. This will take quite a long time - but totally depends on size of database (rows a re more of a factor here than GB - lots of emails or notes with large attachments are not such a big deal as sheer numbers of records. Look out for ActivityPointer as well as Customer Addresses, and all your main entities.
Any idea how big your DB is?
Doing any of this as an in-place upgrade is almost certainly a bad idea. So ideally, build a new 2011 environment, based on Windows and SQL server platforms that will run 2015.
Then migrate your CRM 4.0 database (leaving your live system in use), rewrite scripts, test again. Check everything is OK and export a Solution (unmanaged!) with the new stuff. Then upgrade the migrated platform to 2013, apply SP1, test again, upgrade to 2015. Time how long each upgrade step takes. Make final changes, including taking advantage of new features where they add value. Export Solution. Now you have a plan, you have tested all the steps will work, and can be done in the downtime you have available (eg over one weekend). And you have solutions ready to install at different stages. Start back from 2011, take a fresh copy of your CRM 4.0 database, and this time go through all the steps more quickly, and "for real".
Business Applications communities