Know-how Apps Components Database Design Import

Database Design Import (DBDI) enables the migration of CATIA V5 data stored in a legacy database into 3DEXPERIENCE.

This topic specifies the import correspondences between V5 data types and 3DEXPERIENCE content types, and the import result. The statuses for import results are fully imported, partially imported, and not imported (-).

This page discusses:

Common Import Behavior

This section describes the behavior of CATIA V5 data stored in legacy databases imported into 3DEXPERIENCE that is common to all connectors.

V5 Data Type 3DEXPERIENCE Content Type Import Result
CATFct - - (Some behaviors are suppressed (binds, GenerateComponents, LogicalCombination), some are useless (LoadDocument), some have changed (FilterCatalog).
Technological Object in parts - -
Technological Object in assemblies - -

ENOVIA VPM V5 Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

ENOVIAvpm Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

X-CAD Design Management Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

SmarTeam Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

Adapter for X-PDM Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.