Export and import

Templates and bundles are Salesforce records rather than metadata, so Change Sets and source deploys do not move them. The Library and the Bundles tab both ship Export and Import actions, so you can promote templates from sandbox to UAT to production the same way you already promote code, with no paid release-management tool.

Each template and bundle carries a stable cross-org identity, minted at creation, that survives renames and org boundaries. Import matches on that identity, which is what makes re-promotion idempotent: re-importing the same template updates it in place rather than creating a duplicate.

For a repeatable pipeline, the CLI plugin does the same job from a script or a CI job. The in-org Export and Import described here is the right tool for a single template or a one-off move.

Export

• From the Template Library: every template card has a download icon, and you can multi-select to export several at once. Clicking it downloads a file named sliick_<TemplateName>_<YYYY-MM-DD>.sdt.
• From the Bundles tab: every bundle row has an Export link. The export includes the bundle header, its items, and every member template by default, so the target org has everything it needs.
• An include-files option carries watermark and image content along in the archive. If an image is too large for the platform’s limits, the export degrades gracefully with a “re-attach in the target” note rather than failing.

Org-specific references, meaning the test record and the auto-email recipient, CC, from-address and email-template values, are scrubbed automatically. Files exported by older versions of Sliick Docs still import into a current org.

Import

1. Open the target org’s Template Library, or Bundles tab, with Sliick Docs installed and Sliick_Docs_Admin assigned.
2. Click Import Template or Import Bundle.
3. Choose the .sdt file, then pick a conflict policy for templates that already exist in the target: Skip, Update, Duplicate or Fail.
4. Optionally run a dry-run first. Sliick Docs previews exactly what would be created, updated or skipped and commits nothing, so you can confirm the outcome before it touches the org.
5. Click Import. A summary modal lists what was imported, with any warnings: renamed on collision, unresolved merge fields, fields hidden by your permissions, or unresolved bundle members.

Folder paths referenced by an imported template are created automatically in the target, and org-specific references such as email templates and org-wide addresses are re-pointed to the target org’s equivalents.

What an imported template starts as

Status	Draft by default, so the receiving admin reviews and publishes deliberately. An optional auto-publish toggle activates templates on import if they pass validation, which suits a repeatable promotion pipeline.
Releases	Local to each org. A release is an immutable runtime snapshot and does not travel.
Test record	Unset.
Auto-email	Disabled, because the recipient, CC, from-address and template values are org-specific and are scrubbed on export.

Name collisions

With a Duplicate conflict policy, or for a first-time import where no identity match exists, if the target org already has a template with the same name the import auto-renames it to <Name> (Imported 1), then (Imported 2), and so on, and gives the copy its own fresh identity. The summary surfaces the rename so you can fix it from the Library.

The same auto-rename runs when you create a template with a name that already exists. See Duplicating and reusing templates.

Starter templates

The six ready-made starters are created directly from the gallery with no import step involved. See Starting from the gallery.