Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Import from XML

You can copy Enterprise Architect model elements between models, for distributed development, manual Version Control and other benefits. You do so by importing the parent Package from an XMI (XML-based) file in any of these formats:

  • UML 1.3 (XMI 1.0)
  • UML 1.3 (XMI 1.1)
  • UML 1.4 (XMI 1.2)
  • UML 2.x (XMI 2.1)
  • MOF 1.3 (XMI 1.1)
  • MOF 1.4 (XMI 1.2)
  • Enterprise Architect's Native XML

You can also import the *.emx and *.uml2 files generated by tools such as Rational Software Architect (RSA) and Rational Software Modeler (RSM), as well as Canonical XMI 2.1 files, BPMN 2.0 XML files, Rhapsody and MagicDraw models, and XML files exported by ArcGIS.


Select your target Package in the Browser window, then:


Publish > Model Exchange > Import XML > Import Package from XML

Keyboard Shortcuts


Import a Package from an XML file



See also


Type the directory path and filename from which to import the XML file.

Import diagrams

Select the checkbox to import diagrams.

Strip GUIDs

Select the checkbox to remove Universal Identifier information from the file on import.

By removing the GUID, you can import a Package twice into the same model; the second import requires the checkbox to be selected, to apply new GUIDs to avoid element collisions.

Write log file

Select the checkbox to write a log of import activity (recommended).

The log file is saved in the directory from which the file is being imported, with the same name as that of the imported file plus the suffix _ import.log.

Import using single transaction

This option defaults to the setting of the 'Import using single transaction' checkbox in the 'XML Specifications' page of the 'Preferences' dialog. If you prefer, you can change the option from the default setting.

If the checkbox is selected, the XML file is imported in one transaction. This is not recommended for large imports.

If the checkbox is not selected the data items are imported separately; you can identify problem items without the whole import being blocked. If the import is likely to encounter locking issues, or if you are importing a large XML file, deselect the checkbox.

XML Specifications

Import Discussions by

This option defaults to the 'XMI/VC Import Policy for Discsussions' option in the 'General' page of the 'Manage Project Options' dialog.

This option will be enabled when the option 'Allow user to override if prompted' is selected in the 'General' page of the 'Manage Project Options' dialog.

If enabled, click on the drop-down arrow and select an option that determines how to import Discussions from XMI :

  • Merging from XML - select this option to retain the existing Discussions in Model and merge those in XMI
  • Restoring from XML - select this option to delete the existing Discussions in Model and import those in XMI
Model-Specific Options

Merge XMI

Click on this button to display two options for merging the content of the XMI file with the content of the selected Package.

  • 'Use Merge File' - Merge the contents of the XMI file with the contents of the Package using a Merge File
  • 'Direct Merge' - Merge the contents of the XMI file directly with the contents of the Package, without a Merge File
Merge Package Directly with XMI Merge Package with XMI Using Merge File

Treat Imported Datatypes

If you are importing from Rose XMI 1.1, click on the drop-down arrow and select the datatypes to add to the model.

Baseline Package after Import

Select this checkbox to open the 'Create Baseline' dialog, through which to baseline the imported Package once the import is complete.

Selecting this option also generates a merge file when exporting a Package to XMI 1.1 using the 'Export Package to XML' dialog.

Creating Baselines Export to XML


Click on this button to start the import.


Click on this button to close the dialog.


Click on this button to display this Help page.

Import Progress

Indicates the progress of the import.


  • In the Corporate, Unified and Ultimate Editions of Enterprise Architect, if security is enabled you must have 'Import XML' permission to import Packages from XML
  • If you are connected to a SQL Server repository, you require ALTER permission on the t_image table in Enterprise Architect, to be able to import model images
  • When you import an XML file over an existing Package, ALL information in the current Package is deleted first, unless you use the Use Merge File button; before you import the XML file, please make sure you do not have important changes that you do not want to lose
  • If you are importing an XMI 1.1 file that was previously exported with a UML_EA.DTD file, the UML_EA.DTD file must be present in the directory into which the XMI file is being written; an error occurs if the UML_EA.DTD file is absent

Learn more