Ploy site migration: how it works and what to check when moving from WordPress, Webflow, Framer or Wix
Short answer: Ploy, an AI platform that builds and hosts business websites, moves a site from WordPress, Webflow, Framer or Wix (all website platforms) by reading its public web address and rebuilding the pages on its own design system, a set of fonts, colors and page parts. Its docs call this "a rebuild, not an identical copy", it spends AI credits (points that meter its AI work), and nothing goes live until you approve it. Forms, plugins, embeds and custom code may need separate work, so test before you point your domain at it.
You want to know what actually happens to your pages, links and Google traffic when you hand an existing site to Ploy, and what to check before you switch.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Ploy does not copy your old site file by file. You give its AI Agent your site's public address, it lists every page it finds, builds a new version of each page, and shows you the result. You review, fix, and only then switch your domain. That makes it a rebuild with a safety net, which is good news for sites that already look dated and less good for sites with lots of custom features.
This guide covers where Ploy can move sites from, what it keeps, what it does not, how credits and plans affect the cost, a worked example with made-up numbers, and a test plan with pass and fail rules. If you want to try it, you can start with Ploy's free plan and run the inventory step on a copy of your own address before you commit to anything.
This page may contain affiliate links from which Blur Studio earns commissions.
What Ploy migration is, in plain words
Per Ploy's docs (read November 2026), you paste your public site address into Ploy's Agent, which is its built-in AI assistant, or you start the move through Ploy's MCP connection from Claude, an AI assistant. MCP is a standard way for AI apps like Claude or ChatGPT to connect to other tools. The address has to load without a login. The Agent takes inventory of the site, shows you a plan, rebuilds the pages on a design system it learns from your current look, and waits for your approval.
On a large site, Ploy builds the key pages first while your old site keeps serving everything else. Ploy's WordPress page also says that content such as posts, pages and custom post types is pulled from your public site into PloyDB, its built-in database that can turn each row into a page. A second import creates fresh tables. It is not a sync, so edits you make on the old site afterward do not flow across.
For background on what Ploy is and what else it sells, read what Ploy AI is. For plan prices, see Ploy AI pricing explained.
Supported sources
Ploy's own text lists these starting points. Check Ploy's docs for the current list before you plan around one.
| Source | What Ploy says | What to know |
|---|---|---|
| WordPress (the open-source site software many businesses use) | Dedicated migration page. Pulls posts, pages and custom post types from the public site. | Plugins and shortcodes (small codes that WordPress expands into features) may need separate work. |
| Webflow (a visual site builder) | Dedicated migration page. Collections can import into PloyDB. | Per Ploy, forms, embeds and interactions may need separate work. |
| Framer (a design-first site builder) | Listed as a source. Ploy can also keep an old Framer site live for pages not yet moved. | Framer does not offer HTML export for self-hosting per its own help page, so a public-URL rebuild is the practical route. |
| Wix (a hosted drag-and-drop builder) | Listed as a source. | Wix says a Wix site must run on Wix's servers, so there is no export file to hand over. A rebuild from the public address does not need one. |
| Squarespace, Sanity (content system) | Listed for moving content into PloyDB. | Squarespace exports only a partial XML file for WordPress, so check what you can export first. |
| Custom code (Astro, Next.js, Vite) | Astro repositories import with a command-line tool. Next.js and Vite apps are ported by your own coding agent. | That route uses no Ploy AI credits per its docs. |
What it keeps and what it does not
Kept or aimed at being kept: your public page content, your URL structure where you tell it to keep URLs, and your look, rebuilt on a design system. Ploy's docs say to keep existing URLs where you can and to add 301 redirects in its Path routing screen for any that change. A 301 redirect is a permanent forward from an old address to a new one, and it is how Google learns that a page moved.
Needs separate work, per Ploy's docs: forms, plugins, shortcodes, embeds, interactions, custom code, private pages and live data. Ploy's WordPress page says to use its migration report to review where each form sends email, and to check where past submissions stay.
Not stated, so you must check: how page titles, meta descriptions (the short text Google shows under a result), canonical tags (a tag that names the preferred address of a page), structured data and image names are handled. Ploy's WordPress docs page does not mention SEO tags at all. Ploy's case study of the agency Sengo says it moved about 600 WordPress pages in one night and that the Agent found about 50 existing mistakes on the live site. That is the company's own account, with no search results or redirect detail attached, so treat it as a sign of speed, not proof of rankings.
Do not trust "import in 60 seconds" style claims on any vendor page. Judge the migration by the checks below.
What it costs
As of November 2026, Ploy's pricing page shows Free at $0, Starter at $50 a month ($480 a year), Pro at $300 a month ($2,880 a year) and Enterprise on custom pricing. Check the pricing page before you pay.
- The rebuild spends AI credits. Free gives 500 a day up to 2,000. Starter gives 4,000 a month and Pro 24,000. Unused credits do not carry over. Ploy publishes no price per action, so you cannot work out the credits for a 200-page site in advance. Open Settings, then Organization, then Usage to watch the meter.
- A custom domain needs Starter or higher. On Free, your site publishes to a ploy.build address. You can test a full rebuild there, but you cannot send real traffic to it under your own name.
- Plan for the credits to run out mid-job. When credits are gone, chat stops. You can move up to a bigger credit tier on the same plan, or turn on auto-reload with a monthly spend limit.
Moving a site with your own coding agent through Ploy's command-line tool uses no Ploy AI credits, per its docs. That suits developers, not most owners.
Three ways to switch traffic
- Whole domain. Point your domain's DNS (the address book that tells browsers where your site lives) at Ploy. Ploy's docs say DNS changes can take up to 24 hours, and that adding its SSL (the padlock certificate) verification record first reduces downtime.
- One path at a time. After the domain points at Ploy, move sections one by one and send everything unmoved to your old host, for example a subdomain like www2, using the "Everything else" row in Path routing. Use this for big sites.
- WordPress with the Ploy Connect plugin. The Ploy Connect plugin, which needs a paid Ploy plan, serves chosen Ploy pages through WordPress when you cannot move the domain. Your homepage stays on WordPress.
If you use Cloudflare (a service that sits in front of many sites), Ploy warns that its Flexible SSL mode causes redirect loops. Use Full (strict) or "DNS only".
What to expect from Google
Google's own guide for moving a site with URL changes says permanent redirects do not cause a loss in PageRank, its link-credit score, and that for a medium-sized site it can take "a few weeks or more" for Google to show the new addresses. Google recommends a URL mapping from each current address to its new one. Its Change of Address help says to keep redirects for at least 180 days, longer if Google still sends traffic to them.
Recovery studies are about moving to a new domain name, which is a bigger change than a platform switch on the same address. A Search Engine Journal study of 892 domain moves (published January 2025) found an average of 523 days for traffic to return, and SALT.agency's 2026 study of 1,052 moves found a median of 304 days. I know of no dataset for same-address platform switches, so do not quote either number as your risk. They are a reminder that the more you change, the more you risk. For the fuller method, read how to keep SEO rankings when you rebuild or move a site and what a migration costs.
Worked example with made-up numbers
Say a plumbing company has a 40-page WordPress site: home, 6 service pages, 12 city pages, 15 blog posts, contact, 3 policy pages and 2 others. It gets 900 visits a month. The owner wants a faster, cleaner site and a way to edit pages by chat. All numbers below are invented for the example.
| Step | What happens | Pass looks like |
|---|---|---|
| 1. Benchmark | Export the page list and top 10 pages by clicks from Google Search Console (Google's free tool that shows how your site performs in search). | A saved sheet of 40 addresses and click counts. |
| 2. Free-plan trial | Run the inventory on a Free workspace and read the plan. | The Agent lists all 40 pages and flags the contact form. |
| 3. Review | Compare each page to the old one on phone and desktop. | Every service and city page keeps its phone number, hours and address. |
| 4. Form test | Submit the quote form 3 times. | 3 of 3 reach the owner's email or CRM within minutes. |
| 5. Switch | Move to Starter, add the domain, keep every address the same. | No 404 errors (page not found) in a crawl of the 40 addresses. |
| 6. Monitor | Check Search Console weekly for 8 weeks. | Clicks within a normal range of the benchmark, and no new errors. |
Copy-ready pre-switch test plan
Run this on the Ploy preview address before you touch DNS. Each item is pass or fail. Do not switch with a fail open on anything marked must.
- Page count (must). Every address on your old sitemap, the file that lists your pages, either exists on the new site or has a 301 to its closest match.
- Titles and descriptions (must). The top 10 pages by clicks keep their title and meta description or a better version you chose on purpose.
- No stray noindex (must). Noindex is a tag that tells Google to leave a page out. Search the preview for it and remove it before launch.
- Forms (must). Each form submits, sends the right alert, and the data lands where you expect.
- Tracking (must). Your analytics, ad and call-tracking tags fire on the new pages. Ploy lists Google Analytics 4 and PostHog among its tools, so confirm which one you keep.
- Phone numbers, maps, embeds. Booking widgets, review feeds and maps work. Ploy says embeds may need separate work.
- Speed and mobile. Pages load without layout jumps on a mid-range phone.
- Accessibility. Headings in order, image descriptions present, buttons usable by keyboard. Check the target your market uses, commonly WCAG 2.2 AA (a widely used accessibility standard, a convention and not a law for most private sites).
- Facts. A human reads every page. AI rebuilds can drop a licence number or reword a claim.
- Rollback. Keep the old host running for at least 30 days. Ploy keeps versions you can restore and publish again.
Failure modes to plan for
- Redirect chains and wrong targets. Old address goes to an in-between address and then the final one. Fix by mapping each old address directly to the final one.
- URL drift. The rebuild shortens or renames addresses. Keep them identical unless you have a reason.
- Lost forms and plugin features. Quote calculators, memberships, shop checkouts and booking plugins are not covered by a content rebuild.
- Credit run-out. A big site can use up a month's credits before finishing. Do the key pages first.
- Cookie banner not wired. Ploy's docs say you are responsible for your own banner and privacy policy.
- Old site cancelled too early. Keep the old account and domain registered, and do not cancel hosting until the new site is stable.
Who should skip Ploy migration
- Shops with large product catalogs and checkout. Ploy's migration text covers pages, posts and collections, not a store.
- Membership, course or booking sites that depend on plugins.
- Anyone who needs the final site as files they can host anywhere without a subscription. Ploy's docs say a command-line command can export source code on every plan, but check the terms and test an export before you rely on it.
- Sites where a single mistake is costly, such as regulated businesses, unless a person reviews each page.
- Agencies that need white-label branding. Ploy's agency page does not describe white-label terms.
Pick something else if the move is mostly about design. A designer on Webflow or Framer, or a careful WordPress clean-up, may cost less than a rebuild.
How I'd approach this
My view: use Ploy to move when your site is mostly pages and posts, you are happy to have the look rebuilt, and you will check each page yourself. Skip it when your site depends on plugins you cannot replace. Always put the Free plan test before any payment.
If you want a custom version, Blur Studio builds AI agents that use your business knowledge, CRM and calendar connections, and finishes half-built sites and flows, with ongoing care.
First week plan.
- Day 1: Export your page list and top 10 pages from Search Console. Save a full copy of the old site and database. Note your domain registrar login, and who owns it.
- Day 2: Book a Ploy demo or open the Free plan, and ask in plain words what happens to titles, forms and redirects on your platform. Write down the answers.
- Day 3: Run the inventory on the Free plan. Do not publish to your domain.
- Day 4 and 5: Work through the test plan above and write down every fail.
- Day 6: Decide. If four or more must items fail and cannot be fixed, stop and keep your site. If all pass, choose Starter, and plan the switch for a quiet day.
- Day 7: Set up your redirects, add the domain, and start the weekly Search Console check.
Prices and features can change, so check Ploy's current pricing and migration docs before you decide.
If the site is live but not showing, use the new site not showing on Google checklist.
Related guide: moving a Bubble marketing site to a faster stack.
Related guide: previewing a site rebuild before you commit.
Questions people ask
Does Ploy keep my page URLs when it migrates a site?
Ploy's docs tell you to keep existing URLs where you can and to add 301 redirects in Path routing for any that change. Check each of your important addresses after the rebuild. Google's site-move guide says to map each old address to its new one, and its Change of Address help says to keep redirects for at least 180 days. See how to keep SEO rankings when you move a site.
Does Ploy migration copy my site exactly?
No. Its docs call it a rebuild, not an identical copy. Pages are rebuilt on a design system and you review each one before anything goes live. Forms, plugins, shortcodes, embeds, custom code and private pages may need separate work.
Can I move a Wix site to Ploy?
Ploy lists Wix as a source. Wix says its sites must run on Wix's own servers, so there is no export file to import. A rebuild from your public address does not need one. Check forms, store features and tracking after the move. See moving off Wix or Squarespace without losing search traffic.
How many credits does a migration use?
Ploy does not publish a price per action, so the number is unknown until you run it. Larger sites use more. Check Settings, then Organization, then Usage before a full build. As of November 2026 the Free plan gives 500 credits a day up to 2,000, Starter 4,000 a month and Pro 24,000 a month.
Do I need a paid plan to move a site to Ploy?
You can test a rebuild on the Free plan, which publishes to a ploy.build address. A custom domain needs Starter ($50 a month, or $480 a year, as of November 2026) or higher. Check Ploy's pricing page before you pay.
Will my Google rankings drop after a Ploy migration?
Nobody can promise either way. Google says permanent redirects do not cause a PageRank loss, and that it can take a few weeks or more for new addresses to show. Domain-move studies show long recoveries, but those are about changing domain names, not a same-address platform switch. Benchmark first and watch Search Console weekly. See what a migration costs for the wider picture.
Can I switch only some pages to Ploy?
Yes. After your domain points at Ploy, route chosen paths to Ploy and send "Everything else" to your old host. WordPress sites can also use the paid Ploy Connect plugin, which keeps your homepage on WordPress.
Is a Ploy migration better than hiring an agency?
It depends on the site. Ploy is faster for page-based sites, but you must still review every page. An agency can handle forms, plugins and redirects for you, at a higher price. Migration quotes vary widely by seller and scope. Some seller pages show figures from about $1,500 to $35,000 or more, and no independent survey backs them, so ask what each quote includes.
More in this topic: Ploy.ai: the product, pricing and reviews (12 guides) →
Sources
- Ploy docs: WordPress migration
- Ploy pricing
- Ploy docs: custom domains
- Ploy docs: credits
- Ploy case study: Sengo
- Google Search Central: site move with URL changes
- Search Engine Journal: how long should an SEO migration take
- SALT.agency: migration recovery study
- Wix help: exporting or embedding your Wix site
- Framer help: exporting to HTML