New Name

The product formally known as the CRM Migration Assistant has been renamed to the CRM JavaScript Conversion Assistant to more closely match its name with its functionality.

I am keeping the version number sequence the same.

New Price

The price has been reduced to $395 (from $495).

New Features

The following new features have been added:

Convert from CRM 2011

The most important feature added is the ability to connect to a CRM 2011 Organization and convert the existing JavaScript Web Resources.

The JavaScript can be uploaded back into CRM 2011 after you have finished the conversion process.

Conversion Alert Handling

The way conversion alerts are handled in the user interface has been enhanced. Any entity that contains conversion alerts is now highlighted in the event list:

The number of conversion alerts is displayed in the upper-right corner of the CRM 2011 window. This is actually a button. Clicking the button will cause the CRM 2011 editor to jump to the next Conversion Alert.

Markers have been placed in the left margin on lines that contain a Conversion Alert:

Next and Previous buttons have been added that allow you to jump to the next and previous Conversion Alert:

Improved Conversion Report

The Conversion Report has been modified and enhanced to provide a better view into the work that either has been performed by the conversion process or the work that will need to be provided. Here is how the Conversion Report is designed:

ROI

Provides a "guestimate" as to the amount of time and the CRM JavaScript Conversion Assistant saved you.

Conversion Alerts

Lists all of the conversion alerts found during the conversion process.

ActiveX Objects

Lists all ActiveX objects that were found, and their locations. This is good to know if you are planning to provide cross-browser support.

It should be noted that not all of these keywords identified in the Custom Code Validation Tool will be recognized by the CRM JavaScript Conversion Assistant. This is because the conversion process is verified by a series of unit tests ( 510 at the moment ) and I could not find code samples to verify the usage of the method or property. Since I could not find code, I could not write a test. Not test means no inclusion in the conversion process.

If you run into anything that I missed, please send me a code sample and I’ll get it added to the process as soon as I can.