Content Migration Manager > Automation surface
NXOpen.MigrationManager has no public classes
The NX Open reference documents a MigrationManager namespace described as "Provides classes and interfaces
for Content Migration Manager (CMM)", but in the releases checked it contains no classes or interfaces.
There is no public NX Open API to drive a CMM migration. Automate CMM through its own command-line tools
(cmmBatch; see the knowledge-base articles in this folder, which cite the user's guide section
"Part VII: Appendices > Command line utilities > Batch migration"), and read results back from the
Teamcenter cmm template objects (CMM2Session, CMMAttributes, in tc-data-model/).
Evidence (what was checked, and only that)
| Reference | Classes listed | Page |
|---|---|---|
| .NET (NX 2512) | NamespaceDoc |
https://docs.sw.siemens.com/documentation/external/PL20250429951538534/en-US/custom_api/nxopen_net/a33485.html |
| C++ (Designcenter 2606) | none | https://docs.sw.siemens.com/documentation/external/PL20251024323638784/en-US/custom_api/nx_open_c_plus_plus_ref/a34924.html |
| Java (NX 2512) | none | https://docs.sw.siemens.com/documentation/external/PL20250429951538534/en-US/custom_api/open_java_ref/nxopen/migrationmanager/package-summary.html |
NamespaceDoc in the .NET reference is the generated documentation stub for the namespace itself
(source file MigrationManager_NamespaceDoc.cs), not a usable class.
Not checked: the Python reference, and releases other than the three above. The nearest real API is
NXOpen.Features.SheetMetal.MigratedPanelBuilder, which edits sheet-metal panels that came from the
I-deas Content Migration Manager; it does not run a migration.
Source: https://docs.sw.siemens.com/documentation/external/PL20250429951538534/en-US/custom_api/nxopen_net/a33485.html · retrieved 2026-10-02