On this page
What HubSpot supports natively
| Feature | Dashboards and reports? |
|---|---|
| Clone a dashboard | Yes, within the same account; you choose whether reports are cloned too |
| Multi-account management | No. Copies automated emails, forms, segments, workflows |
| Partner Portability (beta) | No. Reports and dashboards aren’t on its list |
| Standard sandbox | No. HubSpot lists reporting and dashboards as not copied |
So between accounts, a dashboard is rebuilt.
How to copy a dashboard to another account by hand
- List the reports on the dashboard. For each one, note the data source, report type, filters, breakdowns, date range and chart type.
- Check the destination has what the reports use. Properties with the same internal names and options, the same pipelines and stages, matching owners and teams, and any custom objects.
- Rebuild each report in the destination’s report builder.
- Create the dashboard and add the reports in the same layout.
- Reapply dashboard filters, date ranges and access settings.
- Compare a few numbers against the source to confirm the definitions match, allowing for different underlying data.
Common mistakes
- Filters on stage IDs or owner names that don’t exist in the destination. The report saves but shows nothing.
- Custom report builder sources that join objects the destination doesn’t have.
- Rebuilding before the data model is in place. Copy properties and pipelines first; see how to copy a pipeline to another account.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies reports and dashboards between connected portals. Importing them needs the Jetstack Chrome extension, because HubSpot’s public API doesn’t expose them. On deploy, report filters and breakdowns are remapped to the destination’s properties and custom objects, and the dashboard is created first, then its reports added; each report must be in the same deployment or already exist in the destination. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See Ultimate assets.
Sources
- Manage your dashboards (HubSpot Knowledge Base)
- Production assets eligible to copy to a sandbox (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Ultimate assets (Jetstack AI documentation)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Copy & migrate between portals
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse