Skip to main content

Notifications

Announcements

No record found.

Customer experience | Sales, Customer Insights,...
Suggested answer

Delta Data Migration 2011 to 365

Posted on by 90

Dear Colleagues, I have a question and I would greatly appreciate your response if you know the answer or have some comments to share. We are currently in the process of migrating from 2011 on-premise to 365 online. All the data was already migrated from 2011 to 365 roughly a month ago. Users are still working in 2011 and updating records. We would like to find those records that are being updated in 2011 and apply the changes in 365 (i.e. do delta migration) until we switch over to 365 within the next couple of months. 

What is the best way to do this? I can think of 2 ways of doing this. Once through sql server and one through a console app.

The problem with the first solution is that we cannot use linked server because the 365 is on Azure and we don't have access to it. We do have a Managed SQL on Azure that the data from 365 is dumped into but again, I have been told that we cannot use linked server to access that database from another server which would be ideally the 2011 although we can directly connect to this SQL MI (i.e. managed instance). So to do this through SQL, I think we need to do some manual tasks by possibly running the first query on 2011 to get the data that is changed (based on ModifiedOn) and then export that data to a file. Provide that file to the second server (SQL MI), read from it and process it on 365 to find those record that need to be updated. And then possibly generate another file that identifies those records that need to be flagged on 2011, generate another file, and use that file to update 2011. 

The second solution would be to create a console app that connects to 2011, queries modified data from 2011, store it in memory somewhere (which I am not sure where and how) and then connect to 365, loop through the records, find the matching ones and finally flag the 2011 records that need to be migrated. 

I hope my solutions above make sense. My question is:

Which one of these solutions are better or you recommend? What am I missing here? Is there any reference materials you can provide to help? Any other suggestions?

Thank you so much in advance. Please let me know if you have any questions or need clarification on the above.

Homa

  • Suggested answer
    Thangamani Profile Picture
    Thangamani 507 on at
    RE: Delta Data Migration 2011 to 365

    Hi Homa,

       Data Migration is a big task and we need to be careful so that we will not miss any data.

    Actually It is a not  better idea to migrate the data from MSCRM 2011 to Dynamics 365 because between MSCRM 2011 to Dynamics 365 we have MSCRM 2013,MSCRM 2015 and MSCRM 2016 and we should have done a migration from MSCRM 2011 to either of any of these versions minimum to move it to D365.

    This kind of Data migration is mandatory to have before we get into D365 because there is a change in the Database structure from MSCRM 2011 to MSCRM 2013.In MSCRM 2011 we have 2 tables base and extension ,but in mscrm 2013 they merged together and we have a base table alone and the same way there is a change in activity related table as well.

    Coming to the point,Console application or SQL instance update will not help in this point and SQL update is not a supported way of doing it.

    There are some ETL tools are available to do the migration for these kind of scenarios.

    1)Kingswaysoft

    2)SCRIBE tool

    using above one of the tool you can achieve the delta data into D365 without any hurdles.

    Before going for this planning pls do a proper planning and understand the metadata structure so that you can map it properly between source[MSCMR 2011] and [D365].

    Hope this helps.

    Regards,

    Thangamani

  • Suggested answer
    a33ik Profile Picture
    a33ik 84,323 Most Valuable Professional on at
    RE: Delta Data Migration 2011 to 365

    Hello,

    I would suggest to use SSIS + KingsWay soft. You can filter the data by modified on (created or modified since the initial import) and import the sata to the destination.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans