Skip to content
Book a build

Should you fix or rebuild a messy HubSpot portal?

Fix a messy HubSpot portal in place when the data model is sound and the problems are in workflows, properties and reports. Rebuild parts of it when the objects, pipelines or lifecycle logic don't match how the business works. Audit first so you decide from evidence, and rebuild one area at a time rather than starting a new portal.

On this page

What HubSpot supports natively

HubSpot can help you find mess, but not decide whether to fix or rebuild.

Native toolHelps with
Workflows Health tabWhich workflows need review or are unused
Data quality toolsDuplicates, formatting issues, unused and empty properties
Audit logs and property historyHow things got this way

Fix or rebuild: a decision table

FindingFix in placeRebuild that part
Many unused properties and listsYes
Workflows conflicting or erroringYes, in priority orderIf most of a process’s workflows conflict
Lifecycle stages used inconsistentlyIf the definitions are rightIf the definitions don’t match your funnel
Deal pipelines don’t match the sales processYes
Wrong objects for the business (for example, everything on contacts)Yes, carefully
Reports wrong because of dataFix the data first
No naming, no ownersYes

Most portals need both: a cleanup of what’s sound and a rebuild of one or two areas.

How to decide

  1. Audit first. A full portal audit shows which areas are sound.
  2. Rank findings. See how to prioritize audit findings.
  3. Pick the areas to rebuild. Usually the process with the most conflicting workflows or the pipeline that doesn’t match how you sell.
  4. Write a brief for each rebuild: the properties, pipeline stages and workflow logic it should have.
  5. Build alongside, test, switch over, then turn off and later remove the old version.

Where Jetstack AI fits

Jetstack AI keeps the two steps separate. Portal Audit shows which areas need work. For the parts you rebuild, we recommend Projects, currently in limited release: write the brief from step 4 in a Project, or upload it as a document, and Jetty, the Projects assistant, turns it into a plan you review. Approving the plan generates the assets; you review them and approve deployment separately, and the receipt is checked by reading each asset back from HubSpot. Projects builds the new version alongside the old one, in dependency order and with workflows created switched off, but it can change only assets it built, so turning off and removing the old version stays a step you do in HubSpot. If you’re rebuilding with a setup you already run in another portal, Portal reuse can deploy it, and 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. See what Projects can build.

Sources

Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Portal audits

Turn the brief into approved HubSpot assets.

Projects plans the build against the client portal, generates the assets and deploys them only after you approve.

Explore Projects

Portal audits

Related questions.

Should you fix or rebuild a messy HubSpot portal?

Fix a messy HubSpot portal in place when the data model is sound and the problems are in workflows, properties and reports. Rebuild parts of it when the objects, pipelines or lifecycle logic don't match how the business works. Audit first so you decide from evidence, and rebuild one area at a time rather than starting a new portal.

Should we start a brand new HubSpot portal?

Rarely. A new portal means moving records, history and integrations, which is a migration project of its own. Rebuilding parts inside the existing portal keeps the history.

Can we rebuild while the team keeps working?

Yes, if you build the new version alongside the old one, test it, then switch over and turn the old version off. Don't edit live workflows in place for a large rebuild.