# How to migrate Duda client websites to an AI website builder

Source: https://lindo.ai/guides/migrate-duda-to-ai-website-builder
Reviewed: 2026-09-03
Prepared by: Lindo Team

An editable project worksheet, not a guarantee of compatibility or rankings.

## Project brief

- Client / site:
- Source platform and account owner:
- Destination and account owner:
- Reason for moving:
- Critical visitor action:
- Content owner:
- Technical / DNS owner:
- Billing owner (separate approval):
- Planned cutover and content freeze:
- Rollback owner and trigger:
- Archive location (keep private):

## Scope

Start with one client, inventory dynamic content and apps, and test client editing separately from the public site. Keep existing billing and hosting active until their replacements are verified.

Good fit: Agencies with mostly content and lead-generation sites that want to evaluate a different publishing, branding, or client-delivery workflow.

Pause if: A portfolio that depends on untested app, membership, store, or connected-data replacements. Prove those workflows before committing to a bulk move.

## Acceptance checklist

### 1. Document the operational reason for leaving Duda

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 2. Check current export eligibility and exclusions

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 3. Archive content and confirm rights to reused assets

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 4. Enumerate rendered dynamic URLs and their data sources

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 5. Assign a replacement to every app and widget

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 6. Pilot one representative client site

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 7. Test editing with the intended client permissions

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 8. Document domain, support, and billing ownership

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 9. Approve URLs, forms, analytics, and rollback

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

### 10. Launch in supportable waves after pilot acceptance

- [ ] Complete
- Owner:
- Test / evidence link:
- Result and date:
- Exception / approved change:

## URL map

Examples below are illustrative. Replace with the actual source URLs.

| Source URL | Keep / move / merge / retire | Destination | Expected response | Tester / evidence |
| --- | --- | --- | --- | --- |
| /services/roof-repair | Keep | /services/roof-repair | 200 | |
| /roof-repair.html | Move | /services/roof-repair | 301 then 200 | |
| /summer-offer-2022 | Retire | No relevant replacement | 404 or 410 | |

## Dependency register

| Source feature | Business purpose | Destination / replacement | Owner | Acceptance test | Blocker? |
| --- | --- | --- | --- | --- | --- |
| Contact form | Send enquiries to sales | Confirm service | | Test inbox + CRM delivery | Yes until tested |

## Launch decision

- [ ] Client approved content and intentional removals
- [ ] Business actions passed with evidence
- [ ] URLs, redirects, metadata, and public indexability checked
- [ ] Domain change approved; email records preserved
- [ ] Billing changes separately authorized, if any
- [ ] Backup and rollback path available
- [ ] Production enquiry and analytics verified after cutover
- Approved by / date:
- Open exceptions and owners:
- Next review date:

## Primary sources used in the guide

- [Duda: current agency and AI capabilities](https://www.duda.co/)
- [Duda: site export availability, exclusions, and restrictions](https://support.duda.co/hc/en-us/articles/26519246857495-Site-Export)