Thank you for this video. How does this work in 365 on-prem? How do I get this installed? I am trying to merge two environments together and this tool would be so helpful. Update: I think I may have figured it out. I found the manual nuget package download and renamed it .zip and extracted the file and found the Migration Utility within the tools folder.
Hi, Can we add filter condition to fetch records based on some condition to migrate the data. In my DEV instance we have some test data as well and if we migrate the records to PROD all the records gets migrated. Can we exclude test data ? Thanks
When exporting accounts/contacts/opps, etc. how do you maintain the same record owners from the source to the target systems? When I attempted to reimport back into the target system, all records showed the owner as myself since I was running the tool under my name. But I need it to maintain the existing record ownership.
Hi Mike, I had a similar issue recently and I had to import the related entity separately (users in your occasion) first before importing the entity I initially wanted to import. I am not sure if there is a better way to do it. If yes please let me know! Thanks
Hello Sir, this one is a really amazing video. Well, we are looking for migrating from 2011 V5.0 (in premise) to latest 2017 V9.0 So I understand that I need to upgrade from 2011->2013->2013 SP1->2015->2017 So can I use the trial versions of each of 2013->2013 SP1->2015->2017 And then purchase a license for 2017, or do I have to purchase a license for each of 2013->2013 SP1->2015->2017 I appreciate your help on this.
I have manually created records in PROD and DEV for 1 entity. Since we have created manually the GUID of the records won't be the same in PROD and DEV. If I migrate the records using this tool from DEV to PROD will this update GUID of the record. We will add the condition to update the records based on Name field.
Thank you for this video. How does this work in 365 on-prem? How do I get this installed? I am trying to merge two environments together and this tool would be so helpful. Update: I think I may have figured it out. I found the manual nuget package download and renamed it .zip and extracted the file and found the Migration Utility within the tools folder.
Brilliant. Thank You!
Hi Derek, great video! Is it possible to use the tool to export data from CRM 2013 to CRM 2015?
Hi, Can we add filter condition to fetch records based on some condition to migrate the data. In my DEV instance we have some test data as well and if we migrate the records to PROD all the records gets migrated. Can we exclude test data ? Thanks
Hi how to change the environment ??? from DEV to UAT ?? i am just trying to figure out but till now i haven't got the answer.
When exporting accounts/contacts/opps, etc. how do you maintain the same record owners from the source to the target systems? When I attempted to reimport back into the target system, all records showed the owner as myself since I was running the tool under my name. But I need it to maintain the existing record ownership.
Hi Mike, I had a similar issue recently and I had to import the related entity separately (users in your occasion) first before importing the entity I initially wanted to import. I am not sure if there is a better way to do it. If yes please let me know! Thanks
Hello Sir, this one is a really amazing video. Well, we are looking for migrating from 2011 V5.0 (in premise) to latest 2017 V9.0
So I understand that I need to upgrade from
2011->2013->2013 SP1->2015->2017
So can I use the trial versions of each of 2013->2013 SP1->2015->2017
And then purchase a license for 2017, or do I have to purchase a license for each of 2013->2013 SP1->2015->2017
I appreciate your help on this.
I have manually created records in PROD and DEV for 1 entity. Since we have created manually the GUID of the records won't be the same in PROD and DEV. If I migrate the records using this tool from DEV to PROD will this update GUID of the record. We will add the condition to update the records based on Name field.
Yes thats's the reason we are going with this tool,
At the moment, I feel that using the tool is easier than trying to figure out which entities to be included for export/import. 😂
Hi Derek - can this tool be automated?
unfortunately not :/