HighLevel Snapshots can transfer workflows that use saved email templates. The enhanced flow imports supporting email-action copies in the background while keeping the original templates visible. To preserve template connections, transfer linked email templates before or together with their workflows. This guide explains how to transfer, verify, and safely update workflow emails through Snapshots.

TABLE OF CONTENTS

• What Is the Enhanced Snapshot Workflow Email Flow?
• Key Benefits of the Enhanced Snapshot Flow
• How Workflow Email Templates Are Handled
• Requirements and Limitations
• How to Transfer Workflow Emails and Templates
• How to Update Existing Snapshot Workflows
• Frequently Asked Questions
• Related Articles

What Is the Enhanced Snapshot Workflow Email Flow?

A Snapshot copies selected configuration assets from one HighLevel sub-account to another. When an imported workflow uses a saved email template, HighLevel handles the supporting email-action copy and its mapping in the background.

The original template remains visible in the destination's email template library, while additional workflow-specific supporting copies do not appear as separate templates.

Key Benefits of the Enhanced Snapshot Flow

Including the source template with its workflow helps keep transferred email actions usable while reducing duplicate templates in the destination account.

• Cleaner Template Lists: Supporting email-action copies stay hidden from the main template list.
  
  
• Reliable Template Mapping: Transfer linked templates with workflows to preserve the email-action connection.
  
  
• Reusable Automations: Deploy workflows and their email content across sub-accounts.
  
  
• Controlled Updates: Refresh and push selected changes without rebuilding an entire Snapshot.

How Workflow Email Templates Are Handled

Original templates, supporting email-action copies, and workflows are different assets. Understanding where each belongs makes it easier to verify a Snapshot import.

• Original email templates: Appear in the destination's email template library.
  
  
• Supporting email-action copies: Import and map in the background without cluttering the visible template list.
  
  
• Workflows: Appear under Automation → Workflows. Open each Send Email action to verify its content and template connection.

Requirements and Limitations

Workflow emails depend on their linked templates. Selecting both assets and using the correct transfer order helps prevent missing or unmapped email actions.

• Required Order: Transfer the original email template before or together with its workflow.
  
  
• Workflow-Only Transfers: Missing templates can prevent linked email actions from mapping correctly. Transferring a template afterward may not repair the connection.
  
  
• Linked Assets: Expand the Snapshot's folders and asset categories to confirm both the workflow and its relevant email templates are selected.
  
  
• Existing Assets: Review any Override or Skip choices carefully, then verify the email action in the destination.

How to Transfer Workflow Emails and Templates

Create a Snapshot from the source account, include the workflow and its linked templates, then review the destination before activating the imported automation.

1. Prepare the source. Open each workflow's Send Email action and identify its saved source template.
   
   
2. Create the Snapshot. In Agency View → Account Snapshots, click + Create New Snapshot. Name the Snapshot and select the source sub-account.
   
   

3. Select linked assets. Expand the available categories and nested folders. Select the workflow and its applicable email-template assets, then click Create.

4. Open the destination. Go to Agency View → Sub-Accounts. Open the destination's three-dot menu, select Manage Client, then choose Actions → Load Snapshot.

5. Choose the Snapshot. Select Pick a Snapshot, choose the applicable Snapshot, and click Proceed.

6. Select assets to load. Include both the source templates and their workflows. Expand folders as needed to verify the selection, then click Proceed.

7. Resolve conflicts. Choose Override to replace an existing asset or Skip to retain it. Review the selected choices and click Proceed.

8. Confirm the load. Type confirm when prompted and click Proceed to begin loading the Snapshot.

9. Verify the transferred assets. Find the original templates in the destination's email template library. Go to Automation → Workflows, inspect each imported Send Email action, verify the content and template connection, and send a test email before activating the workflow.

Important: Override replaces an existing destination asset and cannot be undone through the Snapshot load. Review conflicts and active workflows before continuing.

How to Update Existing Snapshot Workflows

Changes made in the source sub-account do not automatically update an existing Snapshot. Use Refresh and Push Update to apply selected changes to sub-accounts that previously received it.

1. Update the source workflow and any linked email templates.
   
   
2. In Agency View → Account Snapshots, locate the Snapshot and click Refresh. Select the changed workflows and templates, then confirm the refresh. Retry any failed assets if needed.
   
   
3. Click Push Update. Choose the previously linked destination sub-accounts and the related assets to push.
   
   
4. Check the destination workflows and Send Email actions after the update. Verify the email content and template mapping, then send a test email where appropriate.
   
   

Important: Do not routinely delete live workflows to apply an update. Investigate older mapping problems before removing anything. If an update removes workflow steps, contacts waiting on those removed steps may also be affected. Push Update applies to sub-accounts within your agency; external agencies must re-import an updated Snapshot.

Frequently Asked Questions

Q: Why is a Send Email action missing or not mapped after a Snapshot load?

Confirm that its original template was included before or with the workflow. Check the selected assets and load results, then investigate the mapping before replacing a live workflow.

Q: Is Sync Edits to Template preserved when I transfer a workflow?

The synchronization guide documents that the checkbox state is preserved in Snapshots and duplicated workflows. Verify both the setting and the template link in the destination.

Q: Are Conditional Sending rules retained in transferred email templates?

The enhanced-flow documentation states that Conditional Sending rules are preserved. Review conditional content in a test email after loading the Snapshot.

Q: What if an asset fails during a Snapshot refresh?

HighLevel marks failed assets separately and lets you retry eligible failed assets without restarting the entire refresh.

Q: Where can I check which Snapshot version and assets were loaded?

In Agency View → Sub-Accounts, select the destination and open Actions → Snapshot actions → View snapshot history. Choose a load to review its version and asset statuses.

Q: Do Snapshots transfer contacts and conversations?

No. Snapshots transfer reusable configurations and selected assets, not contact records, conversations, appointments, or live account history.

Related Articles

• Snapshots – Overview
• Load Snapshots Into Existing Sub-Account
• Refresh or Update Snapshots
• Organized Nested Asset Selection for Snapshots
• How to View Snapshot Load History in a Subaccount
• Sync Edits to Template for Workflow Email Actions