<?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: Downgrades when moving off legacy starter bundle to core seat pricing in Blog, Website &amp; Page Publishing</title>
    <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Downgrades-when-moving-off-legacy-starter-bundle-to-core-seat/m-p/1024087#M13133</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/704547"&gt;@rickl&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Hi - we have encountered an issue when transferring off of the legacy starter bundle to the new core seat starter pricing.&lt;/P&gt;
&lt;P&gt;We did this to access a single Sales Pro seat but discovered that the revised Content Core seat now had limited Landing pages (30 max from almost unlimited) and fewer web pages (from 50 down to 30).&lt;/P&gt;
&lt;P&gt;Our only option was to upgrade to a Content Professional or reduce the number of published or archived pages.&lt;/P&gt;
&lt;P&gt;Has anyone else encountered this issue?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I experienced this in the past when the operations hub came out and we lost access to custom code we developed and were locked out of the feature. Hubspot gave us the code back, but we had to disable the workflows. We ended up developing our own workarounds to move forward as we didn't budget for the operations hub at the time. Personally I wish these issues were flagged in these types of transitions because if a user will lose features, or pages of their website, they should be provided an avenue to remedy the situation before it results in errors or potentially in your case, SEO penalties for dead links/pages.&lt;/P&gt;</description>
    <pubDate>Thu, 08 Aug 2024 13:38:16 GMT</pubDate>
    <dc:creator>Ben_M</dc:creator>
    <dc:date>2024-08-08T13:38:16Z</dc:date>
    <item>
      <title>Downgrades when moving off legacy starter bundle to core seat pricing</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Downgrades-when-moving-off-legacy-starter-bundle-to-core-seat/m-p/1023885#M13128</link>
      <description>&lt;P&gt;Hi - we have encountered an issue when transferring off of the legacy starter bundle to the new core seat starter pricing.&lt;/P&gt;&lt;P&gt;We did this to access a single Sales Pro seat but discovered that the revised Content Core seat now had limited Landing pages (30 max from almost unlimited) and fewer web pages (from 50 down to 30).&lt;/P&gt;&lt;P&gt;Our only option was to upgrade to a Content Professional or reduce the number of published or archived pages.&lt;/P&gt;&lt;P&gt;Has anyone else encountered this issue?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Aug 2024 06:43:58 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Downgrades-when-moving-off-legacy-starter-bundle-to-core-seat/m-p/1023885#M13128</guid>
      <dc:creator>rickl</dc:creator>
      <dc:date>2024-08-08T06:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: Downgrades when moving off legacy starter bundle to core seat pricing</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Downgrades-when-moving-off-legacy-starter-bundle-to-core-seat/m-p/1024087#M13133</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/704547"&gt;@rickl&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Hi - we have encountered an issue when transferring off of the legacy starter bundle to the new core seat starter pricing.&lt;/P&gt;
&lt;P&gt;We did this to access a single Sales Pro seat but discovered that the revised Content Core seat now had limited Landing pages (30 max from almost unlimited) and fewer web pages (from 50 down to 30).&lt;/P&gt;
&lt;P&gt;Our only option was to upgrade to a Content Professional or reduce the number of published or archived pages.&lt;/P&gt;
&lt;P&gt;Has anyone else encountered this issue?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I experienced this in the past when the operations hub came out and we lost access to custom code we developed and were locked out of the feature. Hubspot gave us the code back, but we had to disable the workflows. We ended up developing our own workarounds to move forward as we didn't budget for the operations hub at the time. Personally I wish these issues were flagged in these types of transitions because if a user will lose features, or pages of their website, they should be provided an avenue to remedy the situation before it results in errors or potentially in your case, SEO penalties for dead links/pages.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Aug 2024 13:38:16 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Downgrades-when-moving-off-legacy-starter-bundle-to-core-seat/m-p/1024087#M13133</guid>
      <dc:creator>Ben_M</dc:creator>
      <dc:date>2024-08-08T13:38:16Z</dc:date>
    </item>
  </channel>
</rss>

