Search rankings survive the move
A URL inventory and a redirect plan protect the pages that already earn traffic, which is the part a migration most often loses.
Duda to WordPress migration
Rebuild your Duda website in WordPress with the page content, dynamic collections, and required widgets mapped before development. Norml reviews the source account and its access limits, then builds an editable destination using the agreed design. The plan identifies what can be extracted and what must be reconstructed, without assuming a complete website export is available.
A few clients we’ve worked with
What we do
Rebuild Duda in WordPress with page and collection mapping, replacement widgets, form checks, media transfer, and a verified redirect plan.
What a migration actually moves.
Moving a site changes more than where the files live. It moves your URLs, your search history and every integration pointed at the old address.
Nothing is left behind
Content, media, forms and integrations are inventoried before anything moves, so the gaps are found before your customers find them.
There is a way back
A backup, verification checks and a rollback approach turn a bad launch into an inconvenience instead of an outage.
What the migration covers
Duda content can live in pages, collections, external data sources, and connected widgets. We inspect those sources separately and choose a transfer route supported by your account.
- Solution
- Migrations
- Current platform
- Duda
- Destination
- WordPress
Pages, assets and design
We inventory the public pages, navigation, original media, and reusable sections. The live site is the visual reference for the agreed WordPress build. Content capture and any available exports are reconciled against that inventory so important text, files, and images are not lost between systems.
Collections and dynamic pages
We map collection fields, row identifiers, and dynamic-page URLs into suitable WordPress content types. External collections need access to their upstream source and a decision about ongoing updates. A data export does not by itself recreate the page layout or the rules binding fields to widgets.
Widgets, forms and integrations
Required widgets receive a replacement decision, including forms, galleries, search, booking tools, or embedded applications. We record the data each feature reads or writes and test its destination behavior. Lead forms need verified recipients, field mapping, submission confirmation, and agreed spam controls.
Languages, access and URLs
Language variants, gated pages, personalization rules, and dynamic slugs are reviewed explicitly. We prepare redirects for changed addresses and check that restricted material remains protected. Domain settings, analytics configuration, and the editor handoff are included in the approved launch plan.
Client reviews
Read our reviews on Clutch ↗“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
What we need before the move
Account permissions and source access
We need authorized Duda access, the account or agency owner, domain details, original media, and the WordPress destination. For collections supplied by another service, include its owner and available authorized export or API route.
Export and feature boundaries
Available APIs, editor exports, and account permissions must be verified for the source. We do not promise a native one-click Duda-to-WordPress transfer. Memberships, ecommerce, appointments, and billing require separate data and behavior review when included.
How we prepare the move
Identify each content source
Review pages, collection types, field bindings, widgets, and external dependencies. Agree the content inventory, extraction approach, WordPress structure, and any material that needs reconstruction.
Build a representative page
Create a WordPress template using sample collection records and agreed assets. Check how fields appear, how an editor updates them, and whether required widgets or forms behave correctly.
Transfer and verify
Populate the approved content, reconcile records and URLs, and test navigation, forms, access, and mobile layouts. Connect the domain under the agreed plan, recheck public routes, and hand over the publishing instructions.
The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Artur Tsitou
DevOps & Backend Developer
Max Tymoshyn
Founder & Architect
Petr Savenok
Full-Stack Developer
Marina Omelchuk
QA Engineer
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedRelated services.
Questions about the migration
Can dynamic collections be transferred?
We first verify the collection type, available account access, and source fields. Exported or API-accessible records can be mapped into WordPress where supported. Dynamic-page layouts and field bindings still require a destination implementation.
Which Duda widgets need replacements?
Any feature that depends on Duda’s runtime or a connected service needs a compatibility review. We agree the required visitor behavior and editor controls before choosing WordPress components or external integrations.
Is an export required to start?
A reliable source inventory and authorized access are required. Depending on the account, the agreed route may combine available data exports, original assets, and page reconstruction. We establish that route before committing to complete transfer coverage.
Share your current website, the features you rely on, and what needs to change. We will review the WordPress requirements and identify the content, rebuild work, and launch checks your move needs.