Property sprawl is the silent tax on every HubSpot portal. Archiving fixes it—but only if you do it in the right order.
Every B2B team that has been on HubSpot for more than a year is carrying dead weight. Properties created for campaigns that ended. Custom fields added by integrations that were replaced. Dropdown options requested by managers who left three quarters ago. The properties are still there—cluttering record views, confusing reps, polluting reports, and making every new configuration harder than it needs to be.
The solution is straightforward: hubspot archive properties that no longer serve a business purpose. But "straightforward" isn't the same as "simple." HubSpot won't let you archive a property that's referenced in a workflow, form, report filter, or segment. Archive the wrong property and you break automations your team depends on. Skip the dependency check and you're staring at error messages across the portal. This post walks you through how to hubspot archive properties safely—without breaking the workflows and tools that still matter—as part of a broader hubspot CRM cleanup initiative.
Archiving a property in HubSpot removes it from active use—it no longer appears in record views, forms, list filters, or report builders—but preserves the underlying data for 90 days before permanent deletion. During that 90-day window, you can restore the property and its data if you discover it was still needed. Understanding how to hubspot archive properties correctly is the difference between a clean portal and a broken one.
This is different from deleting. Deletion is immediate and irreversible. Archiving gives you a safety net—a buffer period where the property is invisible to your team but recoverable by an admin. For any hubspot portal cleanup effort, archiving is the correct first step. You never delete a property you're unsure about. You archive it, wait, and confirm nobody misses it before letting the 90-day clock run out.
The critical limitation: HubSpot blocks archiving for properties used in what it calls "assets preventing archiving"—workflows, segments, forms, and certain report filters. If a property is referenced in any of these, you must remove the reference before HubSpot will let you archive. Properties used only in index page views (as a column or sort) can now be archived directly without removing them from each view—a recent improvement that simplifies cleanup significantly.
Before diving into the how, it's worth understanding why property sprawl matters beyond the obvious clutter. Gartner estimates poor data quality costs organizations an average of $12.9 million per year. Property sprawl is one of the most common drivers of that cost in HubSpot portals—not because the properties themselves are expensive, but because of what they do to adoption, data quality, and operational efficiency.
Every unnecessary property on a deal or contact record is friction. When a rep opens a record and sees 50+ fields—most of which they don't recognize or need—they disengage. They stop scrolling. They stop updating. The CRM becomes something they tolerate instead of something they use. This is the adoption problem that no amount of training can solve because the root cause is structural, not behavioral.
Properties that haven't been updated in months still appear in dropdown menus when building reports. Team members accidentally filter on dormant properties and get results that look accurate but aren't. Worse, auto-populated default values on unused properties can skew aggregate reports without anyone noticing—because nobody's actively monitoring data in fields that shouldn't exist.
Every workflow that references a property creates a dependency. The more properties you have, the more dependencies exist—and the harder it becomes to modify or consolidate workflows without triggering cascade failures. Property sprawl makes your automation layer brittle. Archiving unused properties reduces the dependency surface area, making every remaining workflow simpler and easier to maintain.
This is the process we use at Squad4 for every hubspot archive properties initiative. The sequence matters—skipping the dependency audit is how teams break workflows they didn't know existed.
Navigate to Settings → Properties. Select each object type (Contacts, Companies, Deals, Tickets) and export the full property list. For each custom property, categorize it into one of three buckets:
Active—Used in a current workflow, report, form, or record view. Updated within the last 6 months. Has a clear owner and documented purpose.
Dormant—Exists but hasn't been updated in 6+ months. Not referenced in any active workflow. May have been created for a campaign, integration, or process that no longer exists.
Unknown—Nobody on the current team can explain what it's for, when it was created, or what data it's supposed to hold. No documentation exists.
The Dormant and Unknown categories are your archive targets. For most portals that have been active for 2+ years, these categories represent 40–60% of all custom properties.
Before touching anything, check where each target property is referenced. HubSpot shows this when you attempt to archive—but doing it reactively means you'll hit blockers one at a time. Do it proactively instead.
For each property you plan to archive, check:
Workflows—Is the property used as an enrollment trigger, a branch condition, or an action target (like "Set property value")? If yes, and the workflow is active, you need to evaluate whether the workflow still needs that property or whether the workflow itself is a candidate for consolidation.
Forms—Is the property a field on any active form? Archiving it will remove it from the form, which could break lead capture if the field is required.
Lists and segments—Is the property used as a filter criterion in any active list? Archiving removes the filter, which could change list membership and affect email sends or workflow enrollment.
Reports and dashboards—Is the property used as a filter, grouping, or measure in any report? Archiving won't always block the action, but the report will break silently.
Record sidebars and cards—Is the property displayed on any custom record view? Recent HubSpot updates now allow archiving properties used only in views without manual removal, but it's still worth documenting.
For each blocking dependency, decide: does the asset (workflow, form, list) still need this property, or is the asset itself a cleanup candidate?
If the workflow is inactive—Turn it off (if not already) and remove the property reference, or delete the workflow entirely if it serves no historical purpose.
If the workflow is active but the property reference is outdated—Update the workflow to use the correct current property, then archive the old one.
If the form is active—Remove the property from the form before archiving. If the field was collecting data you still need, map it to an active property first.
If the list uses the property as a filter—Update the list filter criteria or retire the list if it's no longer used for email sends or workflow enrollment.
This dependency resolution step is where most teams stall. It feels tedious—because it is. But it's the difference between a clean archive and a cascade of broken automations. This is also where hubspot user permissions matter—only admins with Edit Property Settings permissions can archive, and restricting who creates properties in the first place prevents the sprawl from recurring.
Don't archive 200 properties on a Friday afternoon. Archive in batches of 15–25, grouped by object type. After each batch, wait 48–72 hours and monitor for three things:
Workflow errors—Check Automation → Workflows and look for new error flags. Any workflow that suddenly shows enrollment or action errors may have been referencing a property you archived.
Team complaints—If a rep or manager asks "where did this field go?" within the first week, you have a property that was more Active than your audit suggested. Restore it from the Archived tab.
Report discrepancies—Run your core pipeline and revenue reports. If numbers shift unexpectedly, a report may have been filtering on a property you archived.
The 90-day recovery window is your safety net. Use it intentionally—archive, observe, and only let properties permanently delete after you've confirmed zero impact.
Create a simple reference (spreadsheet or shared doc) that logs every archived property: its name, object type, the date archived, the reason for archival, and what dependencies were resolved. This document serves two purposes: it's your audit trail if anyone asks what happened, and it's your governance reference for preventing the same properties from being recreated six months later.
Not every unused-looking property is safe to remove. Even experienced admins who know how to hubspot archive properties can make costly mistakes by removing fields that look dormant but serve critical background functions. Some properties carry historical data that's invisible in day-to-day operations but critical for long-term analysis.
Original Source properties—HubSpot's default attribution properties (Original Source, First Touch, Last Touch) should never be archived, even if they look redundant. They power marketing attribution reporting and can't be recreated once deleted.
Integration-mapped properties—Properties that sync with external tools (ERP, billing, support platforms) may appear dormant because they're updated by the integration, not by users. Archiving them breaks the sync silently. Always confirm with your integrations owner before archiving any property with an API or integration origin.
Properties created during your initial hubspot data import—Some properties were created specifically to map source data during migration. They may look unused now, but they hold historical values that power lifecycle reporting and original-source attribution. Before archiving, verify the data doesn't feed any active report.
Properties used in calculated fields—If a property is referenced in a calculated or rollup property's formula, archiving it breaks the calculation without an obvious error message.
Lifecycle stage and lead status—These are system properties that HubSpot relies on for core functionality. They can't be archived through the normal process, but they're worth mentioning because teams sometimes create duplicate custom versions that should be consolidated, not archived.
Archiving is the cure. Governance is the prevention. Without a property creation process, you'll be running this same cleanup in six months.
Require a property request process. No new custom property gets created without a documented business justification, an assigned owner, and a plan for how the data will be used. This single gate prevents the majority of property sprawl.
Assign property ownership. Every custom property should have a named owner—the person responsible for ensuring the data is current, the property is still needed, and the documentation is maintained.
Run quarterly property audits. Every quarter, export your property list and check: How many new custom properties were created in the last 90 days? Do they all have owners and documentation? Are any properties from the previous audit's Dormant list still dormant? If yes, archive them.
Restrict creation permissions. Limit property creation to RevOps admins and trained CRM owners. When anyone on the team can create a custom property, everyone does—and nobody cleans them up. Getting hubspot user permissions right is the governance layer that prevents property sprawl from recurring after every cleanup.
Every property you archive makes your portal faster to navigate, simpler to configure, and easier to adopt. It reduces the dependency surface for workflows, cleans up dropdown menus in report builders, and eliminates the visual clutter that drives reps toward spreadsheet workarounds.
If your portal has more custom properties than people on your team—or if nobody can explain what half of them do—it's time to hubspot archive properties that aren't earning their place. Export, categorize, audit dependencies, archive in batches, and document what you did. It's methodical work, not glamorous work. But it's the work that makes every other RevOps initiative perform better.
For the complete four-phase cleanup framework—including the purge, simplification, and governance phases that surround property archiving—read our full guide: A RevOps Guide to HubSpot CRM Cleanup and Portal Recovery. Squad4 helps B2B teams cut property sprawl and restore portal usability. We run the dependency audit, execute the archive, and build the governance that prevents the bloat from coming back.