<?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: Problem with the workflow migration process requested by HubSpot before January 8 in &amp;#128172 RevOps Discussions</title>
    <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390439#M236</link>
    <description>&lt;P&gt;Hello Louis,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think you are referring to HubSpot workflow release from November 2019 below:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.hubspot.com/product-updates/a-new-engine-for-your-workflows" target="_blank"&gt;https://www.hubspot.com/product-updates/a-new-engine-for-your-workflows&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In this documentation HubSpot was giving some rules on how they would proceed with the migration and how you can manage it manually if you were not qualifying for the automatic migration. Most of the actual HubSpot customers and all new Marketing Pro/Enterprise users are now automaticaly migrated. You should not have that many customers with this problem.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you know how many of your customer received this email?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my case, only one received it out of more than 200 customers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this doc helps a bit!&lt;/P&gt;
&lt;P&gt;Always here to help if neede!&lt;/P&gt;</description>
    <pubDate>Wed, 02 Dec 2020 04:14:13 GMT</pubDate>
    <dc:creator>EvensSheehy</dc:creator>
    <dc:date>2020-12-02T04:14:13Z</dc:date>
    <item>
      <title>Problem with the workflow migration process requested by HubSpot before January 8</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390426#M235</link>
      <description>&lt;DIV&gt;If you use HubSpot workflows for several years, maybe you have received an email from HubSpot with this subject line:&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;STRONG style="color: inherit; font-size: 24px;"&gt;&lt;FONT face="arial black,avant garde" size="4"&gt;[Action Required] One or more of your workflows need to be updated by January 8&lt;/FONT&gt;&lt;/STRONG&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
I discovered a quite big problem with the Workflow migration process sent to all impacted customers.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;The problem is two-fold:&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;1- When cloning workflows, nothing tells users to check if their workflows are using "Enroll in another workflow" actions. If they do, they need to be changed manually to the new version of the Workflow. If not it will end up in errors. This is the less important problem because this could be caught&amp;nbsp;with the "Workflows with errors" tab later.&lt;/DIV&gt;
&lt;DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;2- The following is way more important. If your Lists, Workflows goals or Workflows enrollment criteria use Workflows actions to include or exclude records, nothing of this will continue to work after cloning your workflows. The worst part is that there is no filter you can use to sort out impacted Lists or Workflows. You need to check them one by one.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;
&lt;DIV&gt;
&lt;DIV id="tinyMceEditorlouischausse_1" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I think HubSpot Customers should be aware of this while doing their migration.&lt;/DIV&gt;</description>
      <pubDate>Wed, 02 Dec 2020 02:39:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390426#M235</guid>
      <dc:creator>louischausse</dc:creator>
      <dc:date>2020-12-02T02:39:43Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with the workflow migration process requested by HubSpot before January 8</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390439#M236</link>
      <description>&lt;P&gt;Hello Louis,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think you are referring to HubSpot workflow release from November 2019 below:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.hubspot.com/product-updates/a-new-engine-for-your-workflows" target="_blank"&gt;https://www.hubspot.com/product-updates/a-new-engine-for-your-workflows&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In this documentation HubSpot was giving some rules on how they would proceed with the migration and how you can manage it manually if you were not qualifying for the automatic migration. Most of the actual HubSpot customers and all new Marketing Pro/Enterprise users are now automaticaly migrated. You should not have that many customers with this problem.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you know how many of your customer received this email?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my case, only one received it out of more than 200 customers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this doc helps a bit!&lt;/P&gt;
&lt;P&gt;Always here to help if neede!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 04:14:13 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390439#M236</guid>
      <dc:creator>EvensSheehy</dc:creator>
      <dc:date>2020-12-02T04:14:13Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with the workflow migration process requested by HubSpot before January 8</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390523#M237</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/92437"&gt;@EvensSheehy&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Not all of our customers received it, but still... and since there is no easy way to flag impacted lists and workflow for the problems I pointed out, I preferred to let know the community. If you follow the manual migration process suggested by HubSpot, users may not realize that and hand up with many broken processes since lists are used in everything (dashboards, workflows, goals, etc.)&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 11:07:19 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390523#M237</guid>
      <dc:creator>louischausse</dc:creator>
      <dc:date>2020-12-02T11:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with the workflow migration process requested by HubSpot before January 8</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390555#M238</link>
      <description>&lt;P&gt;You're right Louis. I think it's better to prevent that to have to repair!&lt;/P&gt;
&lt;P&gt;I'm voting up!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 13:24:29 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Problem-with-the-workflow-migration-process-requested-by-HubSpot/m-p/390555#M238</guid>
      <dc:creator>EvensSheehy</dc:creator>
      <dc:date>2020-12-02T13:24:29Z</dc:date>
    </item>
  </channel>
</rss>

