Hi all, we are looking to move Hubspot themes to a more modern prebuilt theme with easier responsive design capabilities and a new navigation.
If we were to migrate every page we currently have built, how does that affect CTA's, Workflows, Forms, and more that is already set up. Is the transition strictly visual (i.e the funcitonality of the current webpages stays the same) or would we need to redo certain modules and workflows.
@SEsposito4 I'm happy to help with your questions about transitioning to a marketplace theme.
When you download a marketplace theme, there is an option to change the template used on existing pages, however this won't actually change the modules or content from your current theme to the new theme.
The only way to migrate from one theme to another properly is to rebuild each of your existing pages with the new theme and the available modules in that theme (referencing your existing content of course).
The best way to do this is with Content Staging (requires Content Hub Pro+) because you can build a blank page with a template from the new theme based on an existing page (the URL, meta data, traffic analytics, etc. are all retained) but the content would have to be manually populated into the new template selected.
As far as forms, this means that you'd be selecting your existing forms in the forms module for the new theme, but the form in the background would still be the same (unless you opt to create new ones).
The same is true with CTAs, if you select existing CTAs in the new theme's modules then they would retain the same configuration/analytics/etc.
For workflows, that means that if the trigger is a form, CTA, or page URL, then they will all work the same. If you create new URLs or change any of the forms or CTAs, you would need to verify the workflows still trigger properly.
I've migrated hundreds of websites from other platforms to marketplace themes and also from one theme to another, there's no "quick" way about it, but if you do it properly you'll be happiest in the long run and you won't lose all your analytics data.
Here are a few other tips/suggestions:
1 - If you have Content Hub Pro, I recommend paying for a Pro theme - personally I love working with POWER Pro because it has a lot of flexibility (especially the Mega Menu, Advanced Footer, and Bento Grid module) and it's also coded in a way that makes it very easy to customize, plus it's optimized for performance and responsiveness beyond what many themes have done. [full disclosure I worked with them a few years ago].
There are a lot of really good pro themes though and you can't go wrong as long as you focus on the functionality you need vs design alone - it's so easy to make changes with theme settings and a little CSS for design than it is to add functionality if the theme doesn't have the modules you need.
2 - Once you purchase the theme, cancel out of the prompt to configure theme settings or start building pages - instead, create a child theme first (this is power documentation, but it is the same steps for all themes).
A child theme will inherit everything from the marketplace theme, but it gives you a child.css and child.js file where you can extend capabilities. Don't overwrite existing files unless you really have to, happy to share more on that if you have questions.
3 - configure your theme settings to match your brand (colors, fonts, button styles), but build out your pages before you start using the overwrites for specific elements. A lot of themes will have you set global colors and then allow you to change colors for various elements, it's a lot easier to fine tune a theme once you have content than trying to perfect it out of the gate.
All draft pages are visible in the theme settings configurator, which makes it easy to see your changes across multiple pages without publishing.
Same is true for adding CSS - hold off on customizations until you have your pages migrated using the defaults, then decide what you need to overwrite or modify/enhance.
4 - regardless of the theme you choose, review their available documentation first (esp. getting started guides). It will save you a lot of time in the long run.
I'm happy to help further if you have other questions! Best of luck on your migration 🙂
If my reply answered your question please mark it as a solution to make it easier for others to find.
@SEsposito4 I'm happy to help with your questions about transitioning to a marketplace theme.
When you download a marketplace theme, there is an option to change the template used on existing pages, however this won't actually change the modules or content from your current theme to the new theme.
The only way to migrate from one theme to another properly is to rebuild each of your existing pages with the new theme and the available modules in that theme (referencing your existing content of course).
The best way to do this is with Content Staging (requires Content Hub Pro+) because you can build a blank page with a template from the new theme based on an existing page (the URL, meta data, traffic analytics, etc. are all retained) but the content would have to be manually populated into the new template selected.
As far as forms, this means that you'd be selecting your existing forms in the forms module for the new theme, but the form in the background would still be the same (unless you opt to create new ones).
The same is true with CTAs, if you select existing CTAs in the new theme's modules then they would retain the same configuration/analytics/etc.
For workflows, that means that if the trigger is a form, CTA, or page URL, then they will all work the same. If you create new URLs or change any of the forms or CTAs, you would need to verify the workflows still trigger properly.
I've migrated hundreds of websites from other platforms to marketplace themes and also from one theme to another, there's no "quick" way about it, but if you do it properly you'll be happiest in the long run and you won't lose all your analytics data.
Here are a few other tips/suggestions:
1 - If you have Content Hub Pro, I recommend paying for a Pro theme - personally I love working with POWER Pro because it has a lot of flexibility (especially the Mega Menu, Advanced Footer, and Bento Grid module) and it's also coded in a way that makes it very easy to customize, plus it's optimized for performance and responsiveness beyond what many themes have done. [full disclosure I worked with them a few years ago].
There are a lot of really good pro themes though and you can't go wrong as long as you focus on the functionality you need vs design alone - it's so easy to make changes with theme settings and a little CSS for design than it is to add functionality if the theme doesn't have the modules you need.
2 - Once you purchase the theme, cancel out of the prompt to configure theme settings or start building pages - instead, create a child theme first (this is power documentation, but it is the same steps for all themes).
A child theme will inherit everything from the marketplace theme, but it gives you a child.css and child.js file where you can extend capabilities. Don't overwrite existing files unless you really have to, happy to share more on that if you have questions.
3 - configure your theme settings to match your brand (colors, fonts, button styles), but build out your pages before you start using the overwrites for specific elements. A lot of themes will have you set global colors and then allow you to change colors for various elements, it's a lot easier to fine tune a theme once you have content than trying to perfect it out of the gate.
All draft pages are visible in the theme settings configurator, which makes it easy to see your changes across multiple pages without publishing.
Same is true for adding CSS - hold off on customizations until you have your pages migrated using the defaults, then decide what you need to overwrite or modify/enhance.
4 - regardless of the theme you choose, review their available documentation first (esp. getting started guides). It will save you a lot of time in the long run.
I'm happy to help further if you have other questions! Best of luck on your migration 🙂
If my reply answered your question please mark it as a solution to make it easier for others to find.
you're welcome @SEsposito4 - by "legacy", I assume you're referring to the forms not part of the new multi-step forms (previously in beta) and also the previous CTAs before pop-up CTAs were an option.
For forms, there is no issue, both should be supported - all themes should support the legacy forms, but some might not have the new functionality for pop-ups. Maybe a really new theme only has the new forms and not legacy, but you'd have to ask the theme developer to confirm (they all have contact info in the listing).
For CTAs, this really depends on when the theme was developed and if it's been updated. I know Power Pro supports legacy and new, but the legacy CTAs are being sunset - it was originally 2023, but now it's Q1 2025. You may want to review the legacy CTA sunset info here. Some new themes may not have legacy support since it was announced early on that they would be sunset.
It's probably helpful to note that CTAs previously had a lot of styling and if you used them to look like buttons on your website, you'll likely want to migrate to new CTAs at the same time as migrating to the new theme.
Most themes used the old legacy CTAs with no styling and allowed the theme button styles to be applied, adding styling to the CTAs caused CSS conflicts and other issues.
It's just my two cents, but if you're migrating to a new theme, it might be worth considering migrating CTAs (especially because of the sunset) and possibly forms (as I'm not sure when those will be sunset).
It would require more work to rebuild workflows, but you should have time to create clones of your workflows to reflect the new forms/CTAs as you build out the new site. As long as you have a very solid naming convention for all the new assets, it will be easy to cleanup after the launch.
If my reply answered your question please mark it as a solution to make it easier for others to find.