If you have access to multiple HubSpot accounts, you can copy blog, email, and page templates and theme folders from one account to another.
When copying assets that have external dependencies, such as linked stylesheets and global groups, it's recommended that you move all assets into one folder, then copy the folder. This will prevent errors and ensures that your assets are organized when they arrive in the destination account.
Keep in mind the following when copying templates and theme folders:
You must be logged in with the same email address in both accounts in order to copy a template or theme between the two accounts. You will not be able to copy purchased templates from one account to another.
Any assets outside of the folder being copied will not be copied across accounts. This includes any attached CSS/JS files, global groups, custom modules, etc.
Image files will not be moved over to the destination account; they will only be linked to in order to maintain the same file URL, which originates from the source account.
This function can also be used to transfer coded files and custom modules to another account.
Copying a template does not create pages, it only copies the templates, included assets and dependencies.
Theme folders in the @hubspot or @marketplace directories cannot be copied between accounts.
To copy a template or theme folder:
In your HubSpot account, navigate to Marketing > Files and Templates > Design Tools.
In the left sidebar, right-click the name of the template or theme folder, then select Copy to different account. You can also Click the Actions dropdown menu and select Copy to different account.
In the dialog box, use the Destination account dropdown menu to select the account you want to copy the template to, then click Copy assets.
The copy will begin processing, and you'll see a confirmation once that process has completed.
If you encounter an external dependency error, ensure that all external dependencies are included in the folder that you're copying. This includes linked files, global groups, and custom modules.