How to Do a HubSpot Workflow Audit Before Handing Off a Client Portal
You have finished the engagement. The client is ready to take over. And then someone asks: "Can you document all the workflows before you go?"
The portal has 140 workflows. Some are active. Some are inactive. A third were built by someone who left the company two years ago. There is no documentation. There is no naming convention. And you have a week.
This is what to do.
Why a pre-handoff audit is different from a regular audit
Most workflow audits are diagnostic — you are trying to understand a portal you have just inherited. A pre-handoff audit is the opposite. You are trying to make a portal understandable to someone who is about to inherit it.
That shifts the goal. The question is not "what is broken?" The question is: "What does this person need to know to operate this system safely after I am gone?"
The answer is always three things:
A complete picture of what exists
A clear picture of how it connects
A prioritized list of what to watch out for
Everything else is detail. Build toward those three things.
Step one: build the full inventory
Before you open a single workflow, pull a full inventory across every object type.
HubSpot does not give you a native cross-object summary view. You will need to work through Contacts, Companies, Deals, Tickets, and any custom objects separately. For each, note:
Workflow name
Status (active or inactive)
Last modified date
Enrollment count
Object type
This gives you the skeleton of the system before you start reading any of the logic.
A few things you will almost certainly find:
Inactive workflows nobody remembers. These are not automatically safe to delete. An inactive workflow might still be referenced by an active one. Before flagging anything for removal, check whether it appears anywhere as a downstream enrollment target.
Active workflows with zero enrolled records. This usually means a broken enrollment condition — the trigger criteria is set up correctly in theory but is not matching any records in practice. This is worth flagging clearly in the handoff documentation.
Workflows that have not been modified in over six months. Not automatically a problem, but worth noting. If the business logic or team structure has changed since the workflow was last touched, the logic inside it may no longer reflect current reality.
Step two: map the dependencies
The inventory tells you what exists. The dependency map tells you how it all connects. This is the step most agencies skip — and the one that causes the most problems after handoff.
There are three types of workflow connections in HubSpot:
Direct enrollments. One workflow explicitly enrolls records into another via an "Enroll in workflow" action. These are the most visible connection type and the easiest to find — if you open every workflow and look for enrollment actions.
List-based connections. One workflow adds or removes contacts from a HubSpot list. Another workflow uses that list as an enrollment trigger. The connection exists in the data layer, not inside either workflow. This means you can read both workflows individually and never know they are linked. Finding these requires cross-referencing every list used as an enrollment trigger against every workflow that modifies list membership. In a large portal, this is the most time-consuming part of the audit.
Property-based connections. One workflow sets a property to a specific value. Another workflow triggers when that property reaches that value. These are the hardest connections to find because there is nothing inside either workflow that visually points to the other. You have to know what to look for: take the property being set in Workflow A, then search every other workflow for that same property in their enrollment triggers.
When you have completed the dependency map, you can answer the question the incoming team will actually ask: "If I turn off this workflow, what breaks?"
Without the map, that question takes hours to answer. With it, it takes seconds.
Step three: flag the structural issues
A handoff document that just describes what exists is useful. One that also tells the incoming team what to watch out for is the difference between a good agency and a great one.
While you are mapping, flag the following:
Empty workflows. Active workflows with no actions configured. If records are enrolling, nothing is happening to them. Either the workflow was never finished or it was intentionally left empty as a placeholder. Either way, the incoming team needs to know.
Orphaned workflows. Active workflows with no upstream or downstream connections and no obvious standalone purpose. These are candidates for deactivation, but flag them rather than deleting them — the incoming team may know something you do not.
Broken enrollment chains. A workflow that tries to enroll records into another workflow that is inactive. Records hitting the enrollment action go nowhere. This is one of the most common sources of silent failures in mature HubSpot portals.
Conflicting property writes. Two or more active workflows that update the same property, potentially with different values. Depending on timing, records may end up in an inconsistent state. This is a data quality issue masquerading as an automation issue, and it is very easy to miss without a systematic review of which workflows touch which properties.
Stale logic. Active workflows whose triggers or actions reference things that no longer exist — deleted lists, renamed properties, deprecated email templates. These workflows may be failing silently or behaving unpredictably.
Each of these should appear in the handoff document with a severity level and a recommended action. Not as things you fixed, but as things the incoming team needs to be aware of.
Step four: document what the incoming team actually needs
The instinct is to document everything. The better instinct is to document what someone who did not build this system needs to know to run it safely.
That means:
One sentence per workflow describing its purpose. Not its trigger logic — its business purpose. "Sends the onboarding sequence to new customers after deal close" is more useful than "Enrolled when Lifecycle Stage = Customer and Deal Stage = Closed Won."
A clear owner for every active workflow. If nobody currently owns it, say so. The incoming team needs to know which workflows are actively maintained and which are running on autopilot.
The dependency map in a visual format. A written list of connections works, but a visual map is faster to use in practice. When the incoming team is about to make a change, they need to be able to look at the map and immediately see what else is connected.
A prioritized issues list. Not everything you flagged is equally urgent. Give the incoming team a clear view of what needs attention in the first 30 days versus what can wait.
How long this takes
Manually, for a portal with 50 to 100 workflows, a thorough pre-handoff audit takes one to two full days. The inventory is an hour or two. The dependency mapping is the bulk of the time. The documentation write-up is another few hours.
For a portal with 150 or more workflows, add time accordingly. And if you are handing off multiple clients in the same month — which is a normal part of agency life — multiply that across every engagement.
The dependency mapping step is where the time goes. It is the part that does not scale well manually, because it requires cross-referencing lists and properties across every workflow in the portal. You cannot read your way to a complete dependency map. You have to build it systematically, and that takes time.
Howly automates the inventory and dependency mapping. Connect a client portal and Howly loads every workflow across every object type onto a single canvas, maps all three connection types automatically, and flags structural issues in the same view. The dependency map is ready in minutes rather than hours. Most agencies use the canvas export as the visual deliverable in the handoff document and the AI issues summary as the basis for the prioritized action list.
For agencies doing this across multiple client portals, Howly supports unlimited portal connections under a single account — so the same workflow applies to every client without rebuilding anything.
The handoff document structure
A complete pre-handoff audit document has four sections:
1. Portal overview. Total workflow count, active vs. inactive split, object type breakdown. One page. Gives the incoming team a quick orientation before they go deeper.
2. Dependency map. A visual representation of the workflow system showing all active workflows and the connections between them. This is the centerpiece of the document — the thing the incoming team will refer to before making any significant change.
3. Issues list. A prioritized list of structural problems, with severity levels and recommended actions. High priority issues (broken enrollment chains, conflicting property writes) at the top. Lower priority items (stale workflows, possible duplicates) below.
4. Workflow reference. A structured list of every workflow with its purpose, owner, object type, status, and key dependencies. This is the reference document the incoming team uses day-to-day.
Delivered together, these four sections give the incoming team everything they need to operate the portal safely — and a clear starting point for the cleanup work that almost always follows a handoff.
Frequently asked questions
What does a HubSpot workflow audit include before a client handoff?
A complete pre-handoff audit includes a full workflow inventory across all object types, a visual dependency map showing how workflows connect to each other, a structural issues list with severity levels and recommended actions, and a workflow reference document with ownership and purpose for each automation. The goal is to give the incoming team everything they need to operate the portal safely without having to reverse-engineer it themselves.
How do I find workflow dependencies in HubSpot before a handoff?
HubSpot does not surface cross-workflow dependencies natively. You need to check for three connection types manually: direct enrollments (one workflow enrolling records into another), list-based connections (one workflow adding to a list that another uses as an enrollment trigger), and property-based connections (one workflow setting a property value that triggers another). Finding these manually requires cross-referencing every workflow in the portal. A tool like Howly maps all three connection types automatically when you connect the portal.
How long does a pre-handoff HubSpot audit take?
For a portal with 50 to 100 workflows, expect one to two full days of work to complete the inventory, dependency map, and documentation. Larger portals take longer. The dependency mapping step is the most time-intensive part. Agencies using Howly generate the inventory and dependency map automatically, which reduces the audit time to a few hours for most portals regardless of size.
What is the most important thing to document before handing off a HubSpot portal?
The dependency map. The incoming team can learn what individual workflows do by reading them. What they cannot figure out on their own — without significant time investment — is how those workflows connect to each other. Without a dependency map, every change they make carries unknown risk. With one, they can trace the impact of any change before they make it.
Should I fix workflow issues before handing off a client portal?
It depends on what you found and what the engagement scope covers. Structural issues that could cause immediate problems — broken enrollment chains, conflicting property writes — are worth addressing before handoff if you have the time and budget. Lower-priority issues like stale workflows and possible duplicates can be documented and handed over for the incoming team to address. Either way, document everything you find. Do not fix things silently without noting what you changed.
How do I present a workflow audit to a client at handoff?
The most effective format is a visual map as the centerpiece — showing the full workflow system and all connections — with a written issues list alongside it. A visual map is faster to understand in a presentation or review call than a spreadsheet. Howly exports the workflow canvas as a PDF or PNG for client-ready deliverables, and to Lucidchart for teams that want to annotate or edit the diagram further.
Summary
A pre-handoff HubSpot workflow audit is not just documentation. It is the difference between leaving a client with a system they can operate safely and leaving them with one they will break within the first month.
The three things that actually matter: a full inventory, a dependency map that shows how everything connects, and a clear issues list that tells the incoming team what to watch out for.
The dependency mapping step is the one that takes the most time and delivers the most value. It is also the step that does not scale well manually — which is why agencies doing multiple handoffs a month need tooling that does it automatically.
If you are preparing a client handoff, connect the portal to Howly and see the full dependency map before your next review call. Most agencies have the map ready before the end of the same session.
Howly is a read-only HubSpot workflow mapping and audit tool. It maps workflow connections, flags structural issues, and shows the impact of property changes before you make them. Used by RevOps teams and HubSpot agencies managing complex portals at scale.
Related reading:
