Move a site to the app's theme
Rebuild pages from a Marketplace theme on the app-managed theme, and what stays behind.
The app installs its own Sprocket Rocket theme beside the Marketplace theme. Moving a site onto it is manual work, page by page. There is no automatic migration.
If you only need Module Builder on a site that is already built, you do not need to move anything. A shared asset folder adds Module Builder beside the Marketplace theme.
Why the app installs a separate theme
HubSpot locks the files installed by the Marketplace. You can adopt the Marketplace theme so Page Builder and Sprocket Rocket AI work on its pages, but the app cannot write to it, so it cannot manage, update, or back it up. A new installation is a separate Sprocket Rocket theme in your portal.
Connecting the app, adopting the Marketplace theme, and creating a new installation do not replace your Marketplace theme or change existing pages. Pages using the Marketplace theme continue to use it until you choose to move them. The app's updates and backups apply to its own installation, not the separate Marketplace theme.
Move existing pages to the app's theme
Theme settings, global content, and custom code from the Marketplace theme or its child theme do not transfer. Changing a page's template does not change the modules on it: they remain Marketplace modules, which Module Builder still cannot edit.
- Configure the new installation's theme settings, including colors, typography, and spacing.
- Set up its global header and footer.
- Review any custom CSS, modules, and templates in the old theme or child theme, and carry over the changes the new site needs.
- Change a page to a compatible template from the app-managed theme. Review its content, modules, forms, and mobile layout before publishing; a template change can alter module placements.
- Replace the Marketplace modules on the page with the app theme's equivalents so the page no longer depends on locked files.
- Repeat for the remaining pages and review any blog, system, or subscription templates still using the old theme.
Keep the Marketplace theme until every module is replaced
A page on the app's template still depends on the Marketplace theme until its modules are replaced. Uninstalling the theme before then deletes those modules and breaks the page. Keep any child theme while its parent is still in use.
Do I need a child theme?
No. Child themes are neither required nor recommended for app-managed installations. Use the app's module editing, file management, backups, and rollback workflows for that installation.
The child theme guide is for using a Marketplace theme without the app, when you need to customize its locked source files. You can edit page content and the theme's available settings in HubSpot without creating a child theme.