Migrating from ERwin to PowerDesigner

You can easily import a model built with ERwin into PowerDesigner with no loss of metadata. PowerDesigner allows complete flexibility through reliable linking and synchronization between conceptual, physical and object-oriented model approaches, providing outstanding model clarity and flexibility.

PowerDesigner supports the import of the following ERwin v3.x and higher model files, though v4.x or higher files are recommended, as they contain more metadata:

ERwin v3.x (.erx)
ERwin v4.x (.xml)
ERwin v7.x, v8.x, v9.x (.xml) – the ERwin model must be saved as Standard XML Format, and you must uncheck Only save minimum amount of information in the ERwin Save as XML File dialog box.

Note Before importing, we recommend that you review your ERwin model to see if any model object names are duplicated. It is good practice to avoid using duplicate names, and PowerDesigner will automatically attach a suffix to any duplicate objects that it encounters during the import process.

An ERwin logical model can be imported into either a PowerDesigner conceptual or logical model (CDM or LDM), while an ERwin Physical Model is imported into a PowerDesigner physical data model (PDM).

PowerDesigner cannot import the following ERwin objects:

ERwin triggers and stored procedures (not directly possible, but see the process in Post-Import)
ERwin reports
ER1 files
ERwin data sources
ERwin target clients

While PowerDesigner can import all your object display preferences and will retain color and font information, it does not support multiple colors for columns in a single table. The default column color will be used during the import.