> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/sfp/faqs/common-questions/email-templates-deployment-classic-vs-lightning.md).

# Email Templates Deployment: Classic vs Lightning

This document provides information on the issues that may arise during the deployment of email templates, particularly in the context of Salesforce Classic and Lightning.

## Packaging Lightning Email Templates

One of the known issues is that Lightning email templates cannot be packaged. This issue has been documented in the Salesforce CLI GitHub repository. For more information, refer to the following link: [Salesforce CLI GitHub Issue](https://github.com/forcedotcom/cli/issues/2902).

## Identifying the Type of Email Template

When working with email templates, it's important to identify the type of email template not from the file type, but from the type tag. This is because both types of templates are referred to as 'email', while one is of type 'SFX' and the other is of type 'Aloha'.

## Distinguishing Folders

Folders can be more reliably distinguished. They use 'EmailFolder' for Classic and 'EmailTemplateFolder' for Lightning as their opening tags. This distinction is important to note before deploying the templates.

Please ensure to take these precautions prior to deployment to avoid any issues.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/sfp/faqs/common-questions/email-templates-deployment-classic-vs-lightning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.