How to create a custom pipeline in HubSpot

To create a custom pipeline in HubSpot, go to the right object’s settings, create a new pipeline, name it, and then add the stages your team uses. When you’re done, the pipeline should appear in that object’s pipeline dropdown and be available on new records. If you don’t see it, the most common cause is that you were in the wrong object settings area or the changes weren’t saved.

What you need before you start

Before you create anything, make sure you can edit settings for the object you want to use, such as deals, tickets, or another HubSpot object that supports pipelines.

You also need to know which object the pipeline belongs to. A deal pipeline is not the same as a ticket pipeline, and HubSpot keeps those separate.

• Access to the relevant settings area
• The object type you want to set up
• A clear stage flow for how your team works

Create the custom pipeline

1. Open HubSpot and go to the settings area.

2. Find the pipeline settings for the object you want to change. In most accounts, that means going to the object’s settings section and looking for a Pipelines or similar option.

3. Choose the object type first if HubSpot asks you to. For example, select deals if you are creating a sales pipeline, or tickets if you are creating a support pipeline.

4. Click the option to create a new pipeline.

5. Enter a clear name for the pipeline that matches how your team will use it, such as a team name, region, or process name.

6. Save the new pipeline.

After you save, HubSpot should show the new pipeline in the pipeline settings for that object. If you opened the wrong object type, stop there and switch before you make stage changes, since the stages will belong to that object only.

Set up the stages your team will use

Once the pipeline exists, edit its stages so they match the real path a deal or ticket follows in your process.

1. Open the new pipeline in the stage editor.

2. Add the stages you need. Keep the names short and clear so anyone on the team can read them quickly.

3. Rename any default stage that does not fit your process.

4. Reorder the stages so they follow the actual order work moves through, from first step to final step.

5. Remove stages you will not use, if HubSpot allows removal in that pipeline setup.

6. Save your changes.

A practical way to check the order is to read the stage list from top to bottom and ask whether a new record would move through them naturally. For example, if a deal must be qualified before a proposal is sent, those stages should appear in that order.

Check that it saved correctly

After saving, confirm that the pipeline appears where you expect it to appear for that object.

You should usually be able to find it in the pipeline dropdown for the object you just configured. For example, if you made a deal pipeline, it should show up in the deal pipeline selector and be available when you create or edit a deal.

Open a new record for that object and look for the pipeline field or dropdown. Select the new pipeline and make sure the stages you created are available.

If the new pipeline appears and the stage list matches what you set, the setup worked.

Common snags to check if it does not show up

If the pipeline does not appear where you expected, start with the most common causes.

• You edited the wrong object type. A deal pipeline will not appear in ticket settings, and the reverse is true as well.
• You did not save the pipeline or the stage changes.
• Your permissions do not allow you to view or edit that settings area.
• You are looking in the wrong place for the object, such as a record view that does not show the pipeline field by default.
• The account has custom setup or limited access that changes where the pipeline appears.

If you can see the pipeline in settings but not on a record, check the record layout and the object’s property or field configuration. If the pipeline is missing from settings too, go back and confirm you were in the right object area before creating it.

When something still looks off, fix the object selection, permissions, or save issue first, then check again before you add more stages or change an existing pipeline.