The Project Nobody Planned For—but Everyone Depends On

This guide covers why direct import isn't possible, how to audit and retire templates before rebuilding, what merge field remapping requires across formats, and how to validate rebuilt templates against live record data before repointing automations.

Your templates are the engine of every email your team sends. When Salesforce retires Classic features, when your org migrates from another CRM, or when a merger brings two template libraries together, email template migration becomes the project nobody planned for, but everyone depends on. Salesforce cannot automatically convert Classic HTML templates into Lightning format—there is no import button, no bulk converter, no shortcut. Each template must be visually rebuilt, merge fields remapped, folder structures reorganized, and every rebuilt template tested before a single email goes out. This guide walks through each phase, so your team can migrate templates systematically without breaking the emails that drive pipeline, retention, and support.

Why Templates Cannot Be Directly Imported into Lightning

Classic email templates and Lightning Email Templates use fundamentally different architectures. Classic templates store raw HTML or Visualforce markup, while Lightning templates use a component-based structure with structured blocks for text, images, buttons, and dividers. This means Classic HTML cannot be parsed by the Lightning Email Builder—the builder expects structured components, not freeform code. As Salesforce Ben’s Lightning template guide explains, Lightning represents Salesforce’s strategic direction—Classic templates remain functional but receive no new features. Organizations migrating from external platforms face the same challenge: legacy HTML exports do not translate into Lightning components. Every template must be visually recreated using the drag-and-drop builder.

Auditing Your Template Library: What to Migrate, Retire, or Consolidate

Before rebuilding anything, audit your existing templates. Most organizations accumulate dozens or hundreds of templates over the years, many of which are outdated, duplicated, or unused. Export a complete list from Setup, then categorize each template: actively used and high priority, used occasionally, or obsolete. Check last-used dates and associated workflow alerts, Flow actions, and approval processes. Templates referenced by active automations must be migrated first—retiring them breaks live workflows. Consolidate duplicate templates that serve the same purpose with minor variations. A typical audit reduces the migration scope by 30–50%, saving significant rebuild effort. MassMailer’s comprehensive templates guide covers all template types and their use cases, helping you decide which formats to carry forward.

Rebuilding Templates in Lightning: Components, Letterheads, and Layouts

Lightning Email Builder uses a drag-and-drop canvas with structured components: text blocks, images, buttons, dividers, and social icons. Start by creating Enhanced Letterheads that define the header, footer, and brand styling shared across multiple templates. Then build individual templates by dragging components onto the canvas and applying your brand colors, fonts, and spacing. Column-based layouts automatically stack on mobile devices, making every template responsive without custom CSS. Trailhead’s letterhead and template project walks through the complete setup. For templates requiring custom HTML blocks or advanced layouts beyond Lightning’s native components, MassMailer’s Lightning Email Builder guide explains how to extend design capabilities while staying inside Salesforce.

Merge Field Remapping: Translating Syntax Between Template Formats

Merge field syntax differs between Classic and Lightning templates, and differs again when migrating from external platforms. Classic uses {!Contact.FirstName} syntax; Lightning uses the same format but restricts available fields based on the related entity type selected during template creation. External platforms may use entirely different syntax, like {{first_name}} or *|FNAME|*. Create a mapping document listing every field used in legacy templates, its source object, and the corresponding Lightning merge field. Verify each target field is accessible from the template’s related entity. Cross-object merge fields require lookup relationships—if the legacy template referenced account data from a contact email, confirm the Contact-to-Account relationship resolves in Lightning. MassMailer’s template creation guide details merge field insertion and object selection for both Classic and Lightning formats.

Folder Restructuring and Testing: Organizing and Validating Migrated Templates

Lightning templates use Enhanced Folders with sharing controls that differ from Classic’s folder structure. Classic folders cannot hold Lightning templates and vice versa, so you must create a parallel folder hierarchy. Enable Folders and Enhanced Sharing in Setup under Lightning Email Templates, then build folders organized by team, function, or campaign type. Assign folder access through permission sets to control who can view and edit templates. After rebuilding, test every template: send previews to internal addresses, verify merge fields populate with real record data, check rendering across Gmail, Outlook, and mobile clients, and confirm workflow alerts and Flow actions reference the new Lightning templates. Update every automation that pointed to Classic templates before deactivating originals.

MassMailer: Rebuild Templates Faster with CRM-Native Design Tools

Rebuilding dozens of templates in Lightning’s native builder works for simple designs, but organizations with complex layouts or high template volumes need faster tools. MassMailer’s Email Template Builder operates 100% inside Salesforce with advanced drag-and-drop components, custom HTML blocks, image hosting, social icons, and video elements beyond Lightning’s native component library. Templates are stored natively in Salesforce template folders, integrating with existing workflows, Flows, and email alerts. The builder supports merge fields from any standard or custom object, including cross-object relationship fields. Teams migrating from external platforms can recreate sophisticated designs without downgrading to Lightning’s simpler layout options.

Rebuild your template library in hours, not weeks.

MassMailer’s drag-and-drop builder recreates complex templates inside Salesforce with advanced components, merge fields from any object, and native folder storage—no HTML coding required. Install MassMailer free and start building →

Key Takeaways

  • Classic templates cannot be imported into Lightning—each must be visually rebuilt using the drag-and-drop builder.
  • Audit your template library first to retire obsolete templates and reduce migration scope by 30–50%.
  • Enhanced Letterheads define shared brand styling across multiple templates—create them before individual templates.
  • Merge field syntax must be remapped between formats, with cross-object fields verified against lookup relationships.
  • Lightning folders require Enhanced Sharing to be enabled separately—Classic folders cannot hold Lightning templates.
  • CRM-native builders like MassMailer accelerate migration with advanced components that are stored in native Salesforce folders.