Why move from Duda?
WordPress can make it easier to choose your hosting, manage your content, add integrations, and keep control of the finished site. Wigoh helps you move the visible site experience into a WordPress preview without taking the Duda site offline.
What to expect
Wigoh analyzes the public Duda site and recreates its important content and design patterns, including:
- Pages, navigation, headings, and calls to action
- Images and publicly visible media
- Brand colors, typography, spacing, and layouts
- Forms and common site functions using WordPress equivalents
- Page metadata and URL information where available
Duda widgets and account-specific features may not have direct WordPress copies. Treat them as requirements to recreate and test, rather than assuming they transfer automatically.
The migration process
- Share the Duda site URL. Wigoh maps the site before building.
- Review the private WordPress preview. Your Duda site continues serving visitors.
- Test every business-critical feature. Check forms, tracking, booking, maps, and integrations.
- Approve the launch. Prepare the domain and redirects only after the preview is ready.
Prepare for a clean handoff
Create an inventory of Duda widgets, custom code, analytics, forms, and third-party services. Also note which pages are most important to customers and search engines. This gives you a focused review plan and helps separate content migration from feature replacement.
Keep the original site live during the transition. For URL and search checks, use the SEO continuity guide.
Duda migration checklist
- Inventory widgets, integrations, and custom code
- Review all key pages and navigation paths
- Test forms and conversion actions
- Check mobile layouts and image quality
- Confirm analytics and tracking requirements
- Map important URLs and redirects
- Change DNS only after final approval