For the latest updates to this post please visit the original posting here: Using the Legacy Feature Check Tool to Prepare for CRM 2013

As you prepare to upgrade your Microsoft Dynamics 2011 environment to CRM 2013, it is very important to review your implementation for legacy code. CRM 2011 was backward-compatible to CRM 4.0 plugins, custom workflows, and 2007 endpoints; however, these legacy web services endpoints are no longer supported with CRM 2013. Endpoint addresses will need to be updated to CRM 2013 addresses.

The Dynamics CRM team has provided a Legacy Feature Check tool to check for CRM 4.0 plugins, custom workflows, 2007 service endpoints, and ISV folder support for custom web applications. This tool should be utilized in conjunction with the Custom Code Validation Tool that will test for any unsupported JavaScript.

The upgrade process to CRM 2013 will run these tools as part of the EDW checks, but we recommend running them prior to upgrade to allow time to resolve these customizations prior to upgrading. During the upgrade, the system checks will produce a screen displaying verification results. If there is any existing 4.0 code, or if 2007 service end points are discovered, the EDW will list them and halt the upgrade.

The specific results will be found in the log files here:


The results would look similar to this:

Steps to run:

  1. Download the Legacy Feature Check tool.
  2. Run the Microsoft.Crm.LegacyFeatureCheck.exe file from command with parameters:
    1. /out:Results.xml – this will output the results to a specified xml file
    2. /org:orgname – indicates the org to run against; if not specified, all orgs will be checked
  3. The full command should look like this:

By running the legacy feature check tool proactively, you will be able to better prepare for the new release.

For more information regarding Microsoft Dynamics CRM 2013, check out our 2013 resources and also sign up for PowerConnect.

Happy CRM’ing!

The post Using the Legacy Feature Check Tool to Prepare for CRM 2013 appeared first on PowerObjects.