Migrate From Another Page Builder to UiChemy Composer
Move pages, templates, dynamic data, and media built with Elementor, Divi, Bricks, Oxygen, or any other builder into UiChemy Composer with AI, on the same site or from one site to another.
Built your site with another page builder? Your AI assistant can move it into UiChemy Composer for you, page by page, with the same layout, text, images, and dynamic data. It works on the same site, or from one site to another.
The source can be any builder, such as Elementor, Divi, Bricks, Oxygen, Beaver Builder, Brizy, or WPBakery, a theme's own templates, or hand-written code. The old builder never needs to be installed on the new site.
What Moves
| Area | What comes across |
|---|---|
| Pages and posts | Every page, post, and custom post type item, with the same title, slug, and date |
| Templates | Header, footer, single, archive, 404, and search templates, rebuilt as Theme Builder templates with the same display conditions |
| Dynamic content | Post grids and lists become real loops, and field values become live bindings, not frozen copies |
| Content model | Custom post types, taxonomies, terms, and custom fields, with the same names |
| Media and assets | Images, SVGs, fonts, videos, Lottie files, and downloads, uploaded to the new site's media library |
| Site level | Menus, logo, favicon, site title, front page, global colors and fonts, and custom CSS |
| Interactive parts | Sliders, tabs, accordions, counters, and animations, rebuilt to behave the same |
Two Ways to Use It
| You want to... | Source | Target |
|---|---|---|
| Convert pages on your current site | This site | This site |
| Move a site to a new WordPress install | Site A | Site B |
| Move a site that already uses Composer | Site A (Composer) | Site B |
- Same site: the original pages stay untouched. Each new page is created as a draft titled "Original Title (UiChemy)", so you can compare both before switching.
- Two sites: the AI reads Site A and builds on Site B, keeping the original title, slug, date, and status. Site A is only read, never changed.
- Pages already built with Composer are copied as they are, not rebuilt.
What You Need
- UiChemy installed on the target site, with your AI client connected over UiChemy MCP.
- An MCP connector that can run PHP on WordPress, such as AI Connector, WPVibe, or Novamira. The AI needs it to read the old builder's stored data, fields, and settings.
- Same site: one connector on that site is enough.
- Two sites: connect one to each site.
- A browser tool in your AI client (optional, recommended). It lets the AI view each page as a visitor sees it, for a closer match.
No PHP connector, no migration. If none of your connected MCPs can run PHP on the site, the AI stops before starting and tells you which site needs one. Connectors that only offer fixed tools or read-only queries aren't enough.
How It Works
Connect your sites
Connect your AI client to the target site over UiChemy MCP, and add a PHP-capable connector for each site involved. See Connect an MCP Client.
Ask the AI to migrate
Tell it what to move, for example "Convert my About page to Composer" or "Move site A to site B in Composer". You can use the prompt below.
Review the plan
The AI checks everything on the source first, then shows a plan with counts: pages, posts, post types, templates, media, menus, forms, and the builders it found. It also flags anything that needs a decision. Choose everything or only some of it, and whether to publish or leave as drafts.
Let it build
It moves things in order: design system, content model, media, content, pages and templates, then menus and site settings. Progress is shown as it goes, and a long run can pick up where it left off.
Check the report
The AI compares the source and target page by page, then gives a final report: what moved, what was approximated, and what wasn't moved and why.
The Prompt
Migrate my site into UiChemy Composer.
Source: [this site / site A URL]
Target: [this site / site B URL]
Before building anything, check everything on the source (pages, posts, custom post types, templates, custom fields, media, menus, forms, and global design) and show me a plan with counts. Wait for my approval.
Then rebuild every page and template in UiChemy Composer, same to same: same layout, text, images, fonts, colors, and responsive behavior. Keep dynamic content dynamic: post grids as loops and field values as bindings. Rebuild header, footer, single, and archive templates in the UiChemy Theme Builder with the same display conditions.
Do not change anything on the source site. Leave pages as drafts until I approve them. When you're done, compare the source and target page by page and give me a report of what moved, what was approximated, and what wasn't moved.
Example prompt (one page): "Convert my Pricing page, built with Divi, to UiChemy Composer on this site. Keep the original page untouched."
Good to Know
- Your choice of builder on the target. The new pages are built in whichever page builder the target site uses: Elementor or Gutenberg. Bricks is coming soon.
- Pages start as drafts. Posts and custom post type items that were published on the source are published on the target, so loops and archives show them.
- Nothing is created twice. Before creating anything, the AI checks whether it already exists. If Site B already has a page with the same slug, it asks you whether to replace it, skip it, or create it with a new slug. Running the migration again is safe.
- Creating the content model needs UiChemy Pro. Creating custom post types, taxonomies, and custom fields through UiChemy MCP is a Pro feature. On Free, the AI can still read them, and can use ones that already exist on the target, for example from ACF or JetEngine.
- Custom fields keep their names, so every binding keeps working. If the source used ACF or JetEngine, the AI asks where the fields should live on the target, and asks before installing any plugin.
- SVG uploads: WordPress blocks SVG uploads by default. If the target doesn't allow them, the AI inlines small icons as code, or asks you to turn on SVG support.
- Pages built without the theme, such as Oxygen pages with the theme turned off, are set to Elementor Canvas on the target, so no theme header or footer appears.
- Forms, maps, shops, and memberships are flagged in the plan. Forms are rebuilt, while WooCommerce, booking, membership, and LMS features need your decision.
- Same site, separate templates: new templates are created without active conditions, so they don't clash with the old builder's templates. The AI tells you which to switch on, and which old ones to turn off, when you're ready.
What Isn't Moved
- Users and accounts, plugin settings, orders, and form submissions.
- Redirects, if the target has no redirect tool. They're listed in the report.
- Translations, unless the same multilingual plugin is on the target. Otherwise the default language moves and the rest is listed.
- Media over the upload size limit, listed in the report with the reason.
Use Cases
- Leaving a heavy page builder: rebuild a Divi or WPBakery site as clean, lightweight Composer code on the same site, and compare before switching.
- Moving to a new install: carry a client site from an old host or staging site to a fresh WordPress, with content, templates, and media intact.
- Mixed sites: a site built with two builders, plus some plain pages, all end up in Composer in one run.
If It Doesn't Work
Connected but the tool won't respond, or "Could not connect"? See Connect an MCP Client for the fix.