Creating Modules from Imports

A module is a named bundle of related assets designed for repeated deployment. Instead of selecting individual assets every time you deploy, you select a module and deploy the entire set as a unit. Modules are the primary mechanism for standardizing implementations across clients.

What Modules Are

Modules group a set of imported assets under a single name with a description. They act as deployment packages — self-contained sets of assets that work together to deliver a specific capability.

A module might contain:

3 workflows, 2 lists, 1 form, and 4 emails that together form a lead nurturing sequence
1 pipeline with 5 stage-entry workflows and 3 notification emails for a sales process
2 landing pages, 1 template, 1 form, and 1 thank-you email for a campaign landing page stack
10 property sets and 3 association labels for a standardized CRM configuration

The assets within a module include both your explicitly selected assets and any dependencies that were auto-imported alongside them. This ensures the module is self-contained — deploying it brings everything needed for the assets to function.

When to Create Modules

Create a module when:

You plan to deploy the same asset set to multiple portals. If you are onboarding several clients with the same workflow setup, a module lets you deploy consistently without re-selecting assets each time.
You want to share a standard package with your team. Modules appear in the Asset Library for all team members in your organization. A well-named module with a clear description communicates what it contains and when to use it.
You are building a repeatable service offering. If your agency delivers a standard “HubSpot Onboarding Package” or “Sales Enablement Setup,” packaging these as modules makes delivery consistent and efficient.

Skip creating a module when:

You are importing assets for a one-time deployment to a specific client
You want to cherry-pick individual assets for different deployments rather than deploying as a group
You are just exploring a source portal’s assets and have not decided what to deploy

You can always organize assets into modules later from the Asset Library, so there is no pressure to decide at import time.

Creating a Module During Import

The simplest way to create a module is during the import process itself. In Step 3 of the import wizard (Review and Import), you have two options:

Create Module — Imports assets and proceeds to module creation
Only Import Assets — Imports assets directly into the library without bundling

If you choose Create Module, the wizard presents a form after the import completes:

Module Title

Give the module a clear, descriptive name. This is the primary identifier in your Asset Library and what team members see when browsing for deployment packages.

Good naming conventions:

Include the purpose: “Lead Nurture Sequence” rather than “Import March 2024”
Include the version if applicable: “Sales Pipeline v2” or “Onboarding Kit Q1”
Be specific: “Enterprise Deal Pipeline with Automation” rather than “Pipeline Stuff”

Module Description

Add a brief description explaining:

What the module contains at a high level
What business objective it serves
Any prerequisites or assumptions (e.g., “Requires HubSpot Marketing Hub Professional or higher”)

The description appears in the Asset Library alongside the module title and helps team members determine whether a module fits their deployment needs.

How Modules Appear in the Asset Library

Once created, a module appears as a first-class item in the Asset Library. You can find it by:

Browsing the Modules section of the library
Searching by module name
Filtering the library view to show only modules

Each module entry displays:

Title — the name you gave it
Description — the description you provided
Asset count — total number of assets in the module, broken down by type
Created date — when the module was created
Source portal — which portal the assets were originally imported from

Clicking into a module shows the full list of contained assets grouped by type, with the same detail you see for individual assets in the library.

Using Modules in Deployments

When you start a new deployment from Implementation > Deploy, you can select a module as your deployment source instead of picking individual assets. Selecting a module automatically includes every asset it contains.

During deployment:

All assets in the module are included in the deployment
The dependency graph determines the correct creation order
Property mapping, pipeline mapping, and owner mapping apply to all assets in the module
You can still exclude individual assets from the module if needed before finalizing the deployment

See How Deployment Works for the complete deployment walkthrough.

Managing Modules

From the Asset Library, you can:

Rename a module or update its description
View contents to see every asset included
Delete a module — this removes the module grouping but does not delete the individual assets from your library

Individual assets within a module can also be deployed independently outside the module context. A module is an organizational grouping, not a lock.

Modules vs. Templates

Both modules and templates provide reusable asset collections, but they serve different purposes:

	Modules	Templates
Created from	Your own imports	Marketplace or shared
Scope	Organization-specific	Can be shared across organizations
Contains	Imported asset copies from a specific portal	Generalized asset definitions
Best for	Repeating your own proven setups	Starting from community best practices

You can use both in your workflow — deploy a marketplace template as a starting point, then create your own modules from the customized result.

See Modules and Templates for a deeper comparison.

Best Practices

One module per use case. Avoid creating mega-modules with everything in them. A focused module like “Webinar Registration Flow” is more useful than “All Marketing Assets.”
Document assumptions in the description. If the module assumes certain properties exist or a specific pipeline is in place, note it. This saves time during deployment.
Version your modules. When you improve an asset set, import the updated versions and create a new module (e.g., “Lead Nurture v2”) rather than overwriting the original. This preserves deployment history.
Review dependency assets. After creating a module, click into it and verify that the auto-imported dependencies make sense. If you see unexpected assets, check the dependency map to understand why they were included.

Next Steps

Browsing the Asset Library — Find and explore your modules and assets
Managing Assets — Organize, update, and maintain your library
How Deployment Works — Deploy your modules to destination portals