Every year, thousands of organizations migrate HubSpot portals. Mergers and acquisitions consolidate portals. Companies outgrow starter accounts and move to enterprise instances. Agencies onboard new clients and need to transfer historical data. Regardless of the reason, most teams make the same expensive mistake: they skip the pre-migration audit.
The cost of this oversight is real and measurable. Migrating a HubSpot portal without first auditing its contents is like packing every item from your old house into moving boxes without checking what is worth keeping. You pay to pack it, pay to move it, and pay to unpack it, only to throw half of it away at the new location anyway. Except with HubSpot migrations, those costs are measured in consultant hours, project delays, and data cleanup that should have happened before the move.
A pre-migration portal audit identifies exactly what should travel to the new portal, what should be archived, and what should be left behind. Organizations that invest in this step consistently report 25-40% reductions in migration cost, 30-50% faster project timelines, and significantly fewer post-migration issues.
This guide breaks down why the pre-migration audit is the highest-ROI investment in any migration project, with real cost examples and a clear process for getting it done.
The True Cost of Migrating Junk Data
When teams migrate without auditing, they bring everything with them: every inactive contact, every broken workflow, every duplicate record, every obsolete email template. This is not just a cleanliness issue. It directly inflates the cost of migration in several measurable ways.
Volume-Based Migration Pricing
Most migration services, whether you use a tool, an agency, or an internal team, scale their pricing based on volume. The more contacts, records, assets, and workflows you migrate, the more you pay. Consider a portal with 200,000 contacts:
- A data quality audit might reveal that 35% of those contacts are invalid: bounced emails, unsubscribed contacts who will never re-engage, duplicate records, and test entries.
- Migrating 200,000 contacts instead of 130,000 increases data transfer time, increases the number of field mappings to validate, and increases the post-migration QA workload.
- At typical migration service rates, this unnecessary volume adds $3,000-$8,000 in direct costs for a mid-sized portal.
ROI Calculation: Contact Cleanup Alone
A portal with 200,000 contacts where 35% are invalid means 70,000 records that should never be migrated. At typical per-record migration rates, removing these before the move saves $3,000–$8,000 in direct migration costs — before accounting for the hours of post-migration QA those junk records would have required.
Complexity Multipliers
Junk data does not just add volume. It adds complexity. Duplicate contacts create merge conflicts in the destination portal. Broken workflows that reference deleted properties cause errors during migration testing. Inactive integrations that are migrated to the new portal may reconnect with unexpected behaviors.
Each of these issues requires investigation, diagnosis, and resolution, usually at consulting rates of $150-250 per hour. A single complicated data conflict can consume 2-4 hours of a migration specialist’s time.
| Junk Data Type | Migration Impact | Typical Resolution Cost | Prevention via Audit |
|---|---|---|---|
| Duplicate contacts | Merge conflicts in destination | $300–$600 per batch | Deduplicate before migration |
| Broken workflows | Errors during migration testing | $150–$500 per workflow | Archive or delete pre-migration |
| Stale integrations | Unexpected reconnection behaviors | $200–$800 per integration | Disconnect before migration |
| Orphaned custom properties | Mapping failures, bloated schema | $100–$300 per batch | Remove unused properties |
| Invalid contact records | Inflated volume, wasted QA time | $0.02–$0.05 per record | Purge before extraction |
Post-Migration Cleanup Tax
The most insidious cost of skipping the audit is what happens after migration. Teams discover problems in the new portal: duplicate records that came over from the source, workflows that do not make sense in the new context, reports that reference properties or lists that were never properly migrated.
Your team is working in an unfamiliar environment, production processes already depend on the migrated data, untangling issues requires understanding both the old and new portal simultaneously, and urgency increases costs as teams scramble to fix live operational issues.
We have seen organizations spend more on post-migration cleanup than they spent on the migration itself. That is entirely avoidable.
Time Savings: The Hidden ROI of Pre-Migration Auditing
Beyond direct cost, a pre-migration audit significantly compresses project timelines. Migration projects that skip the audit phase inevitably encounter delays that dwarf the time the audit would have taken.
Reduced Scope Means Faster Execution
A typical HubSpot portal migration follows this sequence: scope definition, field mapping, data extraction, transformation, loading, and QA testing. Every step scales with volume and complexity.
Consider the workflow component alone. A portal with 120 active workflows might have:
Without an audit, a migration team must evaluate all 120 workflows during the project. With a workflow audit completed in advance, they only need to focus on the 30 that matter. That is a 75% reduction in one of the most time-consuming aspects of migration.
Fewer Surprises During Migration
Migration projects derail when unexpected issues surface during execution. A pre-migration audit surfaces these issues when they are cheap to resolve:
- Undocumented dependencies between workflows, lists, and forms
- Custom properties with inconsistent data that will cause mapping failures
- Integration connections that require reconfiguration in the destination portal
- Permissions and access configurations that need to be rebuilt
Each unexpected issue discovered during migration typically adds 1–3 days to the project timeline. A pre-migration audit can uncover 10–15 of these issues in advance, potentially saving weeks of delay.
Parallel Workstreams
When the audit is complete, cleanup and migration preparation can run in parallel. Your operations team can start archiving outdated assets and cleaning data while the migration team finalizes technical planning. Without the audit, these activities are sequential, extending the total project timeline.
Reducing Migration Scope: What to Keep, Archive, and Leave Behind
The most valuable output of a pre-migration audit is a clear, categorized inventory of every asset in your portal with a recommendation for each one.
| Asset Type | Migrate (Active) | Archive (Preserve) | Delete (No Value) |
|---|---|---|---|
| Contacts | Valid data, recent engagement | No engagement in 12+ months | Bounced, duplicates, test entries |
| Workflows | Active, driving business processes | Inactive 90+ days | Erroring, broken references |
| Email templates | Used in current campaigns/sequences | Past campaign assets | Drafts, test emails, legacy design |
| Forms & CTAs | Live on website | Completed campaign assets | Orphaned, never embedded |
| Custom properties | Populated, used in reports/workflows | Historical reference only | Zero or near-zero fill rates |
| Deals | Open opps + closed within reporting window | Closed-lost older than 12–24 months | Test deals, sample data |
| Dashboards & reports | Inform regular business decisions | Historical period analysis | Orphaned, never viewed |
| Lists | Used as triggers, segments, filters | Past campaign segments | Empty, duplicate criteria |
Category 1: Migrate (Active and Essential)
These are the assets that must move to the new portal to maintain business continuity:
- Active workflows currently driving lead nurturing, internal notifications, or data operations
- Contact and company records with valid data and recent engagement
- Deal records for open opportunities and closed deals within your reporting window
- Email templates actively used in campaigns and sequences
- Forms and CTAs currently live on your website
- Lists used as enrollment triggers, segmentation criteria, or reporting filters
- Custom properties actively populated and referenced in reports or workflows
- Dashboards and reports that inform regular business decisions
Category 2: Archive (Preserve but Do Not Migrate)
These assets have historical value but do not need to exist in the active portal:
- Closed-lost deals older than your reporting window (typically 12-24 months)
- Contacts who bounced, unsubscribed, or have not engaged in 12+ months
- Completed campaign assets (emails, landing pages) from past initiatives
- Inactive workflows that have been off for 90+ days
- Legacy email templates replaced by newer versions
- Historical reports for time periods you no longer actively analyze
Export these to a data warehouse or archive storage before migration. They are preserved for compliance and reference without bloating your new portal.
Category 3: Delete (No Value)
These assets serve no purpose and should be removed before migration:
- Duplicate records (contacts, companies, deals)
- Test records created during QA or training
- Broken workflows that error on enrollment
- Orphaned forms not embedded on any page
- Unused custom properties with zero or near-zero fill rates
- Draft emails that were never sent and are no longer relevant
- Sample data left over from initial HubSpot setup
Deleting this category is pure waste reduction. It costs nothing to remove and saves money at every subsequent stage of migration. For a comprehensive approach to what falls into each category, our portal audit checklist provides a complete framework.
Real Cost Examples: Audit vs. No Audit
To illustrate the financial impact, here are three composite scenarios based on real migration projects.
Scenario 1: Mid-Market B2B Company
Mid-Market B2B: 85,000 Contacts, 75 Workflows, 3 Integrations
Audit service ($2,500) + pre-migration cleanup ($1,500) + reduced-scope migration ($10,000) + minimal post-migration cleanup ($1,600) = $15,600 total in 5 weeks. Savings of $7,400 (32%) and 3 weeks compared to migrating without an audit.
Same Portal — No Audit Performed
Migration service ($15,000) + post-migration cleanup at 40 hours ($8,000) = $23,000 total in 8 weeks. Significantly more expensive, longer timeline, and the team spent weeks cleaning up issues that should have been caught before the move.
Scenario 2: Enterprise SaaS Company (Portal Consolidation)
- Migration service: $45,000
- Post-migration cleanup (120 hrs at $225/hr): $27,000
- Data conflicts resolution: $12,000
- Timeline: 14 weeks with multiple delays
- Audit service (both portals): $8,000
- Pre-migration cleanup: $9,000
- Reduced-scope migration: $30,000
- Post-migration cleanup (20 hrs): $4,500
Enterprise portal consolidation savings: $32,500 (39%) and 5 weeks. Portal consolidation after mergers and acquisitions is especially prone to hidden costs.
Our guide on merging two HubSpot portals covers the additional complexities these projects introduce.
Scenario 3: Agency Managing Client Migration
Portal size: 45,000 contacts, 35 workflows, 8 integrations
| Line Item | Without Audit | With Audit |
|---|---|---|
| Migration / agency hours | $10,500 (60 hrs at $175) | $6,125 (35 hrs at $175) |
| Audit service | — | $1,500 |
| Client internal hours | $3,000 | $1,000 |
| Total | $13,500 | $8,625 |
| Timeline | 6 weeks | 4 weeks |
Savings: $4,875 (36%) and 2 weeks. For agencies managing multiple client migrations, the efficiency gains compound rapidly. Our agency guide to replicating HubSpot automation covers related best practices for managing migrations at scale.
The Pre-Migration Audit Process: Step by Step
Here is a practical framework for conducting a pre-migration audit.
Phase 1: Inventory (Days 1–3)
Catalog every asset in the source portal: total contacts, companies, deals, and tickets with record counts. All workflows (active, inactive, erroring) with enrollment counts. Email templates, forms, CTAs, and landing pages. Custom properties with fill rates. Lists with membership counts. Connected integrations and data sync configurations. Dashboards, custom reports, user accounts, and permission sets.
Phase 2: Assessment (Days 4–7)
Evaluate each asset category against the Migrate/Archive/Delete framework. Score contact quality (valid email, recent engagement, complete records). Test every active workflow for errors and relevance. Review each integration for necessity. Validate custom property usage and reporting dependencies. Identify cross-dependencies between workflows, lists, forms, and properties.
Phase 3: Documentation (Days 8–10)
Produce a migration scope document: asset inventory with categorization, dependency map showing relationships, risk register with mitigation strategies, cleanup task list prioritized by impact and effort, revised migration scope with reduced volume estimates, and cost-benefit analysis showing projected savings.
Phase 4: Cleanup Execution (Days 11–20)
Execute the cleanup tasks: merge duplicate records, archive or delete flagged contacts, turn off and archive irrelevant workflows, remove unused custom properties, disconnect unnecessary integrations, archive outdated email templates, forms, and CTAs. This is where the savings are realized.
Understanding what you lose during a HubSpot data migration is critical context for the cleanup phase. Some data elements cannot be migrated regardless, so investing cleanup effort on those assets is doubly wasteful.
Bridging the Audit and Migration: Where These Disciplines Intersect
The pre-migration audit sits at the intersection of two disciplines: portal auditing and migration planning. The best outcomes happen when both perspectives are represented.
- Focuses on portal health: What is broken?
- What is underperforming or redundant?
- Approaches the portal as it exists today
- Identifies improvements regardless of migration
- Focuses on transferability: What can be moved?
- What requires transformation or breaks during transfer?
- Approaches the portal through the destination lens
- Flags technical constraints and dependencies
Combined Value
When both perspectives inform the pre-migration audit, you get insights that neither team would produce alone:
Rebuild Opportunity
The audit team identifies a technically functional but poorly designed workflow. The migration team confirms that recreating it in the new portal is a chance to rebuild it properly.
Native Alternative
The migration team flags a custom integration that will be difficult to re-establish. The audit team discovers it is underused and recommends a native HubSpot replacement.
Volume Reduction
The audit finds 40,000 contacts with no engagement in 18 months. The migration team calculates that excluding them saves $3,200 in migration costs and 12 hours of QA time.
This is why Jetstack’s approach combines audit expertise with migration capabilities. The two services are designed to work together, with audit findings directly feeding into migration planning.
How Jetstack’s Pre-Migration Audit Service Works
Jetstack offers a purpose-built pre-migration audit that combines automated scanning with expert analysis. Here is what the process looks like:
Portal Scanning
Our platform connects to your HubSpot portal and catalogs every asset, recording counts, activity dates, error rates, and dependencies.
Quality Scoring
Each asset receives a quality score based on data completeness, recent activity, error history, and business relevance.
Migration Readiness Assessment
Assets are categorized as migrate, archive, or delete with detailed justifications for each recommendation.
Cost Projection
We estimate the savings from the recommended scope reduction compared to a full migration.
Cleanup Roadmap
A prioritized task list for your team to execute before migration begins.
Migration Brief
A technical document that your migration team (internal or external) can use to plan the migration with confidence.
The audit typically completes in 5–7 business days and pays for itself many times over through reduced migration costs. Most clients see a 3–5x return on their audit investment.
Explore our pre-built audit packages in the Jetstack Marketplace or contact us to discuss your specific migration scenario.
For teams planning a complete HubSpot-to-HubSpot migration, our comprehensive migration guide is the natural next step after the audit is complete.
Frequently Asked Questions
How far in advance of a migration should I conduct the audit?
Ideally, 4-6 weeks before the migration project begins. This gives your team enough time to execute the cleanup tasks identified in the audit without rushing. If your migration is already underway, it is still worth conducting a rapid audit. Even partial cleanup reduces costs and risk. The worst time to discover data quality issues is during migration execution.
Can I do a pre-migration audit myself or do I need a specialist?
You can absolutely conduct a basic audit internally using the framework in this guide. The advantage of a specialist or automated tool like Jetstack is speed and comprehensiveness. Internal teams often miss cross-dependencies between assets, underestimate the scope of data quality issues, or lack benchmarks to compare against. A specialist brings pattern recognition from hundreds of prior audits that accelerates the process.
What if the audit reveals problems that delay the migration?
This is actually the audit working exactly as intended. Problems discovered during the audit are dramatically cheaper to fix than problems discovered during or after migration. If the audit reveals issues significant enough to delay the project, those same issues would have caused even longer delays (and higher costs) had they surfaced later. Adjust the migration timeline accordingly and address the issues properly.
Does a pre-migration audit replace a post-migration audit?
No. The pre-migration audit optimizes what goes into the migration. A post-migration audit validates that everything arrived correctly and is functioning in the new portal. Both are important. The pre-migration audit reduces the scope and cost of the post-migration audit, but it does not eliminate the need for post-migration validation.
How much does a typical pre-migration audit cost?
Costs vary based on portal size and complexity. For a mid-sized portal (50,000-150,000 contacts, 50-100 workflows), expect to invest $2,000-$5,000 for a professional audit. Enterprise portals with multiple hubs, complex integrations, and custom objects typically range from $5,000-$12,000. In every case, the audit cost should represent 10-20% of the projected migration cost and deliver 25-40% in total savings.
What happens to data that is archived rather than migrated?
Archived data should be exported to a secure storage location before migration. Common options include exporting to CSV files stored in cloud storage, loading into a data warehouse for historical analysis, or using HubSpot’s native export tools to create a complete backup. The key is ensuring the data remains accessible for compliance, legal, or historical reference purposes without occupying space in your active portal.