WordPress to Ploy.ai migration: What it costs and what you give up

I keep seeing more discussion online about WordPress to Ploy.ai migration. That's not surprising - Ploy came out of stealth in June 2026, built by Bryant Chou, the former co-founder and CTO of Webflow, and it's quickly becoming one of the biggest names in the "AI builds your website" space. It's starting to show up in conversations that used to be about Webflow, Framer, or a plain custom WordPress build.

Ploy makes a huge impression at first glance and I don't want to question that in this article. What I wanted to figure out was whether it makes sense to move an established WordPress site onto it. So, I went through Ploy's pricing page, docs, FAQ, and its own comparison pages, specifically with WordPress migration in mind. Here is what I found, and where I landed.

What Ploy.ai actually is

Ploy describes itself as a platform with three parts: a web engine that builds and edits pages, a grow engine that identifies anonymous website visitors and turns them into CRM leads, and an ads engine that manages ad campaigns. You prompt it to build or update pages, and in the background it also watches your traffic, your SEO rankings, and your competitors, then suggests changes on its own.

Ploy is not really trying to be a WordPress replacement in the way Wix or Squarespace once was. Its own comparison pages are built against tools like Framer, Vercel, Lovable, Bolt, and v0, not against WordPress. It is aimed at marketing teams and startups who need landing pages, SEO content, and ad pages shipped fast, with lead generation built in. A full business website with a blog, a shop, or years of accumulated content is a different kind of job.

Where Ploy should works well

For a quick, temporary, low-stakes site (a campaign landing page, a pre-launch page, a one-off event site, etc.), Ploy is a genuinely good option. You describe what you want, it builds a page on a real design system rather than a generic template, and you pay a reasonable amount for that compared to hiring a developer and a designer, then also paying for a domain and hosting on top. If you need something live this week and you do not plan to keep it forever, this is close to the ideal use case.

What migrating a WordPress site to Ploy means

Ploy has a feature it calls a "slurp": you paste your WordPress URL, and it reads your live site, design, and content, then rebuilds it inside Ploy on its own stack (Astro, React, and Tailwind). Ploy is upfront that this is not a full clone. It describes this step as a best-effort pass that copies your brand's structure, identity, and design tokens, not a one-to-one copy, and the credits you spend afterward are what turn that into a finished site.

Two details from Ploy's own documentation are very important here. First, the slurp captures the rendered HTML of your site at the moment it runs. Anything dynamic (a WooCommerce catalog, a membership area, a custom search, content pulled from a database or an API) comes across as static content, not as working functionality. You would need to rebuild that logic inside Ploy or reconnect it through one of Ploy's integrations. Second, Ploy's own migration cost calculator admits that Framer and Webflow "export cleanly," while "WordPress plugins and custom stacks need functionality rebuilt, not just copied," and that this pushes the difficulty and cost of the whole migration up.

So, if your WordPress site is mostly pages and a simple blog with a clean, non-fancy and complicated design, a Ploy migration will likely look good after a round or two of prompting iteration, and the process really can take hours instead of weeks. But, if your website has a "complicated" design and custom animations, leans on WooCommerce, custom plugins, membership logic, or years of page-builder markup, expect the "free, instant migration" pitch to turn into a real rebuild project once you get past the homepage.

The real cost of staying on Ploy

Ploy's pricing has four tiers: Free at $0 a month, Starter at $50 a month, Pro at $300 a month, and Enterprise at custom pricing. Ploy sells its Pro plan as the "most popular" tier for active workspaces, and it is easy to see why once you look at what each tier actually unlocks.

According to Ploy's own pricing FAQ, the Free plan doesn't include a custom domain at all. Starter, at $50 a month, is what unlocks a custom domain and Google integrations. Pro, at $300 a month, is what unlocks GitHub sync, plus CRM and ad integrations such as HubSpot, Attio, Google Ads, and Meta Ads, along with a much larger visitor-enrichment allowance. So if a client wants their own domain and wants to connect HubSpot (a completely normal ask for a business site), that is $300 a month, every month, for as long as the site exists. Not because they are actively building anything that month, you need to pay 300$ per month just to keep the plan tier that lets those features exist.

To be fair to Ploy, the credits themselves (the thing you actually spend to have the AI do work) are mostly used up while it is actively building or editing something. A site that just sits there and serves traffic burns through very little. So the idea that cost keeps climbing forever is not quite accurate for usage. But the flat monthly fee for the plan tier is a different story, and that one doesn't care whether you touched the site this month or not. Compare that to a typical WordPress setup, where domain and hosting together often run $10 to $30 a month, plugins are usually a one-time or modest annual cost (for example, for ACF), and there is no separate monthly tax per integration.

Who owns what you build

Here is what Ploy's own documentation says: each site you build gets its own repository, but that repository lives under Ploy's GitHub organization, not under your own GitHub account. Ploy does offer a "Code Sync" feature that lets you pull that repository down locally, edit it in your own editor, and push your changes back up. That is a useful feature, and it means you're not completely locked out of the code the way you might expect from a pure no-code tool.

But look closer and it's a sync workflow between you and Ploy's AI agent, not an export or a transfer of ownership. There is no documented way to move that repository into your own GitHub account, and even if you copied the code out by hand, most of what makes the site actually function as a business site (the forms, the CRM sync, the visitor identification, the analytics, the hosting, the SSL, the custom domain routing) runs on Ploy's infrastructure, not in the code itself. Cancel the plan and that all goes with it.

That is a real difference from WordPress - WordPress core, your theme, and your plugins are just PHP files (and of course, some HTML templates, CSS, JS etc.) and a MySQL database, sitting on whatever host you choose. You can move that to a different host in an afternoon, self-host it, or hand the files to any developer. Ploy gives you more visibility into your code than a typical closed platform, which is worth acknowledging, but it doesn't give you that same kind of independence.

A few other things worth knowing

Before moving away from WordPress, it is worth being honest about why you want to leave. If the problem is technical (a site built on top of Elementor that has become impossible to maintain, tons of the plugins), moving to Ploy doesn't exactly fix that problem. It trades one set of constraints for another: instead of plugin bloat, you get a credit system and a fixed monthly fee per feature.

A serious cleanup of your existing WordPress site, or a move to a leaner setup such as headless with a framework like Astro or Nuxt in front of it, usually solves the actual problem for a fraction of $300 a month, and you keep full ownership of the result. Of course, refactoring is not free - it costs the developer and time, but in the age of AI, a developer supported by AI tools can significantly speed up this time, and the cost is one-time.

If the real reason is more personal - you simply don't like using the WP dashboard or would like to work on your website using Claude or Codex - that doesn't mean Ploy is the only option. A well-prepared WordPress system can fully integrate with Claude, allowing you to, for example, create new landing pages without accessing the WP dashboard. You can also look into other solutions, even without a traditional CMS, such as Astro.

Summary

For a fast, temporary, low-stakes page, Ploy is a good tool, and I would recommend it to a client for exactly that job. For migrating an established WordPress site with real content, real functionality, and years of SEO equity, I would slow down - run the numbers past a year or two and ask what happens to the site the day you decide to leave.

If you're just thinking about creating a new website and you really like the idea of ​​editing or expanding it using AI, it doesn't have to be Ploy, we can create a website that works with AI models in both WordPress and another stack, without the need to use a costly "overlay". I can help you analyze your needs and create a solution - feel free to contact me.

A few common questions

Is Ploy.ai good for a WordPress migration?
It depends heavily on the site. Simple, mostly static WordPress sites can migrate cleanly and look good after a bit of refinement. Sites with WooCommerce, membership areas, or a lot of custom plugin logic will need real rebuild work, by Ploy's own admission.

How much does Ploy.ai cost per month?
Free is $0, Starter is $50, Pro is $300, and Enterprise is custom pricing. You need Starter for a custom domain and Pro for things like HubSpot, GitHub sync, or ad platform integrations.

Can I export my code from Ploy.ai?
Partly. Ploy's Code Sync feature lets you pull your site's code from a GitHub repo and edit it locally, but that repo lives under Ploy's own GitHub organization, and most of the site's actual functionality depends on Ploy's hosting and infrastructure rather than portable code.

Is Ploy.ai a replacement for WordPress?
Not really, and Ploy doesn't market itself that way either. It positions itself against tools like Framer and Vercel, aimed at marketing teams shipping landing pages, not as a general CMS or e-commerce replacement.