Culture Biosciences already had a website they liked. The problem was the CMS behind it.
We migrated their existing Webflow website into HubSpot Content Hub, preserving the existing design while rebuilding the underlying pages, templates, resources, navigation, animations, and functionality for HubSpot.
Culture Biosciences wanted to move from Webflow to HubSpot without redesigning their website.
We recreated the site inside HubSpot as closely as possible, giving their marketing team a CMS they preferred while maintaining the existing look, content, functionality, and SEO foundation.
Project highlights:
This wasn't a redesign project.
Culture's existing website already had the visual direction they wanted, but their marketing team was frustrated with Webflow and wanted to manage the site inside HubSpot instead.
We had also worked with Brian, Culture's marketing lead, on websites at previous companies. He was already familiar with HubSpot and brought us in to handle the migration.
The goal was simple:
Keep the website. Replace the CMS.
Rather than introducing a new design system, we recreated Culture's existing site inside HubSpot as closely as possible.
We used the Sprocket Rocket Pro theme as the foundation, then customized modules, styling, spacing, typography, and functionality to reproduce the existing Webflow experience.
That included rebuilding:
The finished HubSpot site intentionally looks very similar to the original Webflow site.
That was the point.
Culture also had a substantial resource library spread across several content types.
As part of the migration, we consolidated the primary resource types into a more manageable HubSpot structure:
Press releases and product updates were folded into the broader Announcements category, simplifying the content structure while working within HubSpot Content Hub Starter.
The result is a centralized resource center that Culture can continue managing and expanding inside HubSpot.
Changing CMS platforms can create SEO issues if URLs, metadata, content, and redirects aren't handled carefully.
As part of the Webflow-to-HubSpot migration, we worked to preserve the site's existing search foundation by maintaining:
The rebuilt site was also QA'd across desktop and mobile before launch.
There wasn't supposed to be a dramatic before-and-after reveal with this project.
Culture already had the website they wanted visually. What they needed was a better platform for the team managing it.
We moved the site from Webflow to HubSpot while maintaining its existing design and functionality, giving Culture a HubSpot foundation they can continue building on.
For a CMS migration like this, that's the goal: minimal disruption for website visitors and a meaningful improvement for the people working behind the scenes.
You don't necessarily need to redesign your website just because you're changing platforms.
Inbound Design Partners helps marketing teams migrate existing websites into HubSpot, whether that means a close 1:1 rebuild or using the migration as an opportunity to improve design, performance, structure, and the editing experience.
Talk to us about a HubSpot migration →
Yes. A Webflow website can be recreated inside HubSpot while preserving the existing design, content, responsive layouts, and much of its functionality. Custom Webflow components may need to be rebuilt using HubSpot modules, templates, CSS, and JavaScript.
A properly managed migration can preserve the site's existing SEO foundation. URLs, metadata, headings, alt text, internal links, and redirects should all be reviewed as part of the migration.
For companies already using HubSpot, moving the website into Content Hub can bring website management, forms, CRM data, marketing tools, analytics, and content publishing into the same platform. The right CMS depends largely on how the marketing team wants to manage the site.
Yes. An existing Webflow design can be rebuilt closely inside HubSpot without requiring a full redesign. The exact approach depends on the complexity of the original site, but HubSpot themes, custom modules, CSS, and JavaScript can be used to reproduce existing layouts, interactions, and responsive behavior.
Yes, in many cases. Animations, sticky navigation, sliders, and other interactive elements can be recreated in HubSpot using custom CSS and JavaScript. More complex Webflow-specific interactions may need to be rebuilt rather than directly transferred.
Yes. Blog posts, case studies, white papers, and other resource content can be moved from Webflow into HubSpot. Depending on how the content is structured in Webflow, some content can be imported while other elements may require manual migration or cleanup.