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.
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.
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.
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.
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.
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.
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.
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.
Review pages, collection types, field bindings, widgets, and external dependencies. Agree the content inventory, extraction approach, WordPress structure, and any material that needs reconstruction.
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.
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.