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 :
Customer experience | Sales, Customer Insights,...
Answered

Best data migration strategy from Dynamics CRM 2011 to CRM 2016 on-premise

(0) ShareShare
ReportReport
Posted on by 20

Hi guys. 

We have currently carried out the CRM migration process from 2011 to 2016 on-premises in a controlled environment. However during the upgrade process step by step recommended by microsoft. Starting in 2011, 2013, 2015 and finally 2016, a long time has elapsed (several weeks) and the data in 2016 is out of date. 1. Where it was installed CRM 2013 and cloned the crm 2011 DB and went through the import process to 2013 and then within this same server using DB 2013 it was brought to 2015. Now we have on another server the DB 2015 migrated to 2016 and everything perfect, however the big problem here is the updating of the data. Any ideas or experience that can help us find a strategy to do it successfully?

Note: At this time the CRM 2011 environment is still productive and for now the UAT team is testing the CRM 2016 environment with slightly outdated data and when we have to deploy to production it will be necessary for the data to be updated in CRM 2016.

We appreciate yoru support or ideas. Thanks!!

I have the same question (0)
  • Swift but Sincere Profile Picture
    82 on at

    When are you going to move the users?  You should have migrated them at each step of upgrade.  If you don't you will have this problem forever.

  • Verified answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Hello,

    I had exactly a similar project when I had to migrate from CRM 2011 to CRM 8.2. In order to make it happen I used the following strategy:

    1. I created the following separated environments - 1 instance of 2013, 1 instance of 2015 and 1 instance of 8.2 (that's the new production).

    2. I performed the migration over the weekend. Created the backup of 2011, imported it to 2013, created backup of 2013, imported to 2015, created backup of 2015 and imported to 2016. I took me both days to perform the migration and apply changes to the code to address differences in API.

  • luiking85 Profile Picture
    20 on at

    In definitely I think it is the best way to maintain data integrity. Thanks Andrew!

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 March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 196 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 129

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans