WordPress to Webflow for Belgium's Digital Dentistry Partner
Bescan needed more than a migration. They needed a site their team could manage in three languages, their SEO partner could build on, and their customers across Belgium and Luxembourg could actually trust. We rebuilt it on Webflow with native localization, brand pages, a product catalog, and full GDPR compliance.
The new Bescan website on Webflow
Why a Belgian digital dentistry distributor outgrew WordPress
Nicolas Ravets started Bescan in 2016 to bring the best digital dentistry equipment to dental practices and labs across Belgium and Luxembourg. Intraoral scanners, CBCT imaging, CAD/CAM systems, 3D printers. The full digital workflow. He built the original website himself on WordPress. It worked. For a while.
The site was in French with Weglot handling automatic translation into English and Dutch. Nicolas had 22 product pages, an about page, a contact page, and a growing sense that the whole thing was getting harder to manage. His SEO and Google Ads partner, a local agency, agreed. They wanted to add pages, restructure content, and optimize. But doing that on the existing WordPress setup meant fighting the platform at every turn.
Nicolas reached out looking for someone to migrate the site to Webflow. What he actually needed was a complete rethink: proper content architecture, native multilingual support that wasn't bolted on, brand pages for each manufacturer, a product catalog that could grow, and GDPR compliance that would hold up under European law. The WordPress site was the starting point, not the blueprint.
What wasn't working on the old WordPress site
WordPress to Webflow migration with multilingual CMS
Template Selection & Brand Customization
Content Architecture & Product Catalog
Native Multilingual Setup
GDPR Compliance & Legal Framework
Performance and accessibility gains after migration
Page Speed 54 → 76
Accessibility 85 → 97
3 Native Languages
6 Brand Pages + Blog + FAQ
Why migration is more than a platform swap
A lot of WordPress-to-Webflow migrations are treated as lift-and-shift operations. Copy the pages, match the layout, swap the CMS. That's a missed opportunity. The reason Nicolas wanted to move platforms wasn't because WordPress is bad. It's because his business had outgrown what his self-built site could do. The migration was the excuse to fix the actual problems: content structure, multilingual management, and the ability for his partners to build on top of the site without calling a developer every time.
The coordination was a three-way effort. Nicolas provided the product knowledge and brand relationships. His SEO agency shaped the content strategy and page structure. We handled the build, the template customization, and the technical details: localization, GDPR compliance, performance. That kind of collaboration works when everyone stays in their lane and communicates clearly. In this case, it did.
