Skip to content

Export and import

Templates and bundles are stored as Salesforce records, so Change Sets and metadata deploys do not move them. Use Export and Import instead. They let you move a template or bundle from a sandbox to UAT to production, with no extra release tool.

Sliick Docs recognises the same template in every org, even after a rename. So when you import a template that already exists in the target org, you can update it instead of ending up with a duplicate.

Moving templates often, or from a script? The CLI plugin does the same job and adds a dry run (see what would change before anything is written). In-org Export and Import is the easy choice for a single template or a one-off move.

  • A template: in the Template Library, click the download icon on the template’s card. You can also export several templates at once. The file is named sliick_<TemplateName>_<YYYY-MM-DD>.sdt.
  • A bundle: on the Doc Bundles tab, click the download icon on the bundle’s card. The file includes the bundle and every template in it, so the target org has everything it needs.

Images and watermarks travel in the file, whatever their size.

Some settings only make sense in the org they came from, so they are left out of the file, such as the test record.

If a template is restricted to specific records, you see Export - record scope won’t travel. The restriction cannot be exported, so the imported copy is unrestricted until an admin in the target org sets it up again. Click Export anyway to continue.

Files exported from older versions of Sliick Docs still import into a current org.

The Import templates dialog with a file chosen, Update existing selected, and the Activate templates on import checkbox

You need the Sliick_Docs_Admin permission set in the target org.

  1. Open the Template Library, or the Doc Bundles tab.

  2. Click the import icon (Import Template or Import Bundle).

  3. Choose the .sdt file. One file can hold templates, bundles or both.

  4. Under If a template already exists in this org, pick:

    • Update existing to add the imported content as a new draft version of the existing template (recommended), or
    • Create a separate copy to keep both.

    New templates are always created, whichever you pick.

  5. Optionally tick Activate templates on import to publish straight away (see below).

  6. Click Import.

A summary lists what was imported, with any warnings, for example a template that was renamed, merge fields that do not match a field in this org, fields your permissions hide, or bundle templates that could not be found.

The import summary listing an updated template, a created template, and a created template that was renamed because its name was taken

Folders a template belongs to are created in the target org if they do not exist yet. Email templates and org-wide email addresses are matched to the target org’s own.

StatusDraft, so an admin in the target org can review it and publish it. Tick Activate templates on import to publish on import instead. If any template fails its checks in the target org, the whole import is cancelled and nothing is imported.
Version historyNot carried over. Each org keeps its own published versions.
Test recordNot set.
Auto-emailNot carried (removed in 3.5). Importing a 3.5 file into an org on an older version turns that template’s auto-email off and clears its recipient and CC.

If the target org already has a template with the same name and the import creates a new one (for example with Create a separate copy), the new one is renamed <Name> (Imported 1), then (Imported 2), and so on. The summary shows the new name so you can rename it in the Template Library.

The same renaming happens when you create a template with a name that is already taken. See Duplicating and reusing templates.

The six ready-made starters come straight from the gallery, so there is nothing to import. See Starting from the gallery.