How to Move Deals Between Pipelines in HubSpot

HubSpot sales pipelines are great until you need to reorganize them. Maybe you're splitting one pipeline into two — separating new business from renewals. Maybe you're consolidating three regional pipelines into one global pipeline. Maybe you've inherited a portal with a pipeline that doesn't match your actual sales process, and you need to start fresh.

Whatever the reason, moving deals between pipelines is a task that sounds simple but has more nuance than expected. Deal stage history, automation triggers, reporting integrity, and property mappings all come into play.

Understanding pipelines and deal stages

A quick refresher on how HubSpot pipelines work, because the details matter when moving deals.

Pipelines are containers for deal stages. Each pipeline has its own set of stages with its own stage names, probabilities, and order. A HubSpot portal can have one pipeline (Free/Starter) or multiple pipelines (Professional/Enterprise).

Deal stages are specific to a pipeline. A deal in "Pipeline A" with stage "Negotiation" and a deal in "Pipeline B" with stage "Negotiation" are in different stages, even if the names are identical. This is important: when you move a deal from one pipeline to another, you must also set a stage that exists in the destination pipeline.

Deal stage history tracks every stage change a deal goes through, with timestamps. This history powers time-in-stage reporting and sales velocity metrics. Moving a deal to a new pipeline resets its stage context — the deal won't carry its old pipeline's stage history into the new pipeline.

Why teams reorganize pipelines

Understanding the motivation helps determine the right approach:

Splitting a pipeline

A single "Sales Pipeline" is being split into "New Business Pipeline" and "Renewals Pipeline." Deals need to be distributed to the appropriate new pipeline based on whether they represent new or existing customers.

Consolidating pipelines

Multiple pipelines (by region, product line, or team) are being merged into one. All deals from the old pipelines need to land in the correct stage of the new pipeline.

Replacing a pipeline

The old pipeline's stages don't match the updated sales process. A new pipeline with new stages has been created, and active deals need to be migrated from old to new.

Cleaning up a pipeline

Stale deals — opportunities that went cold months ago but were never closed — need to be moved to a "Closed Lost" stage or a holding pipeline to clean up the active pipeline view.

Moving deals individually

For a small number of deals (under 20), moving them one at a time is straightforward.

1. Open the deal record
2. Click the "Pipeline" dropdown in the left sidebar (or in the deal stage header)
3. Select the destination pipeline
4. Select the appropriate stage in the new pipeline
5. Save

HubSpot will warn you that moving a deal to a new pipeline changes its stage. Confirm the action.

What happens to the deal:

• The pipeline property is updated to the new pipeline
• The deal stage property is updated to the stage you selected
• A new entry is added to the deal's activity timeline noting the pipeline change
• The deal's stage history in the old pipeline is preserved in the record's history, but won't appear in the new pipeline's time-in-stage calculations

What doesn't happen:

• Associated contacts, companies, and line items are not affected
• Deal amount, close date, and other properties are not changed
• Notes, tasks, and activities stay on the deal

Moving deals in bulk: native options

HubSpot offers limited native tools for bulk deal movement.

Bulk edit from the deals list view

1. Navigate to Sales > Deals
2. Switch to Table view (not Board view — bulk edit doesn't work from the Kanban board)
3. Filter for the deals you want to move (by current pipeline, stage, owner, etc.)
4. Select the deals (use "Select all" to select the entire filtered list)
5. Click "Edit" in the toolbar
6. Choose "Pipeline" as the property to edit
7. Select the destination pipeline
8. Choose the destination stage

This works but has constraints:

• All selected deals go to the same stage. You can't route some deals to "Qualified" and others to "Proposal" in the same batch. If different deals need different stages, you need multiple batch operations.
• No preview. The change is applied immediately with no confirmation screen showing what's about to change.

Import/export approach

For more control over stage mapping:

1. Export your deals list, including Record ID, Deal Name, current Pipeline, and current Deal Stage
2. In your spreadsheet, add the destination pipeline and stage for each deal. This lets you map different source stages to different destination stages.
3. Re-import with "Update existing deals" selected, mapping the Record ID for matching

This gives you per-deal control over the destination stage but requires spreadsheet work and has no undo.

Stage mapping: the critical step

Before moving any deals in bulk, create a stage mapping document. This maps each stage in the source pipeline to a stage in the destination pipeline.

Example:

Notice that two source stages map to one destination stage in this example. That's common when consolidating pipelines. The reverse — one source stage mapping to multiple destination stages — requires per-deal decisions about which destination stage is appropriate.

Share this mapping with your sales managers before executing. They'll often have opinions about how deals should be categorized that you wouldn't know from looking at the data alone.

Using search and replace for pipeline text cleanup

When deals move between pipelines, the deal names often need updating to reflect the new context. Deals named "Acme Corp - New Business Pipeline - Q1 2026" should probably be renamed to "Acme Corp - Q1 2026" if you're consolidating pipelines and the pipeline name in the deal name is no longer relevant.

A search-and-replace operation across deal names handles this cleanly. Search for " - New Business Pipeline" in the Deal Name property and replace with an empty string. Preview the changes to make sure the resulting names look right, then apply.

Similarly, if deals have a custom text property that references the old pipeline name, stage name, or any text that should change with the pipeline move, a bulk search-and-replace operation is more efficient than updating records one by one.

Protecting your reporting

Pipeline changes affect reporting in ways that aren't immediately obvious. Here's how to protect your data:

Take snapshots before moving deals

Before any bulk pipeline change, export the following for your records:

• All deals with current pipeline, stage, amount, close date, and create date
• Pipeline-level reports (deals by stage, pipeline velocity, forecast)
• Time-in-stage reports for the source pipeline

These snapshots let you reconstruct historical performance even after deals have moved.

Understand what happens to time-in-stage data

When a deal moves to a new pipeline, its time-in-stage clock resets for the new pipeline. If a deal spent 14 days in "Negotiation" in the old pipeline and is moved to "Proposal/Negotiation" in the new pipeline, the new pipeline will show 0 days in stage.

The old stage history is still in the deal's activity log, but it won't appear in pipeline-level reports for the new pipeline. If time-in-stage accuracy matters for your reporting, note the migration date and account for it in your analysis.

Update your dashboards

After moving deals, review and update:

• Dashboard filters that reference the old pipeline
• Reports filtered by specific stages that no longer exist
• Sales goals and quotas tied to the old pipeline
• Forecasting views configured for the old pipeline

Create a "migration" marker

Set a custom property (e.g., "Pipeline Migration Date" or "Original Pipeline") on all migrated deals. This lets you filter these deals in reports and distinguish migrated deals from deals that originated in the new pipeline. This is invaluable for apples-to-apples reporting in the months after the migration.

Handling workflows and automation

Pipelines and deal stages are frequently used as workflow triggers. Before moving deals:

Inventory all deal-based workflows. Go to Automation > Workflows and filter for deal-based workflows. Check which ones use pipeline or deal stage as enrollment triggers or branching conditions.

Update triggers before moving deals. If a workflow triggers on "Deal stage is changed to Closed Won in New Business Pipeline," and you're retiring that pipeline, update the trigger to reference the new pipeline before moving deals. Otherwise, migrated deals might trigger (or fail to trigger) workflows unexpectedly.

Watch for re-enrollment. If a workflow has re-enrollment enabled and triggers on a stage change, moving a deal to a new pipeline counts as a stage change. This could re-enroll deals in sequences or trigger actions that have already run.

Pause sensitive workflows during migration. For workflows that send customer-facing emails or create tasks based on deal stage changes, consider pausing them during the migration window. Re-enable them after all deals have been moved and triggers have been updated.

After the migration

Once deals are in their new pipeline:

1. Verify deal counts. Compare the number of deals in the new pipeline against your pre-migration export. Every deal should be accounted for.
2. Spot-check stage assignments. Open 10-15 deals at random and verify they're in the correct stage per your mapping.
3. Test workflows. Create a test deal in the new pipeline and walk it through the stages to verify automations fire correctly.
4. Archive the old pipeline. Once you're confident everything is migrated, you can delete the old pipeline in Settings > Objects > Deals > Pipelines. HubSpot won't let you delete a pipeline that still has deals in it, so any remaining deals need to be moved or deleted first.
5. Communicate to the team. Let reps know which pipeline to use going forward, what the new stages mean, and who to contact if they see anything wrong with their deals.

Pipeline reorganization is disruptive in the short term but pays off quickly if done carefully. A well-structured pipeline that matches your actual sales process improves reporting accuracy, rep productivity, and forecast reliability.