Moving a content-heavy website to HubSpot

A public IT company wanted to move its website from Gatsby and Contentful to HubSpot CMS. The work involved more than rebuilding the visible pages: blog content, images, old URLs and investor-relations feeds all had to be accounted for.

I worked as technical lead in a two-person agency team. My focus was the migration pipeline and investor-relations integration; my colleague worked on the modules, quality checks and client feedback. This was agency work, rather than a direct Klarhimmel commission.

Keep the content, change the platform

The existing site depended on several connected services. Moving to HubSpot meant creating a theme and a repeatable route for transferring content into the new system. The project combined HubL templates and modules, Tailwind CSS and shared design tokens.

The migration pipeline handled content extraction, asset upload and HubSpot API calls. It also prepared redirects and compared the new pages with the old site. Treating those steps as a pipeline made the migration work inspectable, rather than a sequence of manual copy-and-paste tasks.

Give investor relations its own attention

Press releases and filings were a distinct part of the work. A scheduled workflow synchronised press releases from Cision, while a separate module fetched SEC EDGAR filings for a table matched against the original site.

Those feeds needed to be considered alongside the website theme. A page can look finished while the information it depends on is still disconnected.

Make the work easier to review

A local preview tool rendered HubL templates without requiring an upload to HubSpot for every change. That gave the team a way to iterate on the theme and inspect pages locally.

The repository also held module documentation, a phased roadmap and comparison checks. Coding agents supported the implementation, with the team responsible for the technical choices and review.

What the project produced

The project produced a custom HubSpot theme with reusable templates and modules, a content and asset migration pipeline, redirect generation with old-to-new page comparisons, press-release synchronisation with a filings module, and a local preview tool with project documentation.

These are the documented project deliverables. This case study does not claim a verified production launch, traffic improvement or completed transfer of every image reference.

What I learned

Content migration needs one clear source of truth. Edits made directly in the hosted theme can drift from the repository; asset uploads and rewriting the references to those assets should be treated as one operation.

The practical lesson is to review the migration as a connected system: content, URLs, templates, assets and feeds. The new page design is only one part of that system.

The illustration is conceptual artwork, not a screenshot or disclosure of the client's website records.