Between successive versions of the tool the underlying model of pinmap definitions may change.
In such a case, errors will appear inside the configurations when launching the tool after the update.
Figure 1. Old applications Migration
In the example above the pinmap configuration has changed: instead of pin name we are now using the PAD name. The file needs to be migrated.
In order to fix these errors, you must use the migration tool that is accessible using right click inside the configuration editor.
Figure 2. Launching migration
You'll be asked to confirm your choice.
Figure 3. Confirm migration
As a result the pin names have been adapted to the new names (pin name R16 has been replaced by the pad PJ[8]) and the version of the model is now changed and appears inside the converted file (here 2.0.0).
Figure 4. Migration result
As soon as the migration has been done, it is marked as not needed, and you cannot launch the migration anymore.
Figure 5. Unneeded migration
