Short answer: in your first 30 days with an inherited HubSpot portal, change nothing that affects reporting. Get access, export the evidence, write down how records move through lifecycle stages, trace the reports leadership reads, and inspect the CRM sync. By day 30 you should have a written map, a ranked list of problems with evidence, and a decision on what to fix first.
For new marketing leaders, RevOps hires and founders handing HubSpot to a first marketing hire. Last reviewed September 2026.
Why the first 30 days matter
An inherited portal comes with someone else’s decisions and no record of why they were made. The temptation is to start cleaning. Resist it for a month. Every change you make before you have a baseline erases the evidence of what was wrong, and makes the next quarter’s numbers impossible to compare with the last. The first month is for reading.
Week 1: access, inventory, and a frozen baseline
Get the right access. Ask for a Super Admin seat or at least read access to settings, workflows, reports and integrations. Confirm who else holds Super Admin, and whether the person who built the portal still has a login.
Export before you touch. Take these exports on day one and date them:
| Export | What it proves |
|---|---|
| Contacts, companies and deals, all properties | The baseline every later comparison uses |
| Property list per object, with fill rates | How much of the data model is actually used |
| Workflows list with triggers and last activity | What automation is really running |
| Users with permission sets and last login | Who can change what |
| Connected apps and integrations | Which systems write into HubSpot |
| Segments (formerly lists) used in workflows and reports | Which audiences matter operationally |
Check the audit trail window. HubSpot’s centralised audit log keeps 30 days of user activity on all tiers, and some categories (workflow, pipeline and property changes, among others) are Enterprise only. If something changed before you arrived, you may not be able to reconstruct it, so write down what you cannot see as well as what you can.
Week 2: how records move
This is the week to understand the lifecycle, because almost every reporting argument traces back to it.
- List the lifecycle stages and write a one-line definition for each. Ask sales and marketing separately. If the definitions differ, that is your first finding.
- Find every rule that sets lifecycle stage: workflows, form settings, imports, the CRM sync, and HubSpot’s own automatic settings (on record creation, deal creation, deal won and lead association, plus company-to-contact syncing).
- Check how recycling works. HubSpot’s default lifecycle stage only moves forward through its own tools; moving a record back requires clearing the value first. If leads are recycled, find the workflow doing it and check it behaves.
- Trace lead status and owner assignment. Who sets the owner, based on what, and what happens when the rule does not match?
The output of week two is a one-page diagram: how a record enters, what moves it forward, and who touches it at each stage.
Week 3: the reports and the sync
Trace the five reports leadership reads. For each: which properties it uses, what sets those properties, and whether the numbers match an independent export. If the board deck pipeline and a raw deals export disagree, see our explainer on why they drift.
Inspect the CRM sync if there is one. For Salesforce, check:
- The inclusion segment (limits which contacts go from HubSpot to Salesforce) and selective sync (limits the reverse direction).
- The sync rule on each mapped field: Prefer Salesforce unless blank, Always use Salesforce, Two-way or Don’t sync.
- The sync errors under the integration’s Sync health section.
Our HubSpot–Salesforce sync audit playbook walks through each check.
Check scoring. HubSpot retired its legacy score properties on 31 August 2025. If workflows or reports still rely on an old score property, they are running on a number that stopped updating.
Week 4: findings, ranking, and the first decision
Write each problem as a finding with four parts: what is wrong, the evidence, what it breaks, and what fixing it involves. Then rank by exposure:
- Anything that corrupts numbers leadership already uses (lifecycle, pipeline, source).
- Anything that affects sending or compliance (suppression, consent, domain authentication).
- Anything that wastes team time (duplicate properties, orphaned workflows).
- Cosmetic clean-up.
Share the ranked list with your manager and with sales leadership before you fix anything. The list is what gets the fix funded, and it protects you when the numbers move after the fix.
What not to do in the first 30 days
- Do not delete properties or workflows. Archive or pause, and only after the baseline export.
- Do not decide on a platform migration. You do not yet know whether the problem is the platform or its configuration.
- Do not rebuild the lead scoring model. Validate the current one against outcomes first.
- Do not promise leadership new numbers until you know why the old ones were wrong.
- Do not bulk-merge duplicates until you know which source keeps creating them. Otherwise they come back.
A 30-day checklist you can copy
| Day | Deliverable |
|---|---|
| 1–3 | Access confirmed; dated baseline exports saved |
| 4–7 | Property, workflow, user and integration inventory |
| 8–14 | Lifecycle definitions and the “how records move” diagram |
| 15–21 | Report traces for the five leadership reports; sync review |
| 22–28 | Findings written with evidence and exposure |
| 29–30 | Ranked fix list agreed with your manager and sales |
For the full list of checks behind weeks two and three, use our HubSpot audit checklist.
If you want it done for you
Our read-only GTM Systems Audit is this 30-day plan run by people who have done it many times: three weeks, from USD 1,500, every finding with its evidence export, credited in full against the fix. It is built to hand to a new leader or a first marketing-ops hire. See how we help new marketing leaders and a sample report.
FAQ
What should I do first when I inherit a HubSpot portal?
Confirm your access, identify every Super Admin, and export contacts, companies, deals, properties, workflows, users and integrations on day one. That dated baseline is what every later finding and fix will be measured against.
Should I clean up an inherited HubSpot portal straight away?
No. Spend the first month reading, not changing. Early clean-up erases the evidence of what was wrong and breaks comparisons with previous quarters. Archive or pause rather than delete, and only after the baseline export.
How do I find out why lifecycle stages look wrong?
List every rule that sets lifecycle stage: workflows, forms, imports, integrations and HubSpot’s automatic settings. Where several rules set the same property, the result depends on which runs when, and that is usually the cause. Also remember the default stage only moves forward unless cleared first.
How do I evaluate a HubSpot account I inherited without an admin handover?
Work from exports and settings screenshots: property usage, the workflow list with last activity, user permissions and connected apps. The centralised audit log shows 30 days of user activity, with more categories on Enterprise, so older changes may be unrecoverable.
When should I bring in outside help?
When the portal has a Salesforce sync, when leadership needs a defensible answer within weeks, or when you are the only person who can run the audit and also has to run the team. A read-only audit gives you the evidence without taking you out of the seat.
Should a new marketing leader migrate off HubSpot?
Not in the first quarter. Audit first. Most problems that look like platform limits turn out to be configuration, and the audit’s exports become the migration inventory if you do decide to move.