How does Altium's Library Migrator handle components in an integrated library with different components using same symbols?

This article describes how the Library Migrator, used to convert local libraries to managed components in an Altium 365 workspace or a managed server (Concord Pro or Nexus), handles duplicate symbols being used across multiple components with different parameters.

Solution Details

The schematic library editor is used to create a symbol and a component, where the Design Item ID, a system property of a local library, is used to identify the component as well as the symbol. This is different compared to a Managed Component, where the symbol and component identifiers are separated. 

There are circumstances where a common, graphically identical symbol is used across multiple components. When the libraries containing these are migrated to a managed space, the Library Migrator automatically detects the symbols for each component that have duplicate graphical information within schematic or integrated library. As a result, the migration will result in only a single symbol with the generic name, Symbol, being released as a revision into the workspace, and thus, avoids any duplicates from being generated.

It is recommended to adjust the Name of the managed symbol revision after migration. Component parameters are unaffected since they are now grouped under the managed component’s parameters section.

Here's some reference links to Online Documentation related to this Knowledge Base Article:

• Library Migrator Improvements for single model libraries: https://www.altium.com/documentation/altium-designer/nfs-20-0library-migrator-improvements-ad?version=20.0#!single-model-libraries 
• Managed Components: https://www.altium.com/documentation/altium-designer/managed-components-ad 
• Library Migrator (Simple Migration): https://www.altium.com/documentation/altium-designer/librarymigrator-dlg-simplemigrationlibrary-migrator-simple-migration-ad