How TELUS Health Consolidated 335 Landing Pages and 1,705 Blog Posts Into One Multilingual HubSpot CMS

1. Hard-coded theme logic.

Site navigation, footers, and blog display logic lived inside theme files, outside the standard HubSpot content editor. Every routine content change required direct developer involvement, closing off self-service editing for the content team.

2. No multilingual blog grouping.

TELUS Health's Heartbeat Blog and Global Blog properties had no native structure linking a post to its language variants. Regional teams managed translated versions of the same post as separate, disconnected assets.

3. No structure for gated multilingual content.

Assets like the Mental Health Index report had no supporting object model for gated, language-specific delivery. Each new gated campaign was built manually from scratch, with no repeatable system to reuse.

4. Migration tooling limitations.

HubSpot's native asset migrator could not correctly transfer a subset of legacy forms due to field name and type mismatches between the old and new portals. Each affected form required manual rebuilding to preserve data integrity during the cutover.

5. Contractually fixed legacy pages.

Three legal and policy pages were required to remain on the legacy go.lifeworks.com domain even as the rest of the site moved to telushealth.com. The cutover needed a domain-splitting approach that kept those pages functional without folding them into the new architecture.

How Campaign Creators Rebuilt TELUS Health's Multilingual Content Architecture

Campaign Creators sequenced the engagement in phases: a Blog Migration Phase 2 covering both blog properties, followed by a Landing Page Migration covering 335 priority pages, followed by a Post-Migration Theme Cleanup Audit covering an additional 71 templates once the core cutover was verified stable.

Two Custom Objects for Language-Specific Gated Assets

Gated content had previously run through ad hoc forms, with no data model tying a gated asset to its own submissions. Campaign Creators built two new custom objects, Gated Content Files and Gated Content Form Submissions, to give TELUS Health a dedicated data model for language-specific gated assets. This decision means a new gated campaign in any language follows an established object structure going forward, not a one-off build each time.

Gated Assets Tied to Their Host Pages

Gated assets needed to connect directly to the blog and landing page content they supported, not sit as disconnected records checked by hand against the page delivering them. Campaign Creators connected the two new custom objects directly into the surrounding HubSpot CMS content model, so a gated asset and its host page reference the same underlying record. That connection is what lets a content editor manage a gated asset and its page as one unit, not two systems synced manually.

1,705 Posts Across 9 Languages, Blogs First

Blog content had to move as two batches of very different scale and structure at once, 504 posts across 9 languages on the Heartbeat Blog and 1,201 posts across 5 languages on the Global Blog, without breaking either property's existing search visibility mid-migration. Campaign Creators migrated both properties into HubSpot's native multilingual blog grouping, followed by an "as-is" rebuild of 335 priority landing and web pages with corrected metadata, SEO fields, and a new URL structure. Sequencing the blog migration ahead of the landing page rebuild let the team validate the new multilingual grouping model on a smaller, contained content set before applying the same approach at landing-page scale.

Separate Field Sets for Assets and Submissions

A single flat record could not separate a gated asset from each visitor's individual form submission, which would have made it impossible to report on either one without disentangling the other by hand. Campaign Creators defined distinct field sets for the two new objects, so each record type carries only the fields relevant to it, gated-asset metadata on one object and submission data on the other. That separation lets TELUS Health track a gated asset and its submissions independently, in any language, without redefining the distinction for each new campaign.

Content Edits Out of the Developer Queue

Publishing a routine update under the legacy structure meant filing a developer request regardless of how small the change was, from a single blog post edit to a sitewide footer link. Campaign Creators separated the two going forward: standard content changes now run through the content team's own HubSpot content editor, and only structural theme-level changes route to a developer. Day-to-day publishing volume no longer depends on developer availability.

Workflows Rebuilt for Multilingual Groupings

Both workflows tied to the legacy blog properties were built against a single-language structure and would have broken the moment posts moved into native multilingual groupings. Campaign Creators rebuilt both workflows to run correctly against the new multilingual post structure as part of the same migration. Neither workflow needs a separate rebuild each time a new language is added going forward.

Verified Redirects at 2,000+ Pages

A migration touching more than 2,000 combined blog posts and pages had no way to confirm redirect and URL integrity except checking pages individually, which would not hold up against a fixed go-live date. Campaign Creators ran systematic Screaming Frog crawls before and after cutover to verify redirects and URLs across the full migrated set. That gave the team a documented, page-by-page baseline for confirming go-live, not a spot-check.

Impact: A Content Architecture Built to Scale Without Rebuilding Again

TELUS Health's blog and landing page content now lives in one standardized HubSpot CMS architecture, not scattered across theme-level customizations only a developer could touch. Routine content work runs through the content team's own tools, with developer time reserved for structural changes, not day-to-day publishing. As TELUS Health adds new markets or languages, the same multilingual grouping model extends to them directly, without a separate redesign for each one.

Solve Multilingual Content Migration and CMS Consolidation With Campaign Creators

Global organizations that grow through acquisitions and regional expansion often end up with content scattered across inconsistent language variants and theme-level customizations that only a developer can touch. Every new market or language adds to that debt without a plan to resolve it.

Closing that gap requires a content architecture built on native multilingual grouping and a repeatable object model for gated content, sequenced so historical search value carries over, not traded away for speed.

Campaign Creators builds HubSpot CMS architectures that give global teams direct control over multilingual content, a governance-ready structure for gated assets, and a migration approach built to protect search value and historical content at scale.