# How to migrate a WordPress website to an AI website builder

Source: https://lindo.ai/guides/migrate-wordpress-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

Back up the complete WordPress installation, map each plugin to a business requirement, and rebuild the public site as a reviewed draft. Keep WordPress—or another suitable system—for any critical capability you cannot replace.

Good fit: Content-led agency and service-business websites where the destination can handle publishing, enquiry forms, and routine client updates.

Pause if: Complex WooCommerce, membership, learning, or custom application workflows without a separately validated data and feature migration.

## Acceptance checklist

### 1. Identify hosting move versus platform replacement

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

### 2. Confirm ownership of domain, hosting, plugins, and data

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

### 3. Retain a secure restorable database and file backup

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

### 4. Export WordPress content separately

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

### 5. Inventory public URLs and valuable downloads

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

### 6. Assign and test a replacement for each plugin job

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

### 7. Pilot ordinary pages and custom content types

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

### 8. Review blog formatting and source-hosted assets

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

### 9. Implement redirects on the active serving layer

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

### 10. Test production forms and retain the rollback path

- [ ] 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

- [WordPress: what Tools → Export includes](https://wordpress.org/documentation/article/tools-export-screen/)