How to copy a pipeline to a new pipeline

A pipeline in Streak represents a process. For example: a sales pipeline helps you close deals, a hiring pipeline helps you move candidates through interviews, a support pipeline helps you resolve tickets. The structure of your pipeline — its stages and columns — reflects how that process works.

If two pipelines have the same stages and the same columns, that's a strong signal they represent the same process. And if it's the same process, it should be one pipeline. As a general rule: one pipeline per process.

So before duplicating a pipeline, ask yourself: am I actually running a different process, or do I just want to see a different slice of the same one? If it's the latter, Streak's Saved Views feature lets you filter, sort, and group your boxes to focus on exactly the segment you care about — without needing a second pipeline.

Why this matters:

- You can take one pipeline and break it into as many views as you need. You cannot take data from two separate pipelines and then recombine that data into one view.

- Maintaining two pipelines means duplicating your setup work and your ongoing data entry.

- Reporting across two pipelines is harder — for example, to see "new boxes," you'd have to check two places instead of one.

If Saved Views solve your use case, start there. If you've considered this and still want to copy your pipeline, read on.

When you export a pipeline, the following data can be included in the export:

✅ Box data (pipeline column fields)

✅ Contacts & organizations

✅ Tasks

✅ Call logs

✅ Meeting notes

✅ Pipeline newsfeed

The following cannot be exported:

❌ Email threads

See the Export a pipeline article for step-by-step instructions on running an export.

Once you have your export, you can import that data into a new pipeline. See Import data into Streak for full instructions.

If you only want to copy the layout of a pipeline — its stages, columns, and settings — without copying the box data, you can use Create Similar Pipeline from the left-hand sidebar in Gmail.

When do I not need a separate pipeline — and should use Saved Views instead?

If you want to slice your data by things like:

…you're describing a classic Saved View. These are filters and groupings, not fundamentally different datasets. One pipeline with a well-configured Saved View will serve you better than two pipelines.

What are signals that I genuinely do need separate pipelines?

The clearest signal is mismatched columns. If the data you'd track in pipeline A doesn't make sense to show in pipeline B — and vice versa — that's a strong indicator they represent different enough workflows to warrant their own pipelines. When the structure diverges, separate pipelines are the right call.

What are the downsides of multiple pipelines versus one pipeline with Saved Views?

One pipeline can be broken down into an unlimited number of segments using Saved Views. The reverse is not true — you cannot combine multiple separate pipelines into a single view.

For example, if you've split deals into separate pipelines by year, there's no way to then ask "show me all new deals across all years" or "show me all deals in a specific region" in one place. You'd have to check each pipeline individually. One pipeline can be broken down infinitely. Multiple pipelines cannot be recombined.