Copy email templates between Zoho CRM modules
Clone a template from Leads to Contacts, replace its merge fields and test the result without rebuilding the design.
You have a follow-up email for Leads and need the same design for Contacts. Recreating the layout wastes time and makes it easy for the two versions to drift apart.
Zoho CRM supports cloning email templates across modules. Our older guide used exported HTML as a workaround; that is now an alternative for managing an external design, rather than the first step needed to copy a CRM template.
Clone the existing template
Open Setup, then Customization and Templates. Find the source email template, open its clone option, give the copy a clear name and select its destination module. For example, clone a Leads follow-up into Contacts.
These are the native steps described in Zoho's email template guide. If the option is missing, check the template area and your access with the CRM administrator before rebuilding the message.
Give the two templates names that make their purpose visible, such as “Enquiry follow-up — Leads” and “Enquiry follow-up — Contacts”. Naming them only “Copy of follow-up” makes later maintenance harder.
Replace the module-specific merge fields
Copying a design is not enough to make the message correct for another record type. Review the greeting, subject, body, buttons and signature for values supplied by the source module.
Use the destination module's field picker to replace those references. Check more than the person's name: company details, record owners and links can also depend on the record context.
Consider what should happen when a value is missing. A greeting that works with a complete test record may become awkward for a real contact without a first name. Write the message so it still reads naturally, or decide how the process will prevent an incomplete record from using it.
Send a controlled test
Preview the cloned template with a destination-module record and send it to a test inbox you control. Compare the received message with the source version.
- Does the subject contain the intended values?
- Are all placeholders resolved, including links and the signature?
- Do buttons go to the right destination?
- Does the message remain readable on a phone?
- What happens when an optional field is empty?
Use a Leads record for the Leads version and a Contacts record for the Contacts version. Checking the source template alone does not exercise the copied one.
Associate the copy with the right process
Review where each version is used: a manually sent message, a workflow email notification or another automated action. Make sure the process selects the template for the record type it handles.
Do not replace a working source template just to introduce the copy. Keep its existing associations until the destination version has been checked. If the copy is part of a drip sequence, test it within that sequence as well as on its own.
Use HTML when you need a shared external design
An external HTML source can still be useful when several systems need the same branded email. Zoho supports inserting HTML when creating a template, but CRM merge fields and a compatible email layout still need attention.
Keep the source design under a clear owner and use the module's field picker for personalised values. After importing, repeat the preview and send tests. An HTML file that looks correct in a browser is not proof that the email or its CRM placeholders will work correctly.