Skip to main content

Importing and Exporting Pipelines

CustomerFlows supports pipeline CSV tools so you can:

  • download a template sheet for new pipeline setups
  • export an existing pipeline structure
  • upload a CSV to create or update pipelines

This is useful when you want to standardize stage structures across workspaces, clone a proven workflow, or keep a reusable pipeline template for a specific trade.

What The Pipeline CSV Contains​

Each row in the CSV represents one stage in one pipeline.

The template columns are:

ColumnMeaning
pipeline_idExisting pipeline ID, used to update a specific pipeline
pipeline_nameThe pipeline name
is_defaultWhether the pipeline should be the default
stage_nameThe stage label
positionThe stage order
is_closed_wonMarks a stage as closed-won
is_closed_lostMarks a stage as closed-lost

Download A Template Or Export A Pipeline​

In the app:

  1. Open Pipeline
  2. Use the Pipeline CSV tools panel
  3. Click Download template to start from a blank template sheet
  4. Click Export CSV to download the currently selected pipeline structure

Use the template when you are creating a new pipeline from scratch. Use export when you want to copy or edit a real pipeline that already works the way you want.

How Import Decides Whether To Create Or Update​

When you upload a pipeline CSV, CustomerFlows checks existing pipelines in this order:

  1. exact pipeline_id
  2. case-insensitive pipeline_name

If an existing pipeline matches, CustomerFlows updates it.

If nothing matches, CustomerFlows creates a new pipeline.

Practical rule:

  • keep pipeline_id when you want to update the current pipeline
  • change the pipeline name when you want to create a separate copy in the same workspace

Stage Update Behavior​

During import, CustomerFlows updates the stage order and stage status flags from the CSV.

If you change a stage name in the CSV, CustomerFlows treats that as the new stage definition. If the old stage no longer appears in the CSV:

  • it is removed if no deals still use it
  • it is kept at the end of the pipeline if deals still depend on it

This protects active deals from being stranded during a pipeline update.

Default Pipeline Rules​

Only one imported pipeline can be marked as default.

If your CSV marks a pipeline as default, CustomerFlows removes the default flag from the current default pipeline first. If more than one imported pipeline is marked default, the import is rejected.

Best Practices​

  • export the current pipeline before making structural edits
  • keep one clear default pipeline per workspace
  • use a new pipeline name if you want a second copy in the same workspace
  • review closed-won and closed-lost flags carefully before import
  • test with one pipeline first before bulk-importing several workflows

FAQ​

Can I export one pipeline or all pipelines? From the app, the CSV export follows the currently selected pipeline. Through the API, you can export a specific pipeline or all pipelines.

Can I copy a pipeline to another workspace? Yes. Export the pipeline CSV in one workspace, then import it into another. If the destination workspace already has a pipeline with the same name, rename the CSV pipeline first if you want a separate copy instead of an update.

Can I mark more than one imported pipeline as default? No. Only one imported pipeline can be marked default.

What happens to stages I remove from the CSV? Unused stages can be removed. Stages that still have deals attached are kept at the end until those deals are moved elsewhere.

Need help? Email support@customerflows.com or ask in r/CustomerFlows.