Import and export
A template can be exported as a portable JSON bundle and imported into another organisation. This is how a template moves between a test tenant and production, between a partner and a client, or between two organisations in a group.
What an export contains
Section titled “What an export contains”The bundle holds everything needed to reconstruct the template:
The template body, meaning the HTML that gets rendered.
The design document, if the template was built in the designer, so it stays visually editable after import.
Every image the template references, embedded in the bundle.
Export a template from its row menu on the Templates view. The result is a single JSON file.
Importing
Section titled “Importing”Import from the Templates view. An import always creates a new library entry rather than overwriting an existing template, so there is no way to import over something by accident.
If an image name in the bundle collides with one that already exists in the
target organisation, the import creates a numbered variant and rewrites the
cid: references in the imported template to match. The existing image is left
alone, and the imported template points at its own copy.
What does not travel
Section titled “What does not travel”An export is a template, not a configuration. These do not come with it:
Role assignments. The imported template is not made active for anything.
Assignment rules, which reference templates by identity and belong to the organisation rather than to any one template.
Banners and footers, which are separate objects applied at render time.
Version history. The imported template starts fresh.
Set those up in the target organisation after importing.
Using export as a backup
Section titled “Using export as a backup”Version history keeps the last ten published bodies of a template, which covers ordinary mistakes but is not a long-term archive.
For anything you want to keep indefinitely, export it. The bundle is a file you control with no retention limit, and it includes the images, which version history does not.
Exporting before a significant redesign is cheap insurance.
Downloading a standalone signature
Section titled “Downloading a standalone signature”A different kind of export exists for one person’s rendered signature: a
self-contained HTML file with images inlined as data: URIs rather than
attached.
| Where | What it produces |
|---|---|
| Templates view, download action | The live signature for any mailbox you name |
| The “My signature” pane in Outlook | The signed-in person’s own signature |
This is useful for pasting a signature into another system, keeping a personal copy, or sending somebody exactly what their signature looks like. It is a rendered signature rather than a template, so it contains one person’s real details and no placeholders.