Skip to main content
Yes AI - AI Solutions Australia
For sales and marketing leads whose HubSpot portal has outgrown its original setup

HubSpot Portal Audit: Find Out What Your CRM Is Actually Doing

Many HubSpot portals in Australian businesses were set up once, by someone who has since moved on, and then added to by everyone else. A few years later there can be thousands of duplicate contacts, a few hundred custom properties nobody can explain, lifecycle stages sales ignores, workflows that undo each other, and dashboards the leadership team stopped opening. A HubSpot portal audit is a fixed-scope review of all of it, done before anyone builds anything new.

We go through the portal with read access, area by area: records and duplicates, the property list, lifecycle and lead status definitions, pipelines, every active workflow and sequence, forms and sources, connected apps and syncs, users and paid seats, and the reports people rely on. You get a findings register you keep and a cleanup and automation plan in the order it should be done. We build and maintain HubSpot integrations and automations for Australian businesses, and this audit is the review we would want done before touching anyone’s portal.

What the Audit Covers and Produces

9 areas
Reviewed in every portal
Records, properties, lifecycle, pipelines, workflows and sequences, forms, integrations, seats and reporting
1 findings register
Every issue logged with its evidence
A spreadsheet you keep, sorted by impact and effort, naming the screen or export where each finding was seen
Every active workflow
Listed with triggers, actions and conflicts
Including the ones that write to the same property as another workflow or a connected app
1 sequenced plan
Cleanup first, automation second
Each step with who does it, what it depends on and whether an export is needed before it runs

Why HubSpot Portals Drift Out of Shape

Four patterns explain much of what turns up in a portal that has been running for a few years. Nobody did anything wrong, and every one of them gets harder to fix the more automation is layered on top.

Many hands and no owner

Marketing adds properties for a campaign, sales adds fields for a new product line, an agency builds workflows for a launch, and every connected app creates its own properties when it is installed. Nobody is the named owner of the data model, so nothing is ever retired. The portal ends up recording every decision anyone made and none of the reasons for them. The first job of an audit is to give the portal an owner again, starting with a written list of what exists, what uses it and who asked for it.

Definitions nobody wrote down

Lifecycle stage and lead status only work if sales and marketing agree, in writing, what moves a contact from one value to the next. In most portals those definitions live in someone’s head or in a slide from the original rollout, and the workflows that set them were written against rules that have since changed. The result is a funnel report leadership does not believe and a sales team that keeps its own spreadsheet of who is really in play.

Automation stacked on automation

Each workflow made sense when it was built. Together they set the same property from different triggers, re-enrol contacts nobody meant to re-enrol, send two emails to the same person on the same morning, and overwrite a value a sync wrote a minute earlier. HubSpot will run all of it without complaint. Finding the conflicts means reading every active workflow alongside every connected app, which is slow work and the part most portals never get.

Connected apps nobody watches

Accounting, ecommerce, booking, webinar, enrichment and form tools all write into HubSpot. Each one was connected by whoever had admin access at the time, usually with default field mappings and sync rules. When a sync creates duplicates or resets a lifecycle stage, it looks like a HubSpot fault. In most cases the cause is a connected app that nobody has opened since the day it was installed, still writing to fields that now mean something different.

What We Review in Your HubSpot Portal

Nine areas, grouped into six blocks. Every finding goes into the register with the screen, report or export where it was seen, so your own team can check it.

Data quality findings

Records and duplicates

Contacts, companies and deals are counted and profiled. How many contacts have no email, no owner or no associated company; how many companies share a website domain; how many deals sit in a closed stage with no close date, or in an open stage nobody has touched for months. We review the duplicate suggestions HubSpot produces where your subscription includes that tool, check a sample of matches by hand, and trace where duplicates come from: an import, a form, a connected app or manual entry. Merging duplicates without fixing the source just means merging them again next quarter, so the source is the finding that matters.

Property register

Property inventory

Every custom property on contacts, companies, deals and tickets goes into a register with its field type, property group, how many records hold a value, and which forms, workflows, segments (lists), reports and connected apps reference it. We look for properties with no values, properties that repeat another field under a different name, dropdowns with dozens of near-identical options, and free-text fields used where a dropdown would keep the data consistent. Each property is tagged keep, merge, archive or investigate, with the dependencies listed, including outside tools that read the field and do not appear in HubSpot’s own usage list.

Definitions and stage map

Lifecycle, lead status and pipelines

The lifecycle stage and lead status values in use, how many records sit in each, and every workflow, form, import and connected app that sets or changes them. Deal pipelines and stages, the win probability on each stage, the properties required when a deal changes stage, and how many deals skip stages or move backwards. We write down the definitions as the portal actually applies them today, which is often different from what anyone believes, then put the gaps in front of sales and marketing so new definitions can be agreed.

Automation inventory

Workflows and sequences

Every active workflow is listed with its object type, enrolment triggers, re-enrolment settings, actions, the properties it writes and the emails it sends. We map which workflows write the same property, which enrol the same contacts from overlapping triggers, and which still point at a segment, form, owner or property that no longer means what it did. Sequences are reviewed for who is enrolled, what they send, and whether they overlap with marketing emails going to the same person in the same week. Workflows left on after a campaign ended are a common finding.

Inbound data map

Forms, sources and connected apps

Every form, where it is embedded, which properties it writes and which workflows it triggers. How original source and any custom lead source field are recorded, and whether they agree with each other. Every connected app and private app in the portal settings, what it reads, what it writes, which direction it syncs, and which system wins when both change the same field. Syncs with the accounting or operations system get the closest look, because a mapping error there can overwrite good data in both systems at once.

Seat and report review

Users, seats and reporting

Every user, the paid seat type assigned to them where there is one, how recently they have been active, their team, and whether they can change portal settings. That shows paid seats nobody uses and who holds admin rights if a staff member or agency leaves. Dashboards and reports are reviewed for who owns them, which properties and definitions they depend on, and whether the figures agree with the source system. A report built on a broken lifecycle definition is flagged against that definition rather than patched on its own.

Common Findings and What the Plan Does With Them

TaskTraditionalIn the audit planNotes
Duplicate contacts from a form and a connected app both creating recordsMerged by hand every few monthsSource fixed first, then one merge run with agreed matching rulesMerging before fixing the source restarts the count. The plan names the source and the change that stops it.
Several hundred custom propertiesLeft alone because nobody knows what will breakEach property traced to its forms, workflows, reports and syncs, then archived or merged in batchesHubSpot will not archive a property that a workflow or form still uses, but outside tools that read the field through an integration do not show in that check, so batches start with the safest fields.
Lifecycle stage set by four different workflowsA funnel report nobody trustsOne written definition per stage, one set of rules that applies itSales and marketing leaders agree the definitions before anything is rebuilt.
Two workflows emailing the same contact on the same dayComplaints and unsubscribesOverlap mapped, enrolment criteria and suppression lists correctedOften a campaign workflow left on after the campaign ended, or a sequence running alongside a nurture.
Deals sitting in open stages for monthsPipeline value overstated in every forecastStale-deal rules, required fields on stage change and an owner review listThe forecast is only as good as the oldest open deal in it.
Accounting sync overwriting company detailsFinance and sales both editing the same recordField ownership written down: which system wins for each fieldApplies to any two-way sync. The Xero systems audit looks at the same sync from the finance end.
Paid seats held by people who left or rarely log inRenewed every term without reviewSeat list with activity and role, reductions flagged before the renewal dateSeat changes depend on your contract terms. We flag them, you decide.
Dashboards leadership stopped openingFigures exported to a spreadsheet each monthEach report traced to its properties and rebuilt once definitions are agreedFixing the data and definitions first is what makes the rebuilt reports believable.

What to Know Before a HubSpot Cleanup

No cyber security assessment is included

This audit does not include a cyber security assessment. If you need one, we will introduce you to a specialist security firm that carries its own insurance for that work. Where we look at users, admin rights and connected apps, it is an ownership and access inventory: who can change portal settings, who holds the keys if a staff member or agency leaves, and which apps hold a copy of your customer data. We record what is there. We do not rate or score security.

Treat every merge as permanent

Merging records in HubSpot combines their properties, activity and associations, and HubSpot states that merged records cannot be unmerged. Before any bulk merge, property archive or record deletion, export the affected records with every property, write down the matching rules used, and run the change on a small batch first. The plan marks each step that needs an export before it runs, and who checks the result.

Archived properties can break things you cannot see

HubSpot shows which assets use a property and will not archive it while some of them, such as workflows, forms and segments, still use it. Archived properties are deleted permanently after 90 days. Outside tools and integrations that read a field by name do not appear in HubSpot’s usage list, so archiving can still break a sync without a clear error. The property register lists every dependency HubSpot shows plus the integrations we can trace. Archive batches start with properties that hold no values, and sync logs are checked after each batch before the next one runs.

Definitions are a business decision

We can document how the portal currently applies lifecycle stages and lead statuses, and propose definitions that fit how your team sells. Agreeing them is a decision for the sales and marketing leaders together, and it needs to be written down and owned by someone. Without that agreement a rebuilt lifecycle model drifts back to the old state within months. The plan includes a short working session for exactly this.

Seat and tier changes follow your contract

HubSpot subscriptions have terms, renewal dates and commitments set out in your agreement with HubSpot or the partner you bought through. We show which paid seats are unused and which features you pay for and do not use. Whether to reduce seats or change tier is your decision, made against your actual contract dates. We do not quote HubSpot prices and we do not resell HubSpot subscriptions.

Customer data stays in your portal

We work through a user account you create for the audit and remove at the end, and the access granted is recorded in the register. Exports used for analysis are limited to the fields we need, handled in line with your privacy obligations, and deleted when the audit closes. Personal information about your customers is not copied into our own systems or used for anything outside the audit.

How Yes AI Runs a HubSpot Portal Audit

Read first, change nothing

The audit is read-only. You create a user for us, we review with the access agreed, and any setting we had to change to get in is recorded. Nothing in the portal is merged, archived or switched off during the audit. Changes come later, in the order the plan sets, with your approval at each step.

A register your team owns

Findings go into a register you keep: the area, the evidence, the impact, the suggested fix, the effort, and whether an export is needed first. It is written so your in-house admin, an agency or our team can work from it without needing us in the room.

Audit first, build second

Our HubSpot integration and automation service is the build: syncs with accounting and operations, continuous deduplication, lifecycle automation. Our AI for HubSpot page covers AI features on top of a working portal. The audit comes before both, so new automation runs on agreed definitions and clean data. If the plan shows you only need a cleanup, that is what we recommend.

Who should not buy this

If your portal is under a year old with a handful of users, a checklist and an afternoon will do more than an audit. If your main need is a cyber security assessment or a compliance certificate, this is the wrong service and we will point you to a specialist. If you have already decided to leave HubSpot, you need a migration plan rather than a cleanup plan.

How the HubSpot Audit Runs

Five steps. Elapsed time depends mostly on portal size and how quickly access and the findings session can be arranged. The fee is fixed and agreed after a short scoping call.

Scoping call

We ask which hubs and tiers you run, roughly how many records, users and active workflows you have, which systems sync with HubSpot, and what prompted the audit. That sets the scope, the fixed fee and the timetable.

Access and exports

You create a user for us with the permissions agreed on the call. We take exports of properties, workflows, forms, users and record samples, and note any setting we had to change to get access.

Review the nine areas

Records, properties, lifecycle and pipelines, workflows and sequences, forms, connected apps, seats and reporting. We also speak to two or three people who use the portal every day, because the reason behind a workaround never shows up in the settings.

Findings session

We take sales, marketing and whoever owns the portal through the register, and run the working session where lifecycle stage and lead status definitions are agreed and written down.

Register and plan handed over

You receive the findings register and the sequenced cleanup and automation plan. The cleanup, sync fixes and new automation can follow with us or anyone else, decided after the audit.

FAQ

What is a HubSpot portal audit?

It is a fixed-scope, read-only review of how your HubSpot portal is set up and used. We look at data quality and duplicates across contacts, companies and deals, the custom property list, lifecycle stage and lead status definitions, pipelines and deal stages, workflows and sequences, forms and lead sources, connected apps and syncs, users and paid seats, and the reports people rely on. The output is a findings register you keep and a cleanup and automation plan in the order the work should be done. It is the step before rebuilding anything, so new work is designed around what is really in the portal.

Are you a HubSpot partner?

No. Yes AI is not a HubSpot partner and does not resell HubSpot subscriptions. We build and maintain HubSpot integrations and automations for Australian businesses, and the audit draws on that hands-on work: knowing where syncs overwrite data, which workflow settings cause re-enrolment surprises, and which reports depend on which properties. If you already work with a HubSpot partner for licensing or onboarding, we are happy to share the register with them and work alongside them.

How is this different from your HubSpot integration and automation service?

The integration and automation service builds things: two-way syncs with accounting and operations systems, deduplication that runs on a schedule, lifecycle and routing automation. The audit finds out what is already there and what should be fixed first. Plenty of businesses come to us asking for a new integration or workflow when the portal it would run in has conflicting definitions and a duplicate problem. Building on that makes the problem bigger. The AI for HubSpot work has the same dependency, because AI scoring and summaries are only as good as the records they read.

Will the audit change anything in our portal?

No. We review with the access agreed on the scoping call and record any setting we had to change to get in, such as adding a sign-in method for the audit user. No records are merged, no properties archived and no workflows switched off during the audit. Every change in the plan is a separate step that your team approves, with the export or backup it needs listed beside it. If you want us to carry out the cleanup afterwards, that is agreed as its own piece of work once you have read the plan.

Does the audit include a security review of HubSpot?

No. This audit does not include a cyber security assessment. If you need one, we will introduce you to a specialist security firm that carries its own insurance for that work. We do list who holds admin rights in the portal, which users can change settings, and which connected apps read or write your customer data, because a business needs to know who holds the keys before a staff member or agency leaves. That list is an ownership and access inventory. It is not a security rating and should not be used as one.

Who should not buy a HubSpot portal audit?

A business with a new portal and a few users does not need one: a short checklist and an afternoon with whoever set it up will do more. A business whose real concern is cyber security or a compliance certificate needs a specialist security firm instead. A business that has already decided to move off HubSpot needs a migration plan, although the property and workflow inventory from an audit can feed into one. And if you want someone to run campaigns inside HubSpot, you want a marketing agency rather than a systems audit.

What does it cost and how long does it take?

The audit is a fixed fee agreed after a short scoping call, based on which hubs you run, record volume, the number of active workflows and how many systems sync with HubSpot. The initial consultation is free for businesses with 20 or more full-time staff, otherwise $200 including GST. The review itself is usually the shorter part of the timetable. Arranging access, speaking to the people who use the portal and booking the findings session with sales and marketing leaders together tend to set the pace.

Know What Is in Your Portal Before You Build On It

Book a short scoping call. We agree the scope and a fixed fee, review the portal read-only, and hand over a findings register and a sequenced cleanup and automation plan that you keep.

All discussions held in confidence. Australian-based consultants.

Interactive controls are loading. Phone and email links are available.