How to Migrate Sales Pipelines & Deal Stages to HubSpot

Before planning the migration, it's important to identify which pipeline-related assets need to be transferred. Most CRM platforms store similar sales data, but the structure and configuration may differ from HubSpot.

Sales Pipelines

Sales pipelines can be recreated in HubSpot to match your existing sales process.

Examples include:

• New Business Pipeline
• Enterprise Pipeline
• Renewal Pipeline
• Partner Pipeline

If your current CRM uses multiple pipelines, document each one before migration to ensure the structure is recreated correctly in HubSpot.

Deal Stages

Deal stages define the progression of opportunities within a pipeline.

Examples include:

• Qualification
• Discovery
• Proposal Sent
• Contract Review
• Closed Won
• Closed Lost

Each existing stage should be mapped to a corresponding HubSpot deal stage. If stage names differ, focus on matching the business process rather than the label itself.

Open Deals

Active opportunities can be migrated into HubSpot along with their current stage, owner, value, close date, and associated records.

Common deal properties include:

• Deal Name
• Amount
• Close Date
• Deal Owner
• Pipeline
• Deal Stage

These records typically become the primary focus of the migration because sales teams continue working with them immediately after go-live.

Closed Deals

Historical Closed Won and Closed Lost deals should also be migrated when reporting and forecasting continuity are important.

Migrating historical deals helps preserve:

• Revenue reporting
• Win rate calculations
• Sales performance metrics
• Pipeline trend analysis

Deal Associations

Deal associations define the relationships between deals and other CRM records.

Common associations include:

• Deal to Contact
• Deal to Company
• Deal to Activity Records

These relationships should be preserved during migration to maintain timeline history, reporting accuracy, and workflow functionality.

Before moving any data into HubSpot, verify that all pipelines, stages, deal properties, and associations have been identified and documented.

Before rebuilding pipelines or importing deals into HubSpot, audit your existing sales process. This helps identify configuration issues, unnecessary stages, and customizations that could affect the migration.

Audit Existing Sales Pipelines

Start by documenting all pipelines currently used in your CRM.

For each pipeline, capture:

• Pipeline name
• Purpose
• Number of active deals
• Number of closed deals
• Pipeline owner

Many organizations discover duplicate or unused pipelines during this step. These can often be consolidated before migration.

Audit Deal Stages

Review every deal stage within each pipeline.

Document:

• Stage name
• Stage order
• Purpose
• Associated reporting requirements

Example:

The goal is to understand how deals progress today before mapping them into HubSpot.

Review Pipeline Rules & Automations

Many CRMs have automation tied directly to pipeline stages.

Review:

• Lead assignment rules
• Task creation
• Internal notifications
• Automated emails
• Stage progression logic

Documenting these dependencies ensures critical sales processes can be rebuilt in HubSpot after migration.

Identify Custom Deal Properties

Most businesses track more than standard deal information.

Examples include:

• Contract Type
• Renewal Date
• Product Line
• Lead Source
• Competitor
• Implementation Status

Create a complete inventory of custom deal properties and determine:

• Whether the property is still needed
• The corresponding HubSpot property type
• Whether the property affects reporting or automation

The audit phase often reveals outdated stages, duplicate properties, and unused automation. Addressing these issues before migration simplifies the implementation and reduces cleanup work after go-live.

Before creating anything in HubSpot, document how your current pipelines are configured. This documentation becomes the blueprint for rebuilding the sales process and validating the migration later.

Export Current Pipeline Configuration

Export your existing deal data and capture the structure of each pipeline.

Document:

• Pipeline names
• Deal stages
• Stage order
• Stage probabilities
• Required fields
• Pipeline-specific automations

If your CRM supports pipeline exports, save them as a reference throughout the migration project.

Inventory Stage Definitions

Stage names alone do not provide enough information for migration.

For each stage, document:

• Stage purpose
• Entry criteria
• Exit criteria
• Typical sales activities
• Reporting requirements

Example:

This helps ensure stages are mapped based on business meaning rather than matching labels.

Review Stage Exit Criteria

Many sales teams move deals between stages based on specific actions or milestones.

Examples include:

Documenting these rules helps when rebuilding:

• Deal stage requirements
• Workflow automation
• Sales process governance
• Pipeline reporting

Without clearly defined exit criteria, teams often recreate inconsistent pipelines that produce unreliable forecasting and reporting.

Once the pipeline structure, stage definitions, and stage movement rules are documented, you're ready to rebuild the sales process inside HubSpot.

Once the existing pipeline structure has been documented, recreate it inside HubSpot before importing any deal records. This ensures incoming deals are assigned to the correct pipeline and stage during migration.

Create Pipelines

Navigate to:

Settings → Objects → Deals → Pipelines

Create a pipeline for each sales process identified during the audit.

Examples:

• New Business
• Enterprise Sales
• Renewals
• Channel Partners

Avoid creating pipelines that are no longer actively used. Migration is a good opportunity to simplify pipeline management.

Screenshot Opportunity: HubSpot Deal Pipeline Settings

Configure Deal Stages

After creating the pipeline, add the corresponding deal stages.

For each stage:

• Set the stage name
• Arrange the correct stage order
• Define whether the stage represents an open, won, or lost opportunity

Example:

Focus on matching the sales process rather than copying stage names exactly.

Configure Stage Probabilities

HubSpot uses stage probabilities to support revenue forecasting and reporting.

For each open stage, assign a probability that reflects the likelihood of closing.

Example:

If your existing CRM already uses stage probabilities, replicate them where appropriate.

Set Required Properties

HubSpot allows administrators to require specific properties when deals enter or exit stages.

Common examples include:

• Deal Amount
• Close Date
• Product Line
• Contract Type
• Next Step

Required properties improve data quality and ensure sales representatives capture the information needed for forecasting and reporting.

Review your documented stage exit criteria and determine which properties should be mandatory at each stage.

Once pipelines, stages, probabilities and required properties have been configured, HubSpot is ready to receive migrated deal records.

With the pipeline structure in place, the next step is migrating deal records into HubSpot. The goal is to ensure deals are imported into the correct pipeline, assigned to the correct stage, and retain all required business data.

Prepare Deal Data

Before importing, clean and standardize the deal export from your source CRM.

Review:

• Deal names
• Deal stages
• Pipeline values
• Close dates
• Deal amounts
• Deal owners
• Custom deal properties

Most importantly, update the deal stage values in your source data so they align with the HubSpot deal stages you created earlier.

Example:

This simplifies field mapping during import and reduces stage assignment errors.

Map Deal Properties

HubSpot's import tool allows you to map source CRM fields to HubSpot deal properties.

Common mappings include:

Custom properties should also be mapped during this stage.

Examples:

• Contract Type
• Renewal Date
• Product Category
• Lead Source
• Implementation Status

Carefully review all mappings before proceeding with the import.

Preserve Deal Ownership

Deal ownership should be migrated whenever possible to maintain accountability and reporting accuracy.

Before importing deals:

1. Create all required users in HubSpot.
2. Confirm user email addresses match the ownership data in the source CRM.
3. Validate ownership mapping during the import process.

Without existing HubSpot users, deal ownership cannot be assigned correctly during migration.

Import Deals into the Correct Pipeline

Once the data has been prepared and mapped, import the deal records into HubSpot.

Best practice is to:

1. Import a small sample first.
2. Validate stage assignments.
3. Review ownership assignments.
4. Confirm custom property values.
5. Verify pipeline placement.

After successful testing, proceed with the full import.

Post-import, review a sample of deals from each pipeline to confirm:

• Correct deal stage
• Correct pipeline
• Correct owner
• Correct amount
• Correct close date
• Correct custom property values

The deal import should only be considered complete after both data accuracy and pipeline placement have been validated successfully.

Deals rarely exist on their own. They are typically connected to contacts, companies, activities, and other CRM records. Preserving these relationships is critical because many HubSpot reports, workflows, and timeline views rely on associations.

Associate Deals with Contacts

Each deal should remain connected to the appropriate contacts involved in the buying process.

HubSpot supports deal-to-contact associations during import using a unique contact identifier.

Common identifiers include:

• Email Address
• Record ID
• Custom Unique Identifier

Best practice is to migrate contacts before importing deals so HubSpot can match the association correctly.

Example:

When imported correctly, HubSpot automatically associates the deal with the corresponding contact record.

Associate Deals with Companies

Deal-to-company associations are equally important because they support account-level reporting and sales visibility.

HubSpot can associate deals with companies using:

• Company Domain Name
• Company Record ID
• Custom Unique Identifier

Example:

As with contacts, companies should be migrated before importing deal associations whenever possible.

Validate Relationship Integrity

After importing deals and associations, validate that relationships were created successfully.

Review a representative sample of records and confirm:

• Deals are associated with the correct contacts
• Deals are associated with the correct companies
• Contacts appear on deal records
• Companies appear on deal records
• Associated activities remain accessible

You should also review HubSpot reports and record timelines to verify that the relationships support reporting and workflow requirements.

After migrating pipeline data and associations, rebuild the automation that supports your sales process. This ensures opportunities continue moving through the pipeline efficiently and that sales teams receive the right tasks, notifications, and assignments.

Lead-to-Deal Automation

Many organizations automatically create deals when a lead reaches a specific qualification stage.

Examples include:

• Lead becomes Sales Qualified
• Demo is booked
• Opportunity is identified
• Form submission meets qualification criteria

Review your existing CRM automation and recreate the logic using HubSpot workflows.

Screenshot Opportunity: HubSpot Deal Creation Workflow

Deal Assignment Rules

Deal ownership often depends on predefined business rules.

Common assignment criteria include:

• Geographic territory
• Industry
• Company size
• Product line
• Sales team

Using HubSpot workflows, automatically assign deal owners when deals are created or updated.

Example:

Automated assignment helps maintain consistency and reduces manual administration.

Internal Notifications

Sales teams often rely on notifications to take action at critical points in the sales process.

Common examples include:

• New deal created
• Deal enters negotiation stage
• Deal becomes stalled
• Deal closes successfully

Recreate these alerts using HubSpot workflow actions to ensure sales representatives and managers remain informed.

Stage-Based Workflows

Many organizations trigger actions when a deal enters a specific pipeline stage.

Examples include:

Using HubSpot workflows, you can automate these actions based on pipeline stage changes.

After rebuilding automation, test each workflow using sample deals to confirm:

• Enrollment triggers work correctly
• Actions execute as expected
• Notifications are delivered
• Ownership updates correctly
• Stage-based automation functions properly

Automation should only be considered migrated when the underlying business process has been validated, not simply recreated.

Before the migration is considered complete, validate that pipeline data, associations, reporting, and automation function correctly inside HubSpot. This step helps identify issues before sales teams begin working from the new system.

Verify Deal Counts

Start by comparing deal totals between the source CRM and HubSpot.

Review:

• Total deals
• Open deals
• Closed Won deals
• Closed Lost deals
• Pipeline-specific deal counts

Example:

Any discrepancies should be investigated before proceeding.

Validate Deal Stage Mapping

Review a sample of deals from every pipeline and confirm they were assigned to the correct HubSpot stage.

Validate:

• Pipeline assignment
• Deal stage assignment
• Stage order
• Stage probabilities
• Required property values

Common migration issues include:

• Deals assigned to incorrect stages
• Missing stage values
• Deals imported into the wrong pipeline

Screenshot Opportunity: HubSpot Deal Board View

Review Pipeline Reports

Reporting often reveals migration issues that are difficult to identify at the record level.

Review:

• Pipeline value reports
• Forecast reports
• Revenue reports
• Deal stage reports
• Win rate reports

Compare key metrics against the source CRM to ensure reporting continuity.

Examples include:

• Total pipeline value
• Open opportunity count
• Closed Won revenue
• Average deal size
• Sales cycle length

Significant differences may indicate mapping or association issues.

Test Automation

Finally, validate every workflow connected to the sales pipeline.

Review:

• Deal creation workflows
• Deal assignment workflows
• Internal notifications
• Stage-based workflows
• Closed Won automation

Create test deals and move them through the pipeline to confirm:

• Enrollment triggers work correctly
• Workflow actions execute successfully
• Notifications are delivered
• Ownership updates correctly
• Downstream processes are triggered

A pipeline migration should only be approved after data, reporting, associations, and automation have all been validated successfully.

Even well-planned migrations can create issues if pipeline structure, deal data, or automation are not reviewed carefully. The following mistakes are among the most common causes of post-migration pipeline problems.

Migrating Poorly Defined Stages

Many CRM systems contain stages that were created years ago and are no longer consistently used.

Examples include:

• Duplicate stages
• Overlapping stages
• Stages with unclear definitions

Migrating these stages into HubSpot often transfers existing process issues rather than improving them.

Incorrect Stage Mapping

Matching stages based on name alone can create reporting and forecasting problems.

For example:

Stage mapping should always be based on business purpose and sales process definitions.

Losing Deal Associations

Deals may import successfully while losing their relationships with contacts or companies.

This can impact:

• Pipeline reporting
• Account visibility
• Workflow automation
• Activity timelines

Always validate associations after migration.

Rebuilding Automation Before Validation

Many organizations immediately recreate workflows after importing data.

If pipeline stages or associations are incorrect, automation may produce inaccurate results.

Validate the data first, then rebuild automation.

Ignoring Historical Reporting Requirements

Historical deals often drive forecasting, revenue reporting, and performance analysis.

Failing to migrate historical opportunities can affect:

• Win rates
• Revenue trends
• Pipeline growth analysis
• Sales performance reporting

Before migration, determine how much historical deal data should be preserved and validate reporting requirements accordingly.

Use the following checklist before approving a pipeline migration project.

Pipeline Configuration Check

• Existing pipelines audited
• Pipeline structure documented
• Deal stages documented
• Stage definitions reviewed
• Stage probabilities configured
• Required properties configured

Deal Data Check

• Deal data cleaned
• Stage values standardized
• Pipeline values standardized
• Custom deal properties mapped
• Deal owners validated

Deal Import Check

• Test import completed
• Deal property mapping validated
• Pipeline assignment validated
• Deal stage assignment validated
• Ownership assignment validated

Association Check

• Deals associated with contacts
• Deals associated with companies
• Sample records validated
• Timeline history reviewed

Automation Check

• Deal creation workflows rebuilt
• Assignment workflows rebuilt
• Internal notifications rebuilt
• Stage-based workflows rebuilt
• Workflow testing completed

Reporting Check

• Deal counts verified
• Pipeline reports reviewed
• Revenue reports validated
• Forecast reports reviewed
• Historical reporting validated

User Acceptance Check

• Sales team validation completed
• Sales managers approved pipeline structure
• Automation testing approved
• Leadership sign-off completed

A migration should only be considered complete after pipeline configuration, deal data, associations, reporting, and automation have all been validated successfully.

Our HubXpert pipeline migration is more than moving deal records between systems. We focus on preserving the sales process, reporting structure, automation logic, and data relationships that drive revenue operations.

Our migration process typically includes:

1. Pipeline audit and discovery
2. Deal stage mapping
3. Pipeline configuration in HubSpot
4. Deal data preparation and cleanup
5. Deal ownership validation
6. Association migration
7. Workflow reconstruction
8. Migration QA and user acceptance testing

This approach helps ensure sales teams can continue working in HubSpot without losing visibility into active opportunities, historical performance, or pipeline reporting.

Migrating a sales pipeline to HubSpot involves more than importing deals. Pipelines, stages, ownership, associations, automation, and reporting all need to be configured correctly to preserve the integrity of the sales process.

By auditing your existing pipeline, standardizing deal data, rebuilding automation, and validating reporting after migration, you can ensure a smooth transition to HubSpot without disrupting day-to-day sales operations.

When executed properly, a pipeline migration provides an opportunity to improve data quality, streamline sales processes, and create a more scalable revenue operation inside HubSpot.

Can I migrate multiple sales pipelines into HubSpot?

Yes. HubSpot supports multiple deal pipelines, allowing businesses to recreate different sales processes for products, regions, teams, or business units.

How do I map existing deal stages to HubSpot?

Deal stages should be mapped based on their purpose and exit criteria rather than matching stage names directly. This helps preserve reporting accuracy and sales process consistency.

Will historical closed deals migrate into HubSpot?

Yes. Closed Won and Closed Lost deals can be imported into HubSpot and are often migrated to preserve historical reporting, forecasting, and revenue analysis.

Can I migrate deal ownership and sales reps?

Yes. Deal ownership can be migrated if the corresponding users are created in HubSpot before the import process begins.

What happens if my CRM uses more deal stages than HubSpot?

HubSpot allows fully customizable pipelines and deal stages. Most organizations can recreate their existing structure, although some stages may be consolidated during the migration process.

How do I validate a sales pipeline after migration?

Validate deal counts, stage assignments, ownership, associations, automation behavior, and pipeline reports before approving the migration.