locked
CRM 2013 side by side upgradation RRS feed

  • Question

  • Hi,

    Currently we have dynamics CRM version 4.0 installed (Operating system is Windows server 2003) and we are using it since 5 years. So there are enough customizations available. Now we are planning to upgrade to CRM 2011 and then to CRM 2013.

    We have already prepared separate server which are copy of our existing crm 4.0 server, upgraded OS to 2008 and have upgraded all our customization from CRM 4 to CRM 2011 and CRM 2013. This our upgraded version is our UAT environment.

    Now as our CRM 4.0 is running in 2003, our infrastructure team told us, instead of upgrading OS from 2003 to 2008 and then to 2012, we should do following steps:

    1) Install vanilla version of CRM 2013 on separate server which have Windows 2012 OS.

    2) Import all customization from UAT environment to this new server using Solution.

    3) Do Import Organization by restoring database from UAT server.

    Now my question is, does this possible that we can do import organization from our already upgraded environment to vanilla version? If yes, will it create any issue in future?


    • Edited by Ravi MRC Friday, August 29, 2014 3:41 PM
    Friday, August 29, 2014 2:33 AM

Answers

  • Hello Ravi,

    Restore database and import organization from UAT to Production server will move all your customisations AND data from UAT to Production.

    Making the step 2 obsolete.

    unless you have production freeze, your data in UAT and your data in production will be different.

    So for production move this will be your approximate steps to perform - Assuming you have 3 SQL Servers for each version of CRM.

    1. Take a backup of CRM 4 Production Database.
    2. Restore the backup to CRM 2011 SQL Server.
    3. Using the Organisation Import tool, import the CRM 4 database into CRM 2011
    4. Apply the patch for CRM 2011 (unmanaged Solution exported from UAT CRM2011).
    5. Export the database from CRM 2011 instance and import to CRM 2013 server (Remember -data and customisations are overwritten so cerate a new org for migration).
    6. Using the Organisation Import tool on CRM 2013 import the CRM 2011 database into CRM 2013.
    7. Apply the patch for CRM 2013 (unmanaged Solution exported from UAT CRM2013)..
    8. Export the database from CRM 2013 UAT and import to Production
    9. Using the Organisation Import tool on CRM 2013 Production, import the CRM 2013 database into CRM 2013.

    Regars,

    Jithesh

    Friday, August 29, 2014 4:57 AM
  • Don't forget one veryimportant step in the upgrade to 2011.  Afterward, run the compatibility tool check!  About 0% of your JasvaScript and Plugins are going to be compatible with CRM 2013, so you'll need to rewrite all of them. 

    Also, CRM 2013 does a whole lot out-of-the-box that used to require custom JS, plugins, and workflows.  I'd recommend auditing your system to clean up the automation while you have to rewrite everything anyway.


    The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions.

    • Marked as answer by Ravi MRC Wednesday, September 10, 2014 1:45 AM
    Friday, August 29, 2014 8:09 PM

All replies

  • Hello Ravi,

    Restore database and import organization from UAT to Production server will move all your customisations AND data from UAT to Production.

    Making the step 2 obsolete.

    unless you have production freeze, your data in UAT and your data in production will be different.

    So for production move this will be your approximate steps to perform - Assuming you have 3 SQL Servers for each version of CRM.

    1. Take a backup of CRM 4 Production Database.
    2. Restore the backup to CRM 2011 SQL Server.
    3. Using the Organisation Import tool, import the CRM 4 database into CRM 2011
    4. Apply the patch for CRM 2011 (unmanaged Solution exported from UAT CRM2011).
    5. Export the database from CRM 2011 instance and import to CRM 2013 server (Remember -data and customisations are overwritten so cerate a new org for migration).
    6. Using the Organisation Import tool on CRM 2013 import the CRM 2011 database into CRM 2013.
    7. Apply the patch for CRM 2013 (unmanaged Solution exported from UAT CRM2013)..
    8. Export the database from CRM 2013 UAT and import to Production
    9. Using the Organisation Import tool on CRM 2013 Production, import the CRM 2013 database into CRM 2013.

    Regars,

    Jithesh

    Friday, August 29, 2014 4:57 AM
  • Don't forget one veryimportant step in the upgrade to 2011.  Afterward, run the compatibility tool check!  About 0% of your JasvaScript and Plugins are going to be compatible with CRM 2013, so you'll need to rewrite all of them. 

    Also, CRM 2013 does a whole lot out-of-the-box that used to require custom JS, plugins, and workflows.  I'd recommend auditing your system to clean up the automation while you have to rewrite everything anyway.


    The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions.

    • Marked as answer by Ravi MRC Wednesday, September 10, 2014 1:45 AM
    Friday, August 29, 2014 8:09 PM