CAD Migration to Siemens NX: The Short Version
A migration to Siemens NX succeeds when the migrated data behaves like native NX data: geometry that CAM and simulation accept, structure that can be changed, attributes that ERP and Teamcenter read, PMI and drawings that downstream teams trust. Batch validation against explicit acceptance criteria proves it, not a sample. inteliScience runs these validations with DOCUFY DQM and NX Open tooling.
| What you migrated | What to validate | How |
|---|---|---|
| Solids and surfaces | Closed bodies, no gaps or slivers, mass properties, tolerance stack of the translation | Geometry checks, batch |
| Assemblies | Component resolution, constraints or positions, reference sets, no missing components | Structure checks, batch |
| Metadata | Attributes present, mapped and formatted, revision consistent with Teamcenter | Attribute checks, batch |
| Layers and categories | Objects on the NX template categories, not on source-system layer numbers | Layer checks, healing |
| PMI | Semantic where the source had semantic PMI, attached, complete | PMI checks |
| Drawings | Views regenerate, sheets and templates allowed, title blocks from attributes | Drawing checks, sample review |
The Problem: The Translator Reports Success, the Process Does Not
A migration to Siemens NX is declared complete when the last file has been converted without an error message. Three months later the department knows better: a supplier reports a surface model where a solid was expected, CAM stalls on sliver faces, the ERP import rejects half the assemblies because the material attribute arrived as free text, and a drawing regenerates with a view that no longer matches the model.
None of these are translator failures. Translators move geometry and metadata; whether the result complies with your NX rules is a separate question that the translator was never asked. Answering it after the fact, per part, by hand, is how migration budgets double.
Why CAD Migrations Create Quality Risks
Three mechanisms produce most of the quality problems we see in migrated NX data. Not every source system behaves the same, and the mix differs per project, so the list is a map, not a diagnosis.
Native versus imported data. Siemens supports neutral formats such as STEP, IGES, JT, DXF, DWG and 3MF and direct translators for systems including CATIA V4 and V5, Creo, SolidWorks and Inventor [1]. A neutral-format import brings geometry, not design intent: the feature history is gone, expressions are gone, and the result is a “dumb” body that behaves differently under modification than a native NX part. Direct translators and migration tooling can preserve more, depending on the source system and the scope of the project.
Mapping decisions made once, applied to everything. Attribute names, layer numbers, material lists and naming conventions differ between systems. A mapping table written in week one is applied to ten thousand parts in week six. A wrong entry does not fail loudly; it produces ten thousand consistently wrong parts.
Legacy data quality travels. A part that violated the old system’s rules will violate NX rules too, now without the person who knew why. Migration is the one moment when the whole vault passes through a pipeline, which makes it the cheapest moment to check and heal it.
What to Validate After the Migration
Geometry
For each migrated body: is it a closed solid where the source was a solid, or did it arrive as sheets? Are there gaps, overlaps, sliver faces below your minimum, self-intersections or non-manifold edges? Do mass properties match the source within an agreed tolerance? Does the body survive a simple modelling operation, an offset or a shell, without failing? Geometry that passes these checks can be handed to CAM and simulation; geometry that fails needs healing or re-import with different settings.
Model structure
Assemblies must resolve every component, positions or constraints must match the source, reference sets must exist where NX templates expect them, and no component may point to a file that did not migrate. For parts, decide what “structure” means for imported data: if the history is gone, structure rules about feature order do not apply, and your checks should know that.
Relationships
Interpart links, WAVE links, family tables, drawing-to-model associations and Teamcenter item relationships are where migrations silently lose information. Validate that every drawing still points to its model, every assembly to its components, and every managed dataset to the right item revision.
Naming
Part numbers, component names and dataset names must follow the NX and Teamcenter conventions after mapping. A naming check over the migrated set finds mapping errors faster than any manual review, because errors are systematic.
Attributes
Attribute validation is the most valuable check in a migration and the most neglected. Required attributes present, values from the approved lists, formats correct, units consistent, revision aligned with Teamcenter. The mapping table is tested here; every systematic gap in the results is a line in that table.
Layers
Source-system layer numbers rarely match the NX template. A layer check identifies objects outside the target categories, and this is a family where healing pays: moving objects to the correct layer is deterministic and safe in batch.
PMI
Where the source system had semantic PMI, verify that it arrived semantic: attached to faces, complete with tolerance and datum reference, organized in model views. Where the source had only 2D annotations, decide explicitly whether PMI is created in NX or the drawing remains the master; our article on MBD versus the 2D drawing covers that decision.
Drawings
Migrated drawings must regenerate, sit on allowed sheets and templates, take their title blocks from attributes and show no out-of-date views. Drawings are also where a sample review by a human is still worth the time, because a view that regenerates can still communicate the wrong thing.
Standard parts
Fasteners and standard components that were library parts in the source system should become reuse-library parts in NX, not thousands of unique bodies. A standard-part check on the migrated set shows how far the mapping got.
Large Migrated Datasets: Batch Validation
A migration produces the largest batch validation job an NX organization will ever run, and it should be run as one. Both Siemens’ Check-Mate and DOCUFY CAx Quality Manager execute checks in batch mode [2][3]. The batch run answers the questions that decide the project: how many parts pass, which rule families fail systematically, and which failures the mapping can fix versus which need healing or manual work. DQM adds automated healing for supported checks, which for layers, attribute defaults and formats can resolve the systematic share of the findings in the same run [3].
Acceptance Criteria and Quality Gates
Acceptance criteria turn “the migration is done” into a measurable statement. We write them per rule family before the pilot batch, for example: 100 percent of parts have all required attributes with valid values; 100 percent of assemblies resolve; geometry checks pass on at least the agreed share of parts, with the remainder listed for healing or re-import; every drawing regenerates. The quality gate is the same one you use for new data: check results written to Teamcenter, in DQM’s case to Item Revisions and the Validation Master Form since version 2026.1 [4], so that a migrated part is released under the same conditions as a native one.
Migrating to NX and unsure what “done” should mean? As a DOCUFY partner we define the acceptance criteria, run the baseline batch over the migrated set, heal what can be healed and report what cannot, before the data reaches production. See how a DQM evaluation on your migrated data works
Where DQM Fits
DOCUFY CAx Quality Manager brings more than 450 configurable best-practice checks, guided correction, automated healing for supported checks and batch processing of large data volumes into Siemens NX [3]. In a migration it is the validation and healing layer over the migrated set: the checks are configured to the target NX rules, the batch run produces the compliance picture, healing resolves the systematic findings, and the remaining deviations are reported for manual work. Vision4NX technology from inteliScience is integrated into DQM and explains findings in the terms of the applicable rule.
Where inteliScience Siemens NX Expertise Fits
Migrations expose the parts of NX that most departments rarely touch: translator settings, template design, attribute mapping into Teamcenter, NX Open tooling for bulk corrections that no configured check covers. We have built tools that restore colour palettes across NX versions, strip confidential expressions before data exchange and align STEP imports to defined coordinate systems in headless batch runs, which is the kind of work a migration needs alongside the checks. As an official DOCUFY partner we combine that NX Open depth with DQM configuration.
Migration Quality Checklist
- Acceptance criteria written per rule family before the pilot batch.
- Pilot batch on a representative sample, failure rates published.
- Mapping table corrected from systematic findings, pilot repeated.
- Full batch with healing for layers, attributes and formats.
- Geometry failures triaged: heal, re-import, or manual.
- Assemblies resolved, relationships verified, drawings regenerated.
- PMI and drawing master decision documented.
- Standard parts mapped to the reuse library.
- Check results written to Teamcenter as release conditions.
- Residual list handed over with owners and dates.
Frequently Asked Questions
What should be validated after a CAD migration to Siemens NX?
Geometry integrity, assembly resolution and relationships, naming, attributes, layers, PMI, drawings and standard parts, each against the NX rules the organization uses for native data, and each in batch over the whole migrated set rather than on a sample.
Does a STEP import into NX preserve the feature history?
No. Neutral formats transfer geometry and some metadata, not the feature history or expressions. The result is a body without design intent; checks about feature structure do not apply to it, and modifications behave differently than on native parts. Direct translators and migration tooling can preserve more depending on the source system.
How do you check thousands of migrated NX parts?
In batch. Check-Mate runs in batch over many parts; DOCUFY CAx Quality Manager processes large data volumes in batch and heals supported findings automatically. The batch run produces the compliance picture per rule family that the acceptance criteria are measured against.
How much does migration validation cost?
The effort scales with the number of rule families and the size of the set, not with the number of parts alone, because findings are systematic. DOCUFY’s 90-day DQM evaluation package covers company-wide use with customizing and consultant support; the NX Open tooling for bulk corrections is scoped per migration.
Migration validation vs ongoing CAD quality checks: is it the same thing?
Same checks, different moment. Migration validation runs once over everything and heals the systematic share; ongoing checks run on every part from then on. Organizations that set up the rules for the migration usually keep them as their permanent quality gate.
Next Step
Talk to our NX team about acceptance criteria for your migration
Related Topics
- Siemens NX migration
- Siemens NX CAD quality: how to automate model validation
- DOCUFY CAx Quality Manager for Siemens NX
- The Siemens NX CAD Quality Playbook (whitepaper)
References
- Siemens, “CAD interoperability,” Designcenter NX product page, retrieved 16 September 2026.
- Siemens, “CAD model design validation,” Designcenter NX product page, retrieved 16 September 2026.
- DOCUFY GmbH, “DOCUFY CAx Quality Manager,” product page, retrieved 16 September 2026.
- DOCUFY GmbH, “NX-Datenqualität sichern: Neue Version des DOCUFY CAx Quality Managers” (DQM 2026.1), 30 March 2026.