web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Upgrading to 2016 on premise from 2013 on premise

(0) ShareShare
ReportReport
Posted on by

Hi All

I was looking for help online for how to upgrade from 2013 on premise to 2016 on premise. I'm using crm for a while now but never had the chance to perform an upgrade so I'm a little bit anxious about this. I have now installed CRM 2015 on a new server and got stuck with the migration. Read a few articles about this and I'm a little bit confused about migrating the organization over to the new server. The confusing part is what is happening with my current 2013 system? Read somewhere that this is a one way process and once you migrate the organization, it will automatically upgrade to 2015. This is the part I don't understand. Will this affect the current organization, will I be able to keep the 2013 version up and running in the same time, until I have the 2016 version up and running?
Thank you so much

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Rickard Norström Profile Picture
    on at

    Hi,

    If you're have a new server installation (both CRM server and SQL server) you can keep your current CRM available, you're not screwing that up. However, I wouldn't keep using it while you're doing the upgrade since data changed in the old CRM won't be present in the new CRM.

    As for how you should do it, there are instructions in the Implementation guide. How are you planning to do it as of now. In short there are three ways of doing it, in place, same SQL server and migration.

    The inplace upgrade will screw up your current server park, it will upgrade the CRM server and lift the organization database, you can go back to the old database if you have a backup and then install a new CRM 2013.

    The "same SQL database" version is that you install a new CRM 2015 (and later 2016) server and point that server to the old SQL server, it will then update the database to the new system and you can't go back to the old system unless you have a backup as in the in-place upgrade.

    Migration means that you install a new system (CRM and SQL servers) and then backup the organisation database (yourCRM_MSCRM) from the old SQL server, restore it to the new SQL server and then import in using the deployment manager tool.

    After you've done that you need to do it again to a 2016 server.

    Hope it helps

  • Community Member Profile Picture
    on at

    Hi Rickard, thank you so much for that, it does help a lot. I'm planning to do it as migration. I have already built the servers for 2015 and just about to import the organization. We use loads of 3rd party addons(will probably need less with the new 2016 version) and also some in house built plugins and just want to make sure that all work fine after the upgrade. Because I've never done this before the plan is to do a test upgrade first to get comfortable with everything. Then scrap that and do the proper upgrade.

  • Rickard Norström Profile Picture
    on at

    Sounds like a good plan, break a leg!

    Regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans