CATIA Migration Checklist: The Short Version
A CATIA migration checklist turns the switch from CATIA V5 to Siemens NX into decisions made before the bulk move: a route per part class, a pilot on 30 to 50 files, the NX standard, acceptance checks per batch and the Teamcenter data load. This free 34-page whitepaper by inteliScience gives you twelve fillable checklists.
| Format | PDF, A4, 34 pages in English, printable forms with write-in fields and checkboxes |
| Contents | 12 checklists (A to L), a route guide for four routes, 14 acceptance checks with CAx-IF starting thresholds, batch record, remodeling acceptance, Teamcenter data load questions, sign-off form |
| Audience | Design leads, project leads, CAD and PLM administrators, Teamcenter administrators and quality teams moving from CATIA V5 to Siemens NX |
| Balance | Roughly 80 percent practical checklists, 20 percent inteliScience context |
| Languages | English, German, Romanian |
| Price | Free, no registration |
Download the Whitepaper
Download: CATIA to NX Migration Checklist (English, PDF) Deutsch: Checkliste für die Migration von CATIA zu NX (PDF) · Română: Listă de verificare pentru migrarea de la CATIA la NX (PDF)
Why a CATIA Migration Needs a Checklist Before a Translator
A CATIA migration is rarely stopped by the translator. It is stopped by decisions nobody made in time: which data has to move at all, which route each part class takes, which NX standard the data lands in, who checks a batch before designers build on it, and when CATIA is switched off for each program.
The translator itself is the easy part. Geometry and assembly structure convert well. Feature history, parameters, knowledge rules and publications do not, and NIST researchers described this limit of CAD data exchange in 2007: exchange standards carried pure shape and ignored the construction history, parameters, constraints and features that make up design intent. Translators have improved since. For working design intent, the gap has not closed.
So the work sits in decisions per data type, and in four workstreams that most plans cover in one line each: the NX standard, the people who switch, the parallel phase and the PDM data. We’d advise against converting a single production batch before those decisions exist on paper. The checklists in this whitepaper are how we collect them, and they work just as well with Siemens, your reseller, another provider or your own CAD team.
Four Routes per Part Class, Decided on a Pilot
Every part class takes one of four routes, and the translator route comes in two variants. The whitepaper’s route guide maps your answers to a candidate route, and the pilot on 30 to 50 deliberately difficult files then confirms or changes it.
| Route | What arrives in NX | Fits when |
|---|---|---|
| 1. Keep in the archive | Nothing new; a PDF, STEP or JT copy for viewing | The program ends, the part will not change |
| 2a. Direct translator | Bodies and assembly structure from CATPart and CATProduct files, no feature history | Large volumes of your own data with occasional changes |
| 2b. History-based migration tool | NX features where the rebuild succeeds; failed features as bodies | A large, cleanly modeled family that keeps changing |
| 3. STEP AP242 | Geometry, structure and semantic PMI when exported with 3D annotations | Customer or supplier data, or annotations that must stay semantic |
| 4. Remodel in native NX | A new parametric part on your template, compared with the converted body | Parts that change often or become the base for variants |
Drawings need their own line in the plan. With a direct translator or STEP they do not arrive as associative NX drawings. Siemens described in 2017 that its Content Migration Manager (CMM) and NX Migration (NXM) migrate drawings associatively to their parts and assemblies, so that route exists, and the pilot is where you find out what it delivers on your data.
Our clear recommendation: run the direct translator and STEP AP242 on the same sample before anyone buys a history-based tool. If only a small share of parts will keep changing in NX, remodeling those few costs less than licenses plus the repair of every failed feature.
What the Acceptance Checks Measure
Never accept a converted batch on the translator log. A log records that a file was written, not that the data is fit for work in NX. Checklist G compares every converted part with reference values measured in CATIA before the conversion, with thresholds agreed before the pilot.
The starting points come from the CAx Interoperability Forum’s recommended practice for validation properties (version 4.6, April 2023): 0.5 percent for solid volume and surface area, and 0.02 mm plus a 0.1 percent ratio of the model size for the centroid of parts larger than 20 mm. The number of components confirms that an assembly is complete. PMI, drawings and links are checked on a sample of every batch, because mass properties cannot see them. Failures are read by pattern: when forty parts fail on the same attribute, the mapping table is wrong, not the parts.
What the CATIA Migration Checklist Covers
- How to Use This Checklist
- What a CATIA to NX Migration Must Settle
- Checklist A: Scope, Deadline and Inventory
- Checklist B: The Route Decision per Part Class
- Checklist C: Prepare the CATIA Data
- Checklist D: The Pilot
- Checklist E: The NX Standard Before the Bulk Move
- Checklist F: Conversion Settings and the Mapping Table
- Checklist G: Acceptance Checks After Import
- Checklist H: Remodeling Key Parts in Native NX
- Checklist I: The Parallel Phase
- Checklist J: Training the Designers Who Switch
- Checklist K: The Teamcenter Data Load as a Project of Its Own
- Checklist L: Cutover per Program
- Migration Sign-off
- Working With inteliScience
Chapters 3 to 9 take you from the inventory to the first accepted batch. Chapters 10 to 13 cover what runs alongside the batches: remodeling, the parallel phase, training and the PDM data. Chapters 14 and 15 close each program with a signed record of what was moved, by which rules and who accepted it.
Who It Is For
Design leads who have a customer deadline for native NX data and CATIA programs that are still running. Project leads who have to turn “we are moving to NX” into a plan with dates and owners. CAD administrators who will own the NX templates, the translator settings and the mapping table. PLM and Teamcenter administrators who will load item numbers, revisions and relations from ENOVIA, 3DEXPERIENCE or SmarTeam. Quality teams who will be asked whether a migrated part can be released. If you are about to buy a history-based migration tool, fill in Checklists B and D first.
How to Use It
- Fill in Checklist A with your program managers and sort the inventory into part classes.
- Give each part class a candidate route with the route guide in Checklist B.
- Prepare 30 to 50 difficult files with Checklist C, including volume, area and center of gravity measured in CATIA, and run the pilot with Checklist D.
- Set up the NX standard and fix the settings and the mapping table before the first production batch.
- Accept every batch with Checklist G, remodel key parts with Checklist H, and sign off each program with chapter 15.
Plan the Teamcenter data load from the start with its own owner. It is the workstream that slips most quietly, because the CAD files look complete without it.
Sources and Method
The whitepaper uses official Siemens sources for Content Migration Manager, NX Migration, the CATIA V5 translator and the Designcenter rename of June 2026; the CAx-IF recommended practices for PMI (version 4.1, June 2024) and validation properties (version 4.6, April 2023); ISO 10303-242:2025; and a CATIA V5 reference for STEP export settings. The checklists, the route guide and the acceptance procedure come from the way our NX engineers plan and run migrations. No customer data, error rates or savings figures are included.
Read the Cluster Online
- Which CATIA V5 data survives conversion to NX, with scripts to check it
- What experienced CATIA users must relearn in Siemens NX
- What to validate in data migrated to Siemens NX
- From a body without history to a parametric NX part
Frequently Asked Questions
What should a CATIA V5 to Siemens NX migration checklist include?
A CATIA V5 to Siemens NX migration checklist should cover scope and inventory, a route decision per part class, data preparation, a pilot on a representative sample, the NX target standard, conversion settings and attribute mapping, acceptance checks per batch, remodeling of key parts, rules for running CATIA and NX in parallel, training and the Teamcenter data load. The data conversion is only one of five workstreams. The inteliScience whitepaper turns them into twelve fillable checklists, A to L, plus a sign-off form.
Direct translator, STEP AP242 or remodeling: which route fits CATIA V5 data moving to Siemens NX?
It depends on the part class, not on the file. Released parts that will not change stay in the archive; parts with occasional changes go through the CATIA V5 translator in NX and are edited with Synchronous Modeling; customer and supplier data, or 3D annotations that must stay semantic, go through STEP AP242; parts that change often or become the base for variants are remodeled in native NX. Run the translator and STEP AP242 on the same sample before deciding, and test any history-based tool on that sample too.
Can CATIA V5 drawings be migrated to Siemens NX as associative drawings?
Not with a direct translator or STEP, which bring geometry and structure but no associative NX drawings. Migration tools can: Siemens described in 2017 that its Content Migration Manager and NX Migration migrate drawings associatively to their parts and assemblies, so the result has to be checked on a sample against the released PDF. Many companies keep released drawings as PDF archive copies for parts that will not change and create new NX drawings from their templates when a part changes.
Is moving ENOVIA or 3DEXPERIENCE data to Teamcenter part of a CATIA to NX migration?
It belongs to the same program but works best as a separate project. Item numbers, revisions, release states, relations and the change history are not in the CATIA files; they sit in the PDM system and move in a Teamcenter data load with its own owner, schedule and acceptance. Decide early which revisions move, how part numbers map to item IDs and which release status migrated items get, and time the load so that parts and metadata arrive together.
How much does a CATIA to Siemens NX migration cost in 2026?
There is no reliable price per file, because translation runs in batch while the cost sits in the share of parts that fail the checks or need a feature history, plus NX standards, new drawings, training, the parallel phase and the Teamcenter data load. That share differs from one CATIA vault to the next. inteliScience measures it in an NX Migration Check on up to 50 of your parts and assemblies, which ends with an effort range by route and part class.
Next Step
Fill in Checklists A and B for your vault, or just send us your deadline and a rough picture of your CATIA data. Our NX engineers start with up to 50 of your parts and assemblies, typical and difficult ones, and tell you what survives, what the NX standard still needs and what the full migration will take, before anyone commits to a date.

