How to Copy Templates and Themes Between HubSpot Accounts

Copying design assets in HubSpot can be confusing if you manage multiple portals or collaborate with external developers. This guide explains every supported method to move templates, themes, and coded files between HubSpot accounts while keeping your layouts intact and code organized.

All methods below are based on the official documentation so you can safely duplicate your work without breaking existing pages.

Understanding How HubSpot Manages Design Assets

Before you start, it helps to understand how design content is structured in HubSpot design manager.

• Themes: Collections of templates, modules, and assets designed to work together.
• Templates: Individual layouts for pages, blog posts, or emails.
• Coded files: HTML, HubL, JS, and CSS files stored in the design manager file system.
• Theme settings: Global options like colors, typography, and spacing.

Not every asset can be copied using a single method. Some techniques work only for coded templates, while others are better for whole themes. Choosing the right path depends on what you need to move inside HubSpot.

Available Methods to Copy Designs in HubSpot

There are three primary ways to move templates or themes between accounts:

1. Exporting and importing coded files between design managers.
2. Syncing content through a GitHub repository.
3. Using a reverse proxy to serve content across domains.

In addition, you can clone assets within the same HubSpot account to create variations of existing designs.

Method 1: Export and Import Coded Files in HubSpot

This method is best for developers who need to copy specific templates, modules, or related files from one HubSpot account to another.

Step 1: Prepare your source design in HubSpot

In the original account where the templates or themes live:

1. Open Marketing > Files and Templates > Design Tools.
2. Locate the folder, theme, or specific file you want to move.
3. Ensure all dependencies are stored in an organized folder structure so nothing is missed during export.

Step 2: Export design manager files from HubSpot

To export the files:

1. In the design manager sidebar, right-click the folder or theme.
2. Select Export (or a similar option provided for export operations).
3. HubSpot generates a downloadable package containing the selected files.
4. Save the ZIP file locally to your computer.

The export typically includes templates, coded files, and related assets from the selected directory.

Step 3: Import files into the target HubSpot account

Next, sign in to the destination portal:

1. Open Marketing > Files and Templates > Design Tools in the target account.
2. Click the Actions menu or similar option and choose Import.
3. Upload the ZIP file exported from the original HubSpot portal.
4. Confirm the import and wait for the process to finish.

When the import completes, your templates and coded files appear in the design manager, usually inside a folder with the same name as the source directory.

Step 4: Review imported templates

After the import:

• Open each template to confirm that modules, partials, and referenced files load correctly.
• Check CSS and JS references to ensure paths still point to the right files in the new HubSpot portal.
• Update any hard-coded domain references or tracking codes that are specific to the original account.

Method 2: Use GitHub to Sync HubSpot Code

For teams with developers working in external editors, connecting HubSpot design manager to GitHub can be an efficient way to copy and maintain code across accounts.

When to use GitHub integration with HubSpot

GitHub is ideal when:

• You maintain themes as code repositories.
• Multiple environments (e.g., staging and production HubSpot accounts) must share the same theme.
• You want version control, pull requests, and code review for templates and modules.

Basic workflow with GitHub and HubSpot

1. Connect the original HubSpot portal to a GitHub repository using the design manager Git integration.
2. Push all relevant coded files and templates from design manager to the repository.
3. Connect the second HubSpot account to the same repository.
4. Pull the repository content into the target portal’s design manager.

This approach keeps your theme code synchronized and lets you manage updates through Git workflows rather than manual exports and imports.

Method 3: Reverse Proxy for Cross-Domain Content

A reverse proxy is different from typical copying. Instead of duplicating templates inside another HubSpot account, it serves content from a centralized source domain to a different front-end domain.

How reverse proxy works with HubSpot

With a reverse proxy configuration:

• Your public domain (for example, a country-specific site) sends traffic through a proxy server.
• The proxy forwards requests to a main HubSpot-hosted domain.
• Content is rendered from the main portal but appears under the secondary domain.

This method is helpful when you want to reuse designs without physically copying them between HubSpot accounts, or when you centralize all design assets in a single portal.

When to choose a reverse proxy instead of copying

• You need multiple brand or regional domains to show identical layouts.
• You want one master HubSpot portal to control all design changes.
• You prefer infrastructure changes over managing several sets of templates.

Reverse proxy setups are more technical and often require coordination with developers or hosting providers.

Cloning Templates Within the Same HubSpot Account

If you only need a copy of a design inside one portal, you can clone rather than export. Cloning is the fastest way to create variations without affecting existing pages.

How to clone a template in HubSpot

1. Open Design Tools in your account.
2. Right-click the template you want to duplicate.
3. Select Clone or a similar cloning option.
4. Give your new template a unique name and choose a folder.

The cloned template will keep all layout and module structure so you can customize it for different campaigns or brands.

Best Practices for Managing Themes in HubSpot

To keep your design system stable and portable between accounts, use the following recommendations:

• Group related files: Store theme assets in a dedicated folder to simplify exports.
• Use theme fields: Move brand colors, fonts, and spacing into theme settings so they are easy to adjust after importing into another HubSpot portal.
• Avoid hard-coded URLs: Reference relative paths whenever possible to reduce cleanup work after copying.
• Document dependencies: Maintain a simple README file inside your theme folder describing which modules, partials, and assets belong together.
• Test after import: Always create a test page using the imported template to confirm everything behaves as expected.

Resources and Further Help for HubSpot Design

For official technical details on file export and related options, review the original documentation on copying templates and themes between portals on the HubSpot knowledge base.

If you need professional support planning multi-portal architectures, theme migrations, or reverse proxy configurations, you can also consult specialized partners such as Consultevo for deeper strategy and implementation guidance.

By choosing the right combination of exports, GitHub sync, reverse proxy, and in-portal cloning, you can efficiently manage templates and themes across all your HubSpot environments without losing consistency or control.

Need Help With Hubspot?

If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.

Scale Hubspot

“`