Skip to main content
Meticulosity Global

Platform Migration

WordPress to HubSpot Migration: A Step-by-Step Guide for Bilingual Sites


How to run a WordPress to HubSpot migration when the site is bilingual: the residency answer, the redirect map, RTL templates, and what an import overwrites.

By Dr. Ahmed MouradyUpdated August 12, 20269 min read
A minimalist desk setup with a sleek, silver laptop, an open notebook with neatly organized pages, and a simple, white coffee cup on the edge of the desk.

Key Takeaways

  • The order is fixed and expensive to reverse: settle the data-residency answer, then the field mapping, then the record import, then the redirects, in that sequence.
  • HubSpot still has no in-region data hosting for the UAE or Saudi Arabia: the five available regions are US East, US West, Canada, Australia, and the EU in Germany, and Middle East and Africa signups default to the EU, which no later migration can change because HubSpot only migrates data out of US East.
  • Bring contacts and companies over in one multiple-object import: while the Create and associate companies with contacts setting is on, a contact import invents company records from email domains, and a multiple-object import carrying its own associations is exempt from that setting.
  • Upload the native .xlsx rather than exporting to CSV: HubSpot requires UTF-8 whenever a file carries foreign language characters, which Arabic always does, and uploading the file HubSpot already accepts keeps the encoding question from arising at all.
  • Right-to-left layout comes from the dir attribute in the theme's base template, not the page's language tag, so a page can be correctly tagged Arabic and still render left to right.

Migrating your website to a new platform is a significant decision that can impact your online presence, search engine optimization (SEO), and user experience. On a WordPress to HubSpot migration here, two of those decisions are settled before a single page moves: where the data will be hosted, and what your redirect map does with Arabic URLs.

HubSpot, known for its Inbound Marketing, sales, and service software, runs websites on Content Hub (formerly CMS Hub), on the same Smart CRM as the rest of the platform. This guide walks through the migration in the order the work has to happen, which is not the order a feature list suggests.

Step 1: Planning and preparation

Assess your current website

Start by auditing your existing website to understand what works well and what needs improvement. Consider your site's structure, content, SEO performance, and any custom functionality. This assessment will help you identify what to replicate, enhance, or redesign during the migration.

Two inventories come out of it and both get used later: every URL that has to keep resolving, and every field that has to land somewhere in the CRM.

Answer the residency question before the field mapping

Put residency in that same audit: the compliance reviewer reads the migration plan you submit, not a working demo of the new site, so an unanswered residency line in that plan is what stalls the project before a page moves. Which regime you are answering under depends on your trade licence: a Dubai company registered inside the DIFC answers to DIFC Data Protection Law No. 5 of 2020, one inside ADGM to the ADGM Data Protection Regulations 2021, and both are separate from the federal UAE personal data protection law.

HubSpot's side of the answer is a matter of record. Its regional data centers are US East, US West, Canada, Australia, and the EU in Germany, so there is no in-region hosting for the UAE or Saudi Arabia. The region is assigned by IP geolocation at signup rather than chosen, and signups from the Middle East and Africa have defaulted to the EU region since 19 July 2021. Be blunt with the compliance reviewer about what that leaves you: HubSpot offers a move to another regional data center only out of its US East data center, and only where the data is already hosted in the United States, so migration back to US East, or between two non-US regions, is not on offer and a portal already assigned to the EU cannot be moved. The residency answer is therefore inherited at signup and settled there, which puts it in the compliance conversation rather than in a later migration plan. Confirm which region your portal already sits in before anyone writes the field mapping, not after.

Write it for the room rather than for your sponsor: Gartner's 2025 B2B buyer survey found technology buying groups now range from 5 to 16 people across as many as four functions, and the person who forwards your migration plan to legal is rarely the person who picked the platform.

Set migration goals

Define clear objectives for your migration. Whether it's improving your website's user experience, enhancing SEO, or streamlining content management, having specific goals will guide the migration process and allow you to measure their success at a later date. If bilingual is one of them, name it now: it changes the theme decision in step 2, not the content calendar.

Frame those goals against the mandate your sponsor already reports on. Dubai's D33 economic agenda targets generating $27 billion a year through digital transformation projects, per Dubai Chambers. That target is a reason to test a digital-transformation framing with your sponsor: it plausibly travels further through an approval chain than a redesign framing would, though the source confirms only the funding target, not how any specific project gets labelled internally. Our HubSpot vs. WordPress comparison covers what you gain and give up on the platform itself.

Step 2: Content, data, and design

Move the content, then the records

Start by transferring your essential website content, including text, images, and videos. Content Hub imports content and gives each page its own SEO recommendations.

The records are where a migration does damage that is slow and expensive to unpick, so run them like this:

  • One multiple-object import, not two sequenced ones. Check Settings > Data Management > Objects > Companies first: while "Create and associate companies with contacts" is on, a contact import creates a company record from each contact's email domain. HubSpot documents a multiple-object import as exempt from that setting, so an import carrying its own contact-to-company associations lands both without inventing companies alongside them.
  • Know what the domain column will and will not do. Company imports deduplicate on Record ID, then domain name, but a Gulf group running every subsidiary on one parent domain does not land as one record: HubSpot creates a company for each unique domain, subdomains included. The trap is that where several companies share a domain value, contacts on it are automatically associated with only one, with no way to select which, so those associations get repaired by hand afterwards.
  • Map the name columns by hand. Arabic personal names do not split reliably on the first space, so a legacy full-name column mapped straight into First name and Last name mislabels a large share of a Gulf list, and the error is invisible to a reviewer working in English.

Upload the native .xlsx rather than exporting it to CSV on the way. HubSpot accepts .csv, .xlsx, and .xls, and asks for UTF-8 only when the file includes foreign language characters, which Arabic content always does. That conditional is the whole of what HubSpot publishes here: it documents the requirement and not the failure, so there is no stated error, no warning and no rule about what an import does with a file that misses it. What practitioners report, and what to plan around rather than cite, is Arabic coming back as question marks after a round trip through a spreadsheet CSV export, discovered on the record long after the mapping was approved. Excel does expose CSV and UTF8 CSV as two separate save formats, which is the only corroboration we can point at. Uploading the .xlsx HubSpot already accepts costs nothing and removes the question from the migration.

Design for both directions before you choose a theme

With HubSpot, you can choose from pre-built website themes that are optimized for conversion and mobile responsiveness, or create a custom design that is unique to your business. If the site will carry Arabic, a migration is the one moment when text direction is free to decide, because the theme is the thing being replaced anyway. Our own research on MENA CRM buyers finds 64% name right-to-left formatting as a condition of a platform being usable at all, so the alternative is rebuilding the base template of a theme you have just finished migrating a site onto. The supply side is the same shape: Arabic is the content language of just 0.6% of the websites whose language W3Techs tracks.

Right to left comes from the dir attribute in the theme's base template, not from the page's language setting. Selecting Arabic in a multi-language page group changes the language tag and the switcher and leaves the layout running left to right, so a page can be correctly tagged Arabic and still be laid out backwards.

A mirrored left-to-right theme then breaks wherever left and right are hardcoded: icon padding, field alignment, breadcrumb chevrons, carousels, and anything absolutely positioned. Logical properties such as margin-inline-start and padding-inline-end are what let one theme serve both directions instead of two themes drifting apart release by release. Working with a certified partner agency can help you build that theme rather than inheriting an out-of-the-box one.

Step 3: Technical setup and customization

Domain setup and the redirect map

Connect your existing domain to HubSpot to maintain your brand's continuity and SEO ranking. HubSpot's technical support, or a partner who runs HubSpot migrations, can guide you through the cutover.

The redirect map is where a bilingual site loses traffic quietly, and two gates decide whether HubSpot's own redirect tool is available to you while it matters. The tool needs Marketing Hub Professional or Enterprise, Service Hub Professional or Enterprise, or Content Hub at Starter and above, so a portal running Marketing Hub Starter has no redirect tool to reach for at all. And URL redirects only work for domains connected to and hosted in HubSpot: for as long as the Arabic half of the site is still served from the old host, HubSpot will not receive those requests, so the redirects covering it have to be configured on that host and retired once the domain moves. Plan the map as two lists split by where the domain currently lives, not one list to paste in on cutover day.

Where the tool does apply, it percent-encodes special characters typed into its from and to fields, so a redirect entered there in decoded Arabic is encoded consistently. The risk sits one step earlier, in the map you bring with you: a legacy CMS export or spreadsheet that mixes encoded and decoded Arabic paths carries that mismatch straight through if it never passes through HubSpot's own encoding step, and nothing in the redirect report would flag it. Test the Arabic paths by requesting them, not by reading the report.

Then pick the cutover date against two calendars. Eid dates are confirmed by moon sighting and are commonly announced only days in advance, so the exact working days of a launch week are not known when the quarter's plan is signed, and the plan has to name which steps move with the announcement and which are fixed.

Integrate and customize features

Leverage HubSpot's integrations and APIs to add any custom functionality or connect your website with other tools essential to your business.

Step 4: Testing and optimization

Test your website

Before going live, thoroughly test your new HubSpot website. Check for broken links, mobile responsiveness, loading times, and SEO performance. This step is crucial to ensure a smooth user experience.

The Arabic pages need one check no tool runs for you. Latin text and digits inside an Arabic sentence are bidirectionally neutral, so a phone number, an English product name, or a trailing bracket at the end of an Arabic line renders in the wrong position unless it is isolated. HubSpot's Website Grader will not catch it either: it scores performance, mobile readiness, SEO, and security, so a clean grade on a bilingual site is a statement about the English half of it.

Optimize for SEO and performance

Use HubSpot's SEO tools to optimize your pages for search engines. The platform offers recommendations for improving page performance, content quality, and keyword optimization, and our guide to SEO content strategy covers what to do with them once the site is live.

Benefits of migrating to HubSpot

  • Integrated tools: one platform for your website, marketing, sales, and service, so the data is shared rather than synced.
  • A CMS non-specialists can run: the drag-and-drop editor and pre-built templates let non-technical users create and manage content.
  • Personalization and conversion: content that adapts to a visitor's behaviour, location, or stage in the buying process, with built-in tools for testing and conversion rate optimization.

Key considerations when migrating to HubSpot

  1. Time and sequencing. Depending on the complexity of your existing website, the migration will vary in how long it takes. What does not vary is the order: the residency answer, then the field mapping, then the record import, then the redirects. Every step in that list is expensive to reverse.
  2. Training and adoption. Ensure your team is trained on Content Hub and the CRM beside it. HubSpot offers comprehensive resources, and working with a Solutions Partner such as Meticulosity Global can help your team use the platform to its full ability. Ask which language the training runs in and which interface it runs on, because for a bilingual team those are two answers.

Migrating your website to HubSpot can significantly enhance your online presence, streamline your marketing efforts, and improve the overall user experience. By following the steps above, and settling the residency and redirect questions before the build rather than after it, you can ensure a successful migration.

If you are looking for help to migrate your website to HubSpot, reach out to Meticulosity today. We bring 18+ years as an agency and 12+ years as a HubSpot partner to the conversation, and the first one is a consultation with no commitment attached.

Sources

  1. Gartner: Sales Survey Finds 74% of B2B Buyer Teams Demonstrate Unhealthy Conflict During the Decision Process (opens in new tab)
  2. W3Techs: Usage Statistics of Content Languages for Websites (opens in new tab)
  3. HubSpot: Data Centers (opens in new tab)
  4. UAE Government: Data Protection Laws (opens in new tab)
  5. Dubai Chambers: Dubai Chamber of Digital Economy Empowers the Business Community to Build a Future-Ready and Digitally Enabled Economy (opens in new tab)

Frequently Asked Questions

Does HubSpot host website data inside the UAE or Saudi Arabia?

No. HubSpot has no in-region data center for the UAE or Saudi Arabia: region is assigned by IP geolocation at signup, and Middle East and Africa signups default to the EU. HubSpot migrates data only out of US East, and only where it already sits in the United States, so settle residency in the compliance review, not afterward.

How should CRM records be imported during a HubSpot website migration?

As one multiple-object import rather than two sequenced ones. While the Create and associate companies with contacts setting is on, a contact import creates company records from email domains; a multiple-object import that carries its own associations is documented as exempt from the setting, so it lands the records and the associations together. Subsidiaries sharing a parent domain do not collapse, because each unique domain gets its own record, but where several companies hold the same domain, contacts are associated with only one of them and you cannot choose which.

What does HubSpot actually require of an import file carrying Arabic?

HubSpot accepts .csv, .xlsx and .xls, and states one conditional requirement: the file has to be UTF-8 encoded if it includes foreign language characters, which Arabic content always does. It documents no error message for a file that is not, which is the practical problem. Practitioners widely report Arabic arriving as question marks after a round trip through a spreadsheet CSV export, and Excel does treat CSV and UTF8 CSV as two different save formats, but HubSpot publishes nothing on that failure, so treat it as a risk to design around rather than a documented behaviour. Uploading the native .xlsx keeps the question from arising.

Does marking a HubSpot page as Arabic make it display right to left?

Marking a page Arabic changes only its language tag and the language switcher, not its layout. Right-to-left layout comes from the dir attribute set in the theme's base template, not from the page's language setting, so a page can be correctly tagged Arabic in a multi-language group and still be laid out left to right.

Will a clean HubSpot Website Grader score catch Arabic RTL problems?

No, the Website Grader will not catch it. It scores four categories: performance, mobile readiness, SEO, and security, so a clean grade on a bilingual site is a statement about the English half of it. Bidirectional text defects, like a phone number or English word rendering in the wrong position inside an Arabic sentence, need a manual check instead.

Can a website redirect map break on Arabic URLs during a HubSpot migration?

Two preconditions come first. HubSpot's redirect tool needs Marketing Hub or Service Hub Professional or Enterprise, or Content Hub at Starter and above, and redirects only work for domains connected to and hosted in HubSpot, so while the Arabic half of the site is still served from the old host those redirects have to be configured there instead. Where the tool does apply, it percent-encodes special characters typed into its fields, so the risk sits in the map you bring in: a legacy export mixing encoded and decoded Arabic paths carries that mismatch through, and nothing in the redirect report flags it.

HubSpot Migrations

Ready to Move Off Your Current CRM?

We move your data, content and automations onto HubSpot without breaking reporting or losing history along the way. Migrations run on a mapped timeline with a validation pass before your team ever touches the new portal.