CRM migration can be a daunting task as there are many things that can go wrong during the migration development process. For this reason, we are very excited to announce the general availability of a sample CRM migration package that you can take, use and even customize to your specific migration needs. We hope you find this useful.
There are a few challenges when trying to migrate CRM activity entities. In this blog post, we will try to address some of those challenges and show you some ETL design patterns that you can use for your CRM activity migration.
In this blog post, we will try to discuss the best practices that you can use to migrate CRM quote data from one CRM organization to another.
In this blog post, we will demonstrate how to use our software to migrate old KbArticle data to the new knowledgebase along with taking care of the versioning issue by creating new knowledge records and updating the latest version of the existing article records.
CRM 2015 Update 1 introduced the Alternate Key feature which can be used for Update and Upsert function as an alternative way to identify a CRM record in addition to the primary key. However there is one more scenario that this feature can be useful as well, but may have been overlooked, which is to use the Alternate Key for lookup purpose. In this blog post, I will show you how we have enabled the feature for lookup purpose.
We find it is quite tricky when working with recurring appointment. In this blog post, we will demonstrate how to migrate recurring appointment data. You may find it extremely easy to handle the tricky situation by using our software.
In our most recent release of SSIS Integration Toolkit v7.1 for Microsoft Dynamics CRM, we updated our support for SSIS 2016 and 2014. With this release there is a requirement to update your script component in order to work with the latest release.
When using FetchXML query to read data from Microsoft Dynamics CRM server, you might run into an error complaining "Paging cookie is required when trying to retrieve a set of records on any high pages". We have a solution for this error.