Enterprise Administration > Windchill Export and Import > Understanding Windchill Export and Import > Context Considerations > Controlling the Destinations of Imported Objects with Context Mapping Files
  
Controlling the Destinations of Imported Objects with Context Mapping Files
Normally, all objects are imported into the target context where the import process is launched. If you want to override this behavior, you can use context mapping. Due to security considerations, importing is always to a single project context.
The context mapping file allows the distribution of imports into multiple targets. The context mapping file is intended only for advanced users who cannot find another resolution. The context mapping file hardwires the context paths in your import set, so this approach requires detailed synchronization between the source and target system, which is typically only achievable via pilot to production export scenarios.
A better approach is to analyze what your transport needs really are, and then to streamline the creation of appropriate export sets. PTC does not recommend extensive use of the context mapping file functionality at your site.
The context mapping file has the following syntax:
<?xml version="1.0" encoding="UTF-8" ?>
<container-info>
<container>
<source-container>Original containerReference of the object
at the export site</source-container>

<target-container>containerReference of the context
where the object must be imported to at the import site</target-
container>
</container>

<container>
<source-container>Original containerReference of the object
at the export site</source-container>

<target-container>containerReference of the context where
the object must be imported to at the import site</target-
container>
</container>

<container>
<source-container>Original containerReference of the object
at the export site</source-container>

<target-container>containerReference of the context where
the object must be imported to at the import site</target-
container>
</container>
</container-info>
There can be more than one <container> element in the mapping file, as shown in the following example:
<?xml version="1.0" encoding="UTF-8" ?>
<container-info>
<container>
<source-
container>/wt.inf.container.DefaultOrgContainer=DefaultOrg/w
t.inf.container.ClassicContainer=Windchill PDM</source-
container>

<target-
container>/wt.inf.container.OrgContainer=Windchill_RD/wt.inf
.library.WTLibrary=Windchill PDM</target-container>
</container>
</container-info>