Migrating email templates and sequences between HubSpot portals is one of the most delicate parts of any portal-to-portal migration. Unlike contacts or deals, emails carry design systems, personalization logic, and engagement history that can quietly break if the transfer is not handled carefully.
Whether you are consolidating portals after an acquisition, moving from a sandbox to production, or setting up a new business unit, this guide walks you through the complete process of transferring every type of HubSpot email asset between portals.
Understanding HubSpot’s Email Asset Types
Before you start exporting anything, it helps to understand that HubSpot organizes email content across several distinct asset types, and each one has different migration considerations.
Marketing Emails
Bulk sends, newsletters, and campaign emails built in the drag-and-drop or coded editor. Reference design modules, global styles, and CTA objects.
Sales Templates
Plain text templates with light formatting used by reps from CRM, Gmail, or Outlook. Rely heavily on personalization tokens tied to CRM properties.
Automated Emails
Built in the marketing editor but triggered exclusively by workflows. Require migrating both the email and the associated workflow.
Sequence Emails
Multi-step outreach cadences for sales. Depend on connected inboxes, user permissions, and CRM properties. No native export.
Marketing Emails
Marketing emails are the bulk sends, newsletters, and campaign emails you build in HubSpot’s drag-and-drop or coded email editor. They live under Marketing > Email and can be regular sends, automated emails triggered by workflows, or A/B test variants.
Marketing emails reference design modules, global styles, and CTA objects. When you transfer them, you need the underlying template architecture to already exist in the destination portal, or the emails will render incorrectly.
Sales Email Templates
Sales templates live under Conversations > Templates and are used by reps directly from the CRM, Gmail, or Outlook. They are simpler structurally, mostly plain text with light formatting, but they rely heavily on personalization tokens tied to CRM properties.
A token like {{contact.department_custom}} will silently fail if that property does not exist in the new portal. It will not throw an error — it will simply produce blank output in every email sent.
Automated Emails (Workflow Emails)
Automated emails are a hybrid. They are built in the marketing email editor but are triggered exclusively by workflows. Migrating these means migrating both the email and the associated workflow, and ensuring the trigger logic still makes sense in the new portal’s context. For a deeper look at workflow migration, see our workflow migration checklist.
Sequence Emails
Sequences are multi-step automated outreach cadences used by sales teams. Each sequence contains multiple email steps, task reminders, and timing delays. Sequences depend on a connected inbox (personal email), and the enrollment rules are tied to specific user permissions and CRM properties.
Preparing for Email Template Migration
Preparation determines whether your migration goes smoothly or turns into weeks of troubleshooting broken tokens and misaligned designs.
Audit Email Inventory
Catalog every email asset in the source portal by type, ownership, and usage status.
Map Personalization Tokens
Export and verify every token against the destination portal's property schema.
Document Design System
Catalog branded headers, footers, custom modules, color palettes, and image assets.
Audit Your Current Email Inventory
Start by cataloguing every email asset in your source portal. You need a clear count of:
- ✓Active marketing email templates and their associated campaigns
- ✓Sales templates and which teams or users own them
- ✓Sequences and their enrollment counts, open rates, and reply rates
- ✓Automated emails and the workflows that trigger them
- ✓Any A/B test variants you want to preserve
A thorough portal audit before migration will surface orphaned templates, broken tokens, and emails that are no longer in use. There is no reason to migrate dead weight.
Map Personalization Tokens
This is where most email migrations silently fail. Every personalization token in your emails needs a corresponding property in the destination portal.
| Token Type | Example | Migration Risk | Action Required |
|---|---|---|---|
| Default Contact | {{contact.firstname}} | Low | Works universally |
| Custom Contact | {{contact.department_custom}} | High | Verify property exists |
| Company Property | {{company.industry}} | Medium | Check internal name match |
| Deal Property | {{deal.custom_tier}} | High | Create property if missing |
| Owner Property | {{owner.firstname}} | Medium | Verify user exists |
Export a list of every token used across your templates. Create a mapping document that pairs every source token with its destination equivalent. If a property does not exist yet, create it in the destination portal before you begin the migration.
Document Your Design System
If your marketing emails use a consistent design system with branded headers, footers, colour palettes, and custom modules, you need to migrate those foundational elements first.
HubSpot’s email templates can reference:
- Global colour and font settings
- Custom email modules (coded or drag-and-drop)
- Saved sections and layouts
- Logo and image files hosted in the file manager
- CTA objects embedded in emails
Migrating an email without its design dependencies produces a broken shell. Start with the foundation and work your way up to individual emails.
Step-by-Step Migration Process for Marketing Emails
Here is the practical process for moving marketing emails between portals.
Export Email HTML
For each email, export the HTML source from the email editor. For coded emails, copy the HubL template code directly.
Migrate Supporting Assets
Upload images, recreate custom modules, configure brand settings, and recreate CTA objects in the destination portal.
Recreate or Import Templates
Rebuild drag-and-drop emails manually or import HubL-coded templates through the design manager.
Validate Personalization
Open each migrated email and verify every token resolves correctly with fully populated test contacts.
Step 1: Export Email HTML
For each marketing email you want to transfer, open it in HubSpot and export the HTML source. In the email editor, go to Settings and look for the option to view or export the raw HTML. For coded emails, you can directly copy the HubL template code.
For drag-and-drop emails, the exported HTML will contain references to modules and styles that are specific to the source portal. You will need to recreate the template structure in the destination portal and then rebuild or import the email content.
Step 2: Migrate Supporting Assets First
Before importing any email, ensure the destination portal has:
- ✓All referenced images uploaded to the file manager (and note the new URLs)
- ✓Custom modules recreated or imported
- ✓Global styles and brand settings configured
- ✓CTA objects recreated with matching names
This is one area where Jetstack’s implementation tools can save significant time, as asset dependency mapping and batch transfers are built into the platform.
Step 3: Recreate or Import Email Templates
For simple emails, it is often faster to recreate them manually in the destination portal using the same drag-and-drop editor. For complex coded emails or large volumes, you can use HubSpot’s design manager to import HubL-coded templates.
After import, check every module, every image reference, and every link. Broken image URLs are the most common issue because file manager paths differ between portals.
For large migrations with hundreds of images, use a find-and-replace approach to swap the old portal's file manager domain for the new one. This saves hours of manual image re-linking.
Step 4: Validate Personalization Tokens
Open each migrated email and verify that every personalization token resolves correctly. Send test emails to yourself using a contact record that has data in all the fields your tokens reference. Empty tokens are easy to spot, but tokens that pull the wrong data from a similarly named property can slip through if you are not testing carefully.
Migrating Sales Sequences
Sequences present unique challenges because they are tied to individual user inboxes and HubSpot’s sequences tool does not have a native export function.
Manual Sequence Recreation
Currently, HubSpot does not support bulk export or import of sequences. The migration process is manual:
Document Each Step
Record email body text, subject lines, delay timings, and task descriptions for every step in each sequence.
Note Enrollment Criteria
Document enrollment criteria and any automated enrollment triggers tied to the sequence.
Record Performance Baseline
Export open rate, reply rate, and meeting rate as benchmarks for post-migration comparison.
Recreate in Destination
Build each sequence in the destination portal with identical step structure and timing.
Connect Inboxes & Limits
Connect the appropriate user inboxes and configure sending limits in the destination portal.
Preserving Sequence Performance Data
Here is the hard truth: sequence engagement data does not transfer. Open rates, reply rates, click rates, and enrollment history are all tied to the source portal. If this data matters for your reporting, export it before decommissioning the source portal.
Sequence engagement data (open rates, reply rates, enrollment history) does not transfer. Export all performance reports before decommissioning the source portal. This data becomes your benchmark for validating the migrated sequences.
For organizations running dozens of sequences, we recommend using Jetstack’s migration tools to accelerate the documentation and recreation process. What takes a team days to do manually can be templated and executed in hours.
Handling Sequence Permissions and Sharing
In your source portal, some sequences may be shared across teams while others are private to individual reps. Document the sharing settings for each sequence and replicate them in the destination portal. Forgetting this step means sales reps either cannot access sequences they need, or they get access to sequences intended for other teams.
| Sequence Element | Transfers? | Migration Method |
|---|---|---|
| Email step content | Manual | Copy/paste text and rebuild |
| Task step configuration | Manual | Recreate task settings |
| Delay timings | Manual | Document and replicate |
| Enrollment history | No | Export as CSV report |
| Engagement metrics | No | Export before decommission |
| Connected inbox | No | Re-connect in destination |
| Sharing permissions | No | Document and replicate |
Template Design System Considerations
If your organization has invested in a polished email design system, the migration needs to preserve that consistency.
Brand Kit Migration
HubSpot’s brand kit settings, including logos, colours, and fonts, are portal-specific. Export your brand kit configuration and apply it in the destination portal before migrating any emails. This ensures that emails using default brand colours render correctly.
Custom Module Dependencies
Custom email modules are the building blocks of reusable email designs. Each module may reference HubL variables, custom CSS, and JavaScript. These modules need to be migrated through the design manager, and their internal references updated to match the destination portal’s file structure.
Testing Across Email Clients
After migration, do not assume that emails will render identically to how they looked in the source portal. Email client rendering depends on the exact HTML output, and even minor changes in template structure can cause layout shifts in Outlook, Gmail, or Apple Mail.
- ✓Mobile responsive behaviour
- ✓Dark mode rendering
- ✓Image scaling and alt text
- ✓Button and CTA alignment
- ✓Footer and unsubscribe link placement
Use a tool like Litmus or Email on Acid to test every migrated template across the major email clients.
Testing Deliverability After Migration
Migrating email assets is only half the battle. You also need to ensure that emails from the new portal actually reach inboxes.
Domain Authentication
The destination portal must have proper email sending domain authentication configured.
SPF Records
DNS records that authorize HubSpot's sending servers to send email on behalf of your domain.
DKIM Signing
Cryptographic email signing that verifies the email was sent from an authorized server and has not been tampered with.
DMARC Policy
A policy that tells receiving servers how to handle emails that fail SPF or DKIM checks. Aligns with your organization's security requirements.
If your sending domain changes during the migration, expect a temporary dip in deliverability as mailbox providers adjust to the new sending reputation.
Warm-Up Strategy
If the destination portal is brand new or has minimal sending history, you cannot immediately send at the same volume as your source portal. Mailbox providers track sender reputation at the IP and domain level, and sudden high-volume sends from a new source trigger spam filters.
Start With Engaged Contacts
Begin with your most engaged contacts — recent openers and clickers. These are most likely to interact positively, building reputation.
Small Initial Batches
Send to batches of 500-1,000 for the first week. Monitor bounce rates and spam complaints closely.
Gradual Volume Increase
Increase volume gradually over 2-4 weeks. Double your batch size each week if metrics remain healthy.
Monitor Inbox Placement
Track bounce rates, spam complaints, and inbox placement rates. Pause and investigate if any metric degrades.
Suppression List Transfer
Your source portal’s suppression list, including hard bounces, unsubscribes, and spam complaints, must be carried over to the destination portal. Failing to do this means you risk emailing people who have opted out, which violates CAN-SPAM and GDPR regulations and damages your sender reputation.
Failing to transfer your suppression list means emailing people who have opted out. This violates CAN-SPAM and GDPR, exposes your organization to legal liability, and damages sender reputation. Transfer suppression lists before sending any campaigns from the new portal.
Export the suppression list from the source portal and import it into the destination portal’s email health settings before sending any campaigns.
Common Pitfalls and How to Avoid Them
Even experienced HubSpot administrators run into issues during email migrations. Here are the most common pitfalls.
| Pitfall | Symptom | Prevention |
|---|---|---|
| Broken image links | Missing images in emails | Re-upload all images, update every URL reference |
| Missing CTA objects | Empty CTA blocks in emails | Migrate CTAs first, map old IDs to new |
| Token failures | Blank fields in sent emails | Test with fully populated contact records |
| Workflow connection gaps | Automated emails not triggering | Recreate workflows and re-link emails |
| Lost send history | No historical performance data | Export reports before decommissioning |
Broken Image Links
Image URLs in HubSpot emails point to the portal’s file manager. When you migrate an email, the images do not come with it automatically. You need to re-upload images and update every reference. For large migrations with hundreds of images, use a find-and-replace approach to swap the old portal’s file manager domain for the new one.
Missing CTA Objects
Embedded CTAs are separate objects in HubSpot. If you migrate an email without migrating the associated CTA, the email will show a broken or empty CTA block. Migrate all CTAs first and map old CTA IDs to new ones.
Personalization Token Failures
As discussed earlier, tokens that reference non-existent properties fail silently. They do not throw errors, they just produce blank output. Always test with fully populated contact records.
Workflow Connection Gaps
Automated emails that are triggered by workflows will not function until the corresponding workflow is recreated in the destination portal and the email is re-linked. Our workflow dependencies guide covers how to map and preserve these connections.
Losing Send History
You cannot transfer email send history between portals. Campaign performance data, A/B test results, and individual send records stay in the source portal. Export any reports you need for historical reference before decommissioning. For a complete picture of what data you lose in migration, read our guide on what you lose during HubSpot migration.
Email migration success depends on preparation depth, not execution speed. Invest the time in token mapping, design system documentation, and supporting asset migration before touching a single email template.
FAQ
Can I copy HubSpot email templates directly between portals?
HubSpot does not offer a native one-click copy for email templates between portals. You can export the HTML source and recreate templates in the destination portal, or use third-party tools to accelerate the process. Coded templates (HubL) can be transferred through the design manager, but drag-and-drop templates need to be manually rebuilt.
Will my email engagement data transfer to the new portal?
No. Email open rates, click rates, bounce data, and send history are tied to the source portal and do not transfer during migration. Export any reports you need for historical reference before deactivating the source portal.
How do I handle sequences that are connected to live deals?
Pause all active sequences before migration. Contacts currently enrolled in a sequence will stop receiving follow-ups once the source portal is deactivated. Recreate the sequences in the destination portal and re-enroll contacts at the appropriate step. Communicate the transition to your sales team so they can manually follow up during the gap.
Do I need to re-authenticate my email sending domain?
If both portals use the same sending domain, the existing SPF and DKIM records may already cover the new portal’s sending infrastructure. However, you should verify the authentication settings in the destination portal and update DNS records if needed. If you are changing sending domains, full re-authentication is required.
How long does email template migration typically take?
For a small portal with under 20 templates and a few sequences, expect 1-2 days of focused work. For enterprise portals with 100+ templates, complex design systems, and dozens of sequences, plan for 1-2 weeks. Using Jetstack’s migration services can reduce this timeline by 50-70%.
What is the best way to preserve email A/B test data?
A/B test results do not transfer between portals. Before migration, export the results of all significant A/B tests, including winning variants, performance metrics, and statistical significance data. Use these findings to inform your email strategy in the destination portal rather than trying to recreate the tests.