★★★★★ 4.7 CE

Duda Migration & Switching Guide 2026

Duda is harder to move into than out of: there's no importer, so you rebuild, but it offers rare full code export. Dynamic features break on the exported site.

Website BuildersVerified today

Full review Pricing Official site ↗

Duda Migration verdict

Verified today·6 sources checked

Duda is the unusual builder that is harder to move into than out.

There is no importer for an existing site, so you rebuild the design and bring content in through the Media Manager, product CSV and a client form. On the way out it offers full code export, a zip of HTML, CSS, JS and media you can host elsewhere.

How to plan the move

Duda suits agencies building fresh sites for clients who value that the finished markup can be exported and hosted anywhere. It is less ideal if you need to import an existing site quickly, since there is no site importer and the build starts from scratch.

Honest limits

There is no importer for an existing site, so you rebuild the design and bring content in via Media Manager, product CSV and the client form.
Full code export is available, covering HTML, CSS, JS, images and media, but it comes as three device-specific folders. Dynamic features like personalization and contact forms stop working on an exported site. You cannot edit it in the builder or unminify the code.
Export is role-gated to account owners or staff, and you may not resell Duda template designs.

Site import: Not supported (rebuild)
Content import: Media + products (CSV)
Code export: HTML/CSS/JS zip
Export caveat: Dynamic features stop
Export format: 3 device folders

View sources

This page covers importing into Duda and switching away. SEO output and pricing live on their own pages.

What moves into Duda, and can you leave?

Migration & portability receipt

Pick what you are bringing to Duda, and see exactly what transfers.

Migration read4 transfer, 1 need hand work

Media (images, video, files): via CSV or API, Media Manager, up to 15,000 items, 200MB/file.
Store products: via CSV or API, CSV import to native or third-party store.
Client copy & business data: via CSV or API, via the content-collection form to the Content Library.
Old URLs / redirects: via CSV or API, CSV redirect import, 200 per file.
Existing site (design/pages): does not transfer, no site importer; rebuilt in the editor.

Cutover steps, in order

1Rebuild the site in the editor, no site importer.
2Import media and products, Media Manager + product CSV.
3Collect client content, collection form to Content Library.
4Set redirects and schema, CSV 200/file + JSON-LD embed.
5Connect domain (CNAME + A), no AAAA/CAA; up to 48h.

Every row is a documented import/export capability from Duda and the source platforms, not an effort estimate.

Duda migration configuration

Duda does not host domains. Connect yours with a CNAME that forwards the naked domain to www, plus two A records on the @ domain for balance and redundancy. Do not configure AAAA or CAA records, which can block the SSL certificate. Propagation usually takes a few hours and up to 48.

Connect a domain (DNS)text

; Add at your domain host (auto host-login or manual)
@      A      <Duda IP 1>     ; two A records on @ for balance/redundancy
@      A      <Duda IP 2>
www    CNAME  <Duda target>  ; CNAME forwards naked domain to www
; do NOT add AAAA or CAA records (they can block SSL); up to 48h to propagate

Bring your old URLs over with a two-column CSV (old URL, new URL), up to 200 rows per file, with wildcards and variables. Add one single redirect first to reveal the CSV upload. Existing pages take priority over a redirect.

Bulk redirects (CSV)csv

old URL,new URL
/old-home,/
/products/*,/shop/*
/contact-us,/contact
# up to 200 rows per file; wildcards + variables; existing pages take priority

Account owners or staff can export the published site as a zip of HTML, CSS, JS, images and media that runs without the editor. Two big caveats: it exports as three device-specific HTML/CSS folders, and dynamic features (personalization, contact forms) stop working, so additional development is needed to run it elsewhere.

Export the site (the way out)bash

# Export downloads a .zip with HTML / CSS / JS / images / media
# It generates THREE device-specific HTML/CSS folders (desktop/tablet/mobile).
# Dynamic features stop working on the exported site:
#   personalization, contact forms, and other dynamic widgets.
# You cannot edit it in the builder afterward, or unminify the JS/CSS.

What imports cleanly into Duda

Content	Into Duda	Detail	Source
Existing site (WordPress/other)	Not supported	No documented importer for an existing site; the design is rebuilt in the editor	—
Media (images, video, files)	Media Manager	Import up to 15,000 items per site, 200MB per file, from your computer or social	—
Client content	Collection form	Share a form; inputs land in the Content Library (Business Data, Text, Media)	—
Store products	CSV (native + third-party)	Import products to the native store or a connected third-party store by CSV	—
Pages, layout, design	Rebuilt	Built in the editor; no automated import of an existing layout	—
Redirects	CSV (set up in editor)	Bring old URLs over via the redirect manager CSV, 200 per file	—

Source-to-Duda mapping

Element	Lands in Duda as	Caveat	Source
Images, video, files	Media Manager	Up to 15,000 items, 200MB per file	—
Store catalog	Products (CSV)	Native or third-party store import	—
Client copy & business data	Content Library	Via the customizable collection form	—
Old URLs	URL redirects (CSV)	200 per file; existing pages take priority	—
Schema	Re-generated in editor	JSON-LD generated by type and embedded per page	—
Design / layout	Rebuilt	No automated site import; built in the editor	—

Duda migration timeline and rollout

Phase	What happens	Effort	Source
1. Rebuild the site	Design in the editor	High; no site importer	—
2. Bring in media	Media Manager import	Low; up to 15,000 items	—
3. Import products	Store CSV (if ecommerce)	Low; native or third-party	—
4. Set redirects & schema	CSV redirects + JSON-LD embed	Medium; 200 per CSV file	—
5. Connect domain	CNAME + two A records, no AAAA/CAA	Low; up to 48h to propagate	—

What to verify before you commit to Duda

There is no importer for an existing site: you rebuild the design in the editor and bring content in through the Media Manager, product CSV and the client form, so plan for a manual rebuild on the way in
On the way out Duda offers full code export, a real differentiator: a zip of HTML, CSS, JS, images and media that runs without the editor, so your markup is portable
But the export has teeth: dynamic features like personalization and contact forms stop working, the site comes as three device-specific HTML/CSS folders, and you cannot edit it in the builder or unminify the code afterward
Export is also role-gated and restricted: only account owners or staff can export, and you may not copy Duda template designs to sell, so the export is for hosting your own content, not redistributing templates

Duda Migration FAQ

Can I import an existing site into Duda?

No. Duda does not document an importer for a WordPress or other-builder site, so you rebuild the design in the editor. What you can import is content. Media comes through the Media Manager, up to 15,000 items at 200MB per file, store products by CSV, and client copy through a customizable content-collection form that lands in the Content Library.

Can I export my Duda site?

Yes, and this is a real differentiator for a hosted builder. Account owners and staff can export the published site as a zip of HTML, CSS, JavaScript, images and media that runs without the editor, so you can host it elsewhere. The export is for your own content, and you may not copy and resell Duda's template designs.

What breaks when I export a Duda site?

The dynamic layer. Personalization, contact forms and other dynamic features stop working on an exported site, and because Duda serves content per device the export comes as three device-specific folders. You cannot edit it in the builder afterward or unminify the code, so additional development is needed to run it on a new platform.

How do I bring my old URLs to Duda?

Through the redirect manager. You import a CSV of up to 200 redirects per file, with the old URL in the first column and the new URL in the second, and wildcards and variables are supported. Set these up as part of the rebuild, and remember that existing pages take priority over a redirect.

How do I connect my domain to Duda?

Duda does not host domains, so you add DNS records at your registrar. Use a CNAME that forwards the naked domain to www, and two A records on the @ domain for balance and redundancy. Do not add AAAA or CAA records, which can block the SSL certificate. Propagation usually takes a few hours and up to 48.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources

Source	What was checked	Last checked
Duda Official	Official product page	July 10, 2026
Duda Support	Articles 26519965613847 Import And Collect Content	July 10, 2026
Duda Support	Articles 26519925447703 Url Redirects	July 10, 2026
Duda Support	Articles 26519964391447 Schema Markup	July 10, 2026
Duda Support	Articles 26520132463383 Make Your Site Live Initial Steps And DNS Record Setup	July 10, 2026
Duda Support	Articles 26519246857495 Site Export	July 10, 2026

Every fact on this Duda page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.