Moving boxes between pipelines is super helpful if you have more than one pipeline to manage the same customer. With the ability to move boxes, you can start a customer in a sales pipeline, and once you close the deal, you can move the customer to an accounts pipeline.
Move a box or many boxes to a new pipeline.
When moving boxes between pipelines, it is essential to ensure the destination pipeline has a compatible structure to maintain data integrity and avoid mismatches or data loss. Matching column names and values and using consistent workflows can make transitions seamless and efficient.
First, open the pipeline view and select the boxes you'd like to move. Then, in the pipeline toolbar located above the stages, click on the three dots to the right. Last, select 'Move boxes' and the name of the pipeline you'd like to move the boxes to.
This action will move the box and any emails, comments, files, reminders, and newsfeed items inside the box.
As a friendly reminder, you'll want to ensure the Stage names, Column names, and dropdown/tag values are identical (i.e., spelling, casing, etc.) in both Pipeline A & B, or else you're at risk of losing data and or/ moving the boxes to an incorrect stage. If the Stage and Column names are identical in both pipelines, everything will get moved over just fine.
Steps to Avoid Mismatches and Data Loss
1. Duplicate Pipelines for Consistency
Duplicating pipelines ensures all columns, dropdowns, and tag values are identical between source and destination pipelines, minimizing errors during transfers.
2. Manually Match Columns Between Pipelines
If duplication isn't possible, manually match all necessary columns and tag/dropdown values in the source pipeline with the destination pipeline. For instance:
Identify critical columns and tag/dropdown values
Add these columns/values manually to the destination pipeline.
Double-check to confirm no columns are missing.
3. Leverage Streak's Warning Pop-Up
Streak provides warnings when column names/values are missing during transfers. Use these alerts to pause and rectify inconsistencies in the destination pipeline before proceeding, ensuring that nothing is overlooked. By employing these practices, potential data mismatches can be avoided, ensuring an efficient transition process.

