How can we help?

Michael Ochs

On May 12th, we released the latest version of Migration Dynamics which incorporates a lot of feedback from partners that we’ve received in the first half of the year since we released the initial version. The latest version includes some key new features as well as fixes for specific problems when migrating to Dynamics 365. We’ve also created a definitive guide to choosing a new AMS/CRM for your association. Below are the release notes for the latest version.

New Features

  • Support for Filtering Data to be Migrated – We’ve added the ability for users to specify a query for entities on the entity grid view prior to migrating. This allows filtering of the data being migrated on an entity by entity basis. If no filter is specified all applicable records will be migrated as usual. This has been the top feature request for Migration Dynamics from users and should make migrating deltas of data easier as well as migrating small subsets for testing.
  • Migration Path Algorithm Improvements – We’ve made dramatic improvements to the migration path algorithm which determines the best way to order data when migrating that will reduce the possibility of orphaned records. A common example of this sort of orphaning of data is when you have a parent entity i.e. Account that has a related system or custom entity in a 1:N relationship i.e Orders. Since orders rely on their parent account to be present when the data is migrated Migration Dynamics can intelligently make the decision to migrate accounts before orders. Likewise, the order entity relies on products and units of measure and price lists. Migration Dynamics is smart enough to migrate these entities in the correct order to reduce the possibility of orphaned records being created. Of course, the algorithm can only do so much. Circular relationships will always have orphans so Migration Dynamics tracks these and restores their relationship as the parent records are migrated.
  • Migrating Saved/System Views – Custom / Unmanaged System views (not user views) can be migrated using Migration Dynamics in the 1.1.6 version. Note: Managed and non-custom views have to migrated as part of the solution in which they exist. This feature allows system views that have been customized by the customer to be migrated the same as user queries in previous versions. In this version, we also added logic to remove attributes specified in views that no longer exist on the target system. Migration Dynamics already handles ignoring fields that don’t exist in the target when migrating data, but previously if those fields were included in a saved view migrating the saved view would fail due to the field not existing in the target system.
  • Improved Error Handling & User Notifications – In this version, we added easier to understand error messages and email links to the for easier reporting of errors to Cobalt. The latest version also includes messages which indicate when the current version of Migration Dynamics needs to be updated so clients can receive updates faster.

Don’t make your next decision about a new AMS/CRM harder than it needs to be!

Our Definitive Guide to Choosing a New AMS/CRM for Your Association will help you avoid the costly process pitfalls and biggest headaches of wasted effort. The guide offers practical tips for research, RFPs, vetting vendors, and everything you will need to make a choice with confidence for your team. View or download this free resource today!

View the Guide Now

Bug Fixes

  • Chrome Browser Issues – Previous versions of Migration Dynamics failed to show the entity list on the last screen of the Migration Wizard when being run in later versions of Chrome. We’ve fixed this browser specific issue in the latest version.
  • Opportunity Products Fail to Migrate when Opportunity is Won or Lost – In previous versions of Migration Dynamics there was a problem with migrating opportunity products if the parent opportunity entity was already migrated with a Won or Lost status. The issue here was that the correct integration endpoints were not being called when reopening the parent record and subsequently closing the opportunity again. We’ve resolved this issue in the latest version.
  • Static Marketing List Members Fail to Migrate – Marketing list members were not migrated correctly in previous versions of Migration Dynamics. This issue has been resolved in the latest release. In previous versions, you could migrate dynamic marketing lists without a problem, but static marketing lists would migrate without their related contacts, leads or accounts. This has been resolved in the latest version.

The latest update of Migration Dynamics includes some very powerful new features. The most impressive is the ability to filter the data being migrated. In previous versions, it was all-or-nothing when it came to migrating a specific entity. Meaning if only a handful on records from an entity failed to migrate you had to migrate all the data again to correct the errors. This is also useful if you want to only migrate some data from one environment to another which can be useful for validating your migration setup before performing the full migration or moving configuration data from one environment to another.


Keep updated with our news & articles.