Enterprise Administration > Windchill Export and Import > PTC Windchill PLM Connector - Creo Packages Administrator's and User's Guide > Creo Packages > Importing Packages > Introduction
  
Introduction
Creo Packages can import a package containing Creo Parametric data from one the following PLM systems:
• Windchill PDMLink
• Pro/INTRALINK
Mapping files can be created to map the package contents of objects to be imported in the target PLM system.
During import operations, Creo Packages provides a conflict handling and resolution infrastructure with the capability to map the following:
• Life cycle name
• Life cycle state
• Series
• Folder structures
After the import, the Creo Parametric model files and the associated metadata are available in the target PLM system. This imported design data may be new to the target PLM system, a new iteration of a previously shared design, or a new version of a previously shared design.
* 
It is not possible to import an earlier revision or iteration of an object if a later revision or iteration already exists on the target system. If you attempt to do so, following are the results:
• If you try to import an earlier version—An error message appears and the import fails.
• If you try to import an earlier iteration—An overridable conflict notice appears.
* 
PTC does not recommend using Creo Packages to export and import the first iteration of CAD documents with higher revisions. Creo Packages is primarily intended for exchanging CAD document content and maintaining the version history of CAD documents.
When revising a CAD document, there is an option to update version information only, without modifying the content of the document. Because CAD content can only be modified by performing a check-out operation and a check-in operation, an additional iteration is created. PTC recommends using the latest iteration of the previous revision. This keeps the version levels in synch for the identical CAD document content on the target and source systems. By default, Creo Packages displays a conflict in this scenario, which enables you to choose how to manage it.
You can adjust this behavior by setting the following Creo Packages preference for conflicts:
conflict.OVERRIDE_FIRST_ITERATION=USE_LATEST_ON_PREVIOUS
When this preference is set to INCLUDE (the default value), the first iteration is included in the import. In that case, the Creo Packages import process creates an additional iteration to honor the content along with the revise operation.