Move off WordPress. Keep the blog you like.
You inherited a WordPress site, or built one five years ago, and now you're afraid to update the plugins because one broke the site last year. Give the AI your live URL. It drafts every page and every post in its own builder. WordPress stays live as a fallback until you're sure.
Who this is for
The site is slow. You pay somewhere between $10 and $80 a month for hosting, plus a handful of annual plugin licenses you forgot you renewed. You have a blog with a hundred posts you like and don't want to lose. The last plugin update broke something, so now you don't touch it.
You want the content, especially the blog, to move cleanly. You want the site to get faster on the way and you want to stop being WordPress's customer. Here is how the move works and where it doesn't fit.
What the move looks like
WordPress is the most likely source to have a hidden dependency break at cutover, so the flow is careful, with a couple of weeks on a subdomain before the root domain moves.
- Hour 1-2
Scrape and ingest
You give the AI your live WordPress URL. It scrapes pages, posts, images and metadata from the live site. Nothing reads WP-JSON or a WXR export, so what is on the public pages is what comes across.
- Hours 3-8
Drafts, then fine-tune
Drafts of every page and post appear in Giant Context. You review and adjust. Large blogs get spot-checked in batches, not read post by post.
- Day 1
Content approved
Pages and posts approved and live at a staging subdomain Giant Context provisions for you. WordPress stays fully live throughout.
- Day 2-15
Subdomain cutover
Point a subdomain like new.yourdomain.com at Giant Context and live with it for two weeks. WordPress edge cases often take a week or two to surface, which is why the window is longer than for other platforms.
- Day 15-21
Root domain cutover
Update your A, AAAA or CNAME records at your registrar. If Cloudflare sits in front of WordPress, update the record there and purge the cache. WordPress stays up as a fallback, and a DNS flip back takes minutes.
- After 14 days
Retire the old install
After a confident week or two, cancel the hosting plan (download a full backup first) or downgrade to the cheapest tier as an archive. Cancel any annual plugin licenses before the next renewal.
How each piece moves
Everything lands as a draft you approve
Your migrated pages and posts don't overwrite the live site. They arrive as drafts. You read them, fine-tune the ones that need it and approve. For a 500-post blog, you review a sample across the archive rather than reading every post, and the rest pass through with spot-checks.
What doesn't carry over
WordPress's strength is its huge library of plugins, and most of them don't have a Giant Context equivalent. Read this part carefully before you start.
WooCommerce. If your WordPress is an ecommerce store, this migration isn't for you. Giant Context does not do ecommerce.
Membership, community and course plugins such as LearnDash, MemberPress, BuddyPress and bbPress. Not supported today. If these are core to your site, stay on WordPress.
Form plugins with complex logic. Gravity Forms, Contact Form 7 and WPForms are rebuilt as forms, but conditional logic and WordPress-specific integrations may not come across cleanly. Advanced Custom Fields with deep nested relationships may need manual restructuring.
Heavy theme code and plugin-specific features. Event calendars, listings directories and thousands of lines of custom PHP don't have a Giant Context analog. The AI recreates the visual design. Programmatic behavior has to be reimplemented. Page builders like Elementor and Divi transfer as the rendered outcome, not their internal editing structure.
Two things to check before you start. Caching plugins can serve stale content, so flush the cache before scraping, and sites behind aggressive Cloudflare bot protection may need the AI's user agent allowed through. The only migration tooling is the scrape. There is no one-button migration, no WP-JSON pull, no WXR import and no automatic flagging of changed posts, so the migration runs on live-URL scraping with manual review. For plugin-heavy sites, the first conversation is whether this migration is even the right move.
What it costs, compared
WordPress bills you for hosting and plugin licenses. Giant Context bills you for the AI doing the writing, and hosts the site too.
WordPress | Giant Context | |
|---|---|---|
Hosting and plugins | $30-200/mo when amortized, covering managed or shared hosting plus premium themes and plugins for SEO, forms, caching, backup and security. | About $11/mo of uptime for the live site, knowledge base and custom domain. SEO, sitemaps, robots.txt and schema are built in, with no plugins to license. |
Writing the content | A copywriter or agency on top, billed separately. WordPress hosts the posts. It doesn't write them. | About $50-150/mo of AI usage at a typical cadence. The AI writes the posts and pages. |
Total | $30-200/mo, plus whoever writes the content. | $60-160/mo, including the writing. |
Start with the URL
Give the AI your live WordPress address and it comes back with drafts of every page and post. Nothing goes live until you approve it, and WordPress stays up as a fallback throughout. If your site leans on plugins, ask in chat first. The answer might be to stay put.