<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Substructure to pipeline or automations to move between pipelines in Sales Integrations</title>
    <link>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952833#M6729</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/732822"&gt;@JWDickens&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What I typically do with this type of automation is mark the record closed in the current pipeline with automation and then use the "create record" function to create a new deal in the new pipeline.&amp;nbsp; This is super helpful if you are using a pipeline for qualifying/SDR activity because you can count a "Closed Won" deal in the qualifying pipeline as a win for your SDR's.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With that said, you should be able to Set the Property Value "Deal Pipeline and Stage" with a workflow aciton like this, if that is what you prefer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-04-01 - 14_11_06 - Unnamed workflow - 2024-04-01 18_10_21 GMT+0000 _ HubSpot.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/114255iD0736C3EE404768B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="2024-04-01 - 14_11_06 - Unnamed workflow - 2024-04-01 18_10_21 GMT+0000 _ HubSpot.png" alt="2024-04-01 - 14_11_06 - Unnamed workflow - 2024-04-01 18_10_21 GMT+0000 _ HubSpot.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; This will move the deal to the desired pipeline at the stage selected.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Apr 2024 18:12:29 GMT</pubDate>
    <dc:creator>trevordjones</dc:creator>
    <dc:date>2024-04-01T18:12:29Z</dc:date>
    <item>
      <title>Substructure to pipeline or automations to move between pipelines</title>
      <link>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952826#M6728</link>
      <description>&lt;P&gt;Hey all, Kinda new to Hubspot so hope this is not a silly question.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a pipeline process that at points along the way there is a subprocess that needs to be accounted for. My thought was to create another pipeline and have an automation move the card from one pipeline to another until that process is completed when it can be then moved back to the original pipeline. I have been tinkering with things for a few hours now though and can't seem to make that work. I could stuff it all into one pipeline but that seems to get unmanageable and long and wanted to use this process to both simplify and notify as these subtasks/pipelines may have a different owner.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hopefully that makes sense and it's something that can be done but I'm at a loss so far. Any advice or direction would be greatly appreciated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 17:56:15 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952826#M6728</guid>
      <dc:creator>JWDickens</dc:creator>
      <dc:date>2024-04-01T17:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: Substructure to pipeline or automations to move between pipelines</title>
      <link>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952833#M6729</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/732822"&gt;@JWDickens&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What I typically do with this type of automation is mark the record closed in the current pipeline with automation and then use the "create record" function to create a new deal in the new pipeline.&amp;nbsp; This is super helpful if you are using a pipeline for qualifying/SDR activity because you can count a "Closed Won" deal in the qualifying pipeline as a win for your SDR's.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With that said, you should be able to Set the Property Value "Deal Pipeline and Stage" with a workflow aciton like this, if that is what you prefer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-04-01 - 14_11_06 - Unnamed workflow - 2024-04-01 18_10_21 GMT+0000 _ HubSpot.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/114255iD0736C3EE404768B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="2024-04-01 - 14_11_06 - Unnamed workflow - 2024-04-01 18_10_21 GMT+0000 _ HubSpot.png" alt="2024-04-01 - 14_11_06 - Unnamed workflow - 2024-04-01 18_10_21 GMT+0000 _ HubSpot.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; This will move the deal to the desired pipeline at the stage selected.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 18:12:29 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952833#M6729</guid>
      <dc:creator>trevordjones</dc:creator>
      <dc:date>2024-04-01T18:12:29Z</dc:date>
    </item>
    <item>
      <title>Re: Substructure to pipeline or automations to move between pipelines</title>
      <link>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952868#M6730</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/9374"&gt;@trevordjones&lt;/a&gt;&amp;nbsp;thank you for the reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it sounds like with this approach it would be more like a stair step down approach where I would have basicly 2 or 3 pipelines and as it closes in one it opens in the next and so on. Would that be accurate? Although I would like to have one main pipeline and reintroduce cards back to the main that may not be possible.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 18:51:40 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952868#M6730</guid>
      <dc:creator>JWDickens</dc:creator>
      <dc:date>2024-04-01T18:51:40Z</dc:date>
    </item>
    <item>
      <title>Re: Substructure to pipeline or automations to move between pipelines</title>
      <link>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952872#M6731</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/732822"&gt;@JWDickens&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To be clear, I proposed two options in my reply. The first would have been the stair step you describe, while the second would move the same card from one pipeline to the next.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:00:01 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Integrations/Substructure-to-pipeline-or-automations-to-move-between/m-p/952872#M6731</guid>
      <dc:creator>trevordjones</dc:creator>
      <dc:date>2024-04-01T19:00:01Z</dc:date>
    </item>
  </channel>
</rss>

