# Export and move mappings ## What you'll do You download one template with everything it needs as a single ZIP: its FHIR Connect mappings, its OPT, the IG packages of its FHIR profiles and the ConceptMaps it translates codes with. You then upload that ZIP into another Atlas or engine, for example from a test tenant to production. ```{figure} ../images/ship/export-dialog.png :class: screenshot :alt: The dialog "Export template" for International Patient Summary with the options FhirConnect mappings, OPT file, FHIR profiles (disabled) and Terminologies with four ConceptMaps Exporting the International Patient Summary template of the demo. ``` ## Before you start - Export works with or without versioning. Exporting a *release* needs versioning and a connected Git repository (see {doc}`release`). - To upload elsewhere you need write access to the mappings there. ## Steps ### Export a template 1. Open the export dialog from one of these places: - the Workspace top bar, **Export** (only the icon on narrower screens), for the open template; - the Engine state page: select the template and click **Export** in its action row. ```{figure} ../images/ship/export-topbar.png :class: screenshot :alt: The Workspace top bar with the Export button framed **Export** in the Workspace top bar. ``` ```{figure} ../images/ship/export-state.png :class: screenshot :alt: The templates table of the Engine state page with the selected template's action row and its Export button framed **Export** on the Engine state page. ``` 2. Choose what goes into the ZIP. Atlas looks up the linked profiles and ConceptMaps when the dialog opens and ticks those that exist. | | Option | Contents | |---|---|---| | [1]{.callout} | **FhirConnect mappings (YAML)** | *The context mapper and every linked model mapping.* Disabled when the template has no context mapper. | | [2]{.callout} | **OPT file** | *The raw operational template XML.* | | [3]{.callout} | **FHIR profiles (IG packages)** | The stored IG packages that provide the models' profiles, plus their stored dependencies, each with its size and number of profiles. Disabled with *No mapping uses a profile from a stored IG package.* when there are none. | | [4]{.callout} | **Terminologies (ConceptMaps)** | *The ConceptMaps the mappings' terminology references*, listed by URL. Disabled with *No mapping references a stored ConceptMap.* when there are none. | Amber lines name what the template refers to but the engine doesn't have: *Not in any stored package:* for profiles, *Not found in the engine:* for ConceptMaps. Those can't be in the ZIP. 3. Click **Export** [5]{.callout}. The browser downloads the ZIP and the dialog closes. On the **Releases** tab of the Versioning page, **Export ZIP** on a template release downloads the template as of that release, with its mappings, OPT and ConceptMaps (IG packages aren't versioned). ### What the ZIP contains The engine builds the ZIP in the layout of its Git repository: `templates/