Emesent
From WordPress to Global CMS: How Emesent Turned Their Website from a Source of Friction into a Marketing Asset
Services Used
Project Manager
Project Location
Australia
Services Used
Solution
Website Migration & CMS
Project Manager
Project Location
Australia
Project Goals
Emesent builds autonomous drone platforms and LiDAR mapping solutions for the places humans can't safely go — underground mines, active construction sites, and emergency response zones. A CSIRO spinoff operating across seven language markets, their HubSpot CRM was central to their go-to-market operation. Their website sat completely outside it - on WordPress, managed by an external agency, disconnected from every contact record and attribution model the business depended on.
Their wants
01
A website their marketing team could update and publish without relying on an external agency
02
03
04
Their needs
01
02
03
Their existing client portal migrated and connected to HubSpot contact properties for the first time
04
A structured handover programme leaving the team fully independent at close of engagement
Identifying the problem
Emesent had invested heavily in HubSpot. Their contacts, pipeline, and deal data all lived there. And yet their website - every visit, every demo request, every resource download, sat on WordPress, completely cut off from all of it.
Every content update meant a ticket to an external agency - a wait and an invoice. Katie Koss, Head of Platforms, had used HubSpot CMS before and knew exactly what they were missing: "It just made no sense to keep the two separate when we rely so much on the integration between the two for all of our marketing operations."
Across seven language markets, the migration complexity compounded - inconsistent translations, fragmented workflows, duplicate form structures that would shatter CRM attribution if mishandled. The risk wasn't just downtime. It was lost SEO equity, broken lead tracking, and a multilingual content operation that would take months to untangle.
Scope of works
CMS Hub
-
Full site migration from WordPress to HubSpot CMS. Every page, blog post, resource, and file asset moved accurately and completely.
-
Rebuilt on drag-and-drop templates - marketing team publishes independently, no engineering required.
Content Hub
- Full content library structured within HubDB.
- Custom database-driven modules for product specs and resource libraries -complex technical content manageable by marketing without code.
CRM
-
Existing gated client portal migrated from a subdomain into HubSpot, connected to contact properties for the first time.
-
Access now controlled by CRM data automatically.
The Plan
- Phase 1 | Jul 2025
- Phase 2 | Aug–Oct 2025
- Phase 3 | Oct–Nov 2025
- Phase 4 | 20 Jan 2026
- Phase 5 | Jan–10 Feb 2026
Phase 1 | Jul 2025
-
Discovery and scoping
-
Site architecture mapped
-
Migration priorities confirmed
Phase 2 | Aug–Oct 2025
-
HubDB modules
-
Page templates
-
Weglot integration built pre-migration
Phase 3 | Oct–Nov 2025
-
Page-by-page migration
-
URL redirect mapping
-
Structured UAT with cross-functional team
Phase 4 | 20 Jan 2026
-
DNS cutover coordinated with Emesent IT
-
Zero downtime
Phase 5 | Jan–10 Feb 2026
- Language switcher finalised post-launch
- HubDB workshop delivered
- Full platform handover
The Strategy
- Redirect mapping as a first-class deliverable
- Single form across all languages
- Portal migrated, not rebuilt
- Training as the final deliverable
Redirect mapping as a first-class deliverable
The migration was the opportunity - not just to move, but to connect.
-
Every URL mapped and validated before go-live.
-
SEO equity preserved.
-
Organic traffic protected.
Single form across all languages
-
Duplicate forms per region would have fragmented CRM data.
-
One unified approach meant the migration made the CRM cleaner, not messier.
Portal migrated, not rebuilt
-
Connected the existing client portal to HubSpot contact properties during migration so CRM data controlled access automatically at launch.
Training as the final deliverable
-
The engagement didn't close until the team operated everything independently.
-
HubDB workshop and CMS enablement were the final milestone, not an after thought.
The Results
7
languages markets on one platform
0
downtime on DNS cutover
100%
on time and on budget
7 Language Markets. One Platform. Zero Content Loss. Every page, redirect, form, and resource migrated accurately across seven languages. CRM attribution intact from day one. The marketing team publishes globally from a single HubSpot dashboard - no agency, no tickets, no waiting.
Zero Downtime on DNS Cutover. The live switchover on 20 January 2026 was undetectable to the wider business. Stuart, Head of Marketing: "Nobody even noticed it happened. It just was there, done, working." Every redirect validated in real time. No broken links. No lost traffic.
100% On Time. On Budget. Five phases, multilingual build, cross-functional UAT, post-launch module additions. Delivered exactly as scoped.
The Impact
Surely something will go wrong eventually....? Nope. Nothing ever went wrong. We are so glad we chose Neighbourhood to handle our website migration project. Moving our site from another platform to HubSpot had the potential to be nerve-wracking and full of bugs, but our experience with Harry and the Neighbourhood team proved the complete opposite. They were efficient, professional, and delivered what they promised - on time and on budget. Neighbourhood will certainly be the go-to for our next HubSpot project.
Conclusion
Zero downtime. Zero content loss. SEO preserved. CRM connected. Seven languages. Five months. On time, on budget.
The agency dependency is gone. The team is independent. The data flows clean.
That's what a migration done right looks like.