Basic Administration > Managing Data > Context Template Administration > Working With Context Templates > Importing a Context Template
  
Importing a Context Template
The context import and export functionality is intended to assist in the sharing of context information between systems. You can export specific settings and files from a current context into a template data file using the Export as Template action from the details page of a context. Then you can log in to another system and import the template data file using the Import Template icon on the Templates table.
The Import Template icon is available for project, program, product, and library context templates.
Use the following procedure to import a context template:
1. Navigate to the context under which you want the imported template stored.
If you want to import templates for a specific organization, select the desired organization under Organizations .
If you want to import templates for the entire site, navigate to Site .
2. Click the Templates link.
The Templates page appears.
3. Select the type of context template from the table view drop-down list on the Templates table.
4. Click import template icon from the top of the Templates table.
The import template window opens.
5. Enter the path to the template data file or click Browse to locate the file you want to import. You can import ZIP and JAR files.
* 
The file you select must contain all of the necessary information for creating a context template of the type identified in the View drop-down list. The ZIP file created as a result of executing an Export as Template action contains the necessary information.
6. Click OK to import the template and close the window.
The Templates table updates to show the imported template in the list of templates.
* 
If you import a project template from a previous version of Windchill ProjectLink, there is no visual indication on the imported template that it is a classic project template, rather than a Windchill ProjectLink 10.1 project template. Projects created using a classic project template will have limited functionality available compared to projects created with a Windchill ProjectLink 10.1 project template. PTC recommends that you rename the classic project template before it is exported to indicate that it is a classic project template, so that the distinction is clear after the classic project template has been imported. For a functional comparison of classic projects and Windchill ProjectLink 10.1 projects, see Converting Project Types.