Remote.com Website Migration

The Client

Remote.com is an all-in-one HR and payroll platform that helps companies hire, manage, and pay teams across the globe.

Their website operates in 25+ languages, with content spanning marketing pages, a high-volume blog, product documentation, pricing, and resource hubs. The entire digital presence was built on HubSpot CMS.

The Challenge

Remote decided to move their website from HubSpot to Contentstack, a headless CMS better suited for their multi-language, composable content strategy.

The problem was that nobody could tell them what the journey would actually involve. The site had accumulated 65,000+ entries across 75 content types, over 166 modules, 45 database tables, and 25+ languages.

Components had been duplicated across teams. Similar modules existed in multiple slightly different versions. Over 20 internal stakeholders each owned different parts of one website.

What they needed was a plan, and validation that the move could be programmatic.

The Approach

Audit

Using a proprietary audit tooling, Smuves scanned the entire portal and produced a structured inventory of every content type, module, template, language, asset, and entry. The audit mapped relationships between components and pages, surfacing overlaps and redundancies that years of hypergrowth had obscured.

Analysis

The team reviewed all 166 modules with Remote's stakeholders and classified each one. Some were migrated as-is. Others were retired with documented replacements. The most complex group were modules that needed to be consolidated.

The analysis process identified overlaps, compared structures, and designed a single consolidated version for each in the new platform.

Architecture 

With a clear picture of what was worth keeping, the team designed how everything would live in Contentstack. This meant defining reusable field groups, setting up relational structures between content types, extracting shared elements like color schemes and call-to-action patterns into standalone components, and building an SEO framework applied consistently across all page rendering content types.

The localization strategy required particular care, mapping which content types had full, partial, or no language coverage.

Transformation 

Before any migration script could be written, content transformation rules were documented covering how data would change as it moved between platforms.

Migration

After all was planned the Smuves ETL was customized to programmatically extract HubSpot content, transform it, and load it into Contentstack. Without the need of a developer.

Pages, blogs, posts, authors, tags, assets, and HubDB tables became content types. Relationships were preserved like authors and tags assigned to to their respective blog posts. And assets linked via Contentstack ID removing any issues with missing visuals and media. Localized entries were created seamlessly in the background and without any extra steps. After all entries were made, we swept through all module and rich text links and connected them to entries.

The Result

With the content movement able to be done programmatically the Remote.com team could then focus on the next steps of building out their front end layer to complete their transition from a monolithic system to headless.