WordPress Migration (Leave WordPress Behind)
WordPress stays safe only if PHP, WordPress core, themes, and plugins are all kept current. Instead of a site you keep defending, we move you to one with almost nothing to defend: your current design converted to a static site served from a CDN, our own CMS when staff need to publish in-house, or a headless CMS for serious media sites. We handle backups, DNS cutover, shutting down and deleting the old WordPress, and post-migration uptime and cost monitoring.
Features
- Three migration paths: static, our own CMS, or headless
- Design and URLs preserved so SEO carries over
- Finished only when the old WordPress is shut down and deleted
- Post-migration uptime and usage/cost monitoring (monthly)
From WordPress to a site you don't have to defend.
In October 2026, critical PHP vulnerabilities were disclosed and sites across Japan scrambled into emergency maintenance. WordPress runs on PHP, so it is only safe while PHP, WordPress core, themes, and plugins are all kept current.
“We update content a few times a year, but security work comes every month.”
“There’s an old site nobody has touched in years.”
Oflight fixes that at the level of the system itself, not the to-do list.
Sound Familiar?
Even a site you no longer use can be hijacked and turned into a launchpad for attacks, and you may be held responsible as the party that enabled them.
Leaving it alone is the most expensive risk of all.
Our philosophy: energy-saving management = systems × trust²
Rather than a site you keep defending with effort, we build one with very little to defend in the first place. Combining generative AI with engineering also makes the migration itself fast and inexpensive.
| Typical WordPress operation | After migrating with Oflight | |
|---|---|---|
| Code running on the server | PHP, a database, many plugins | None in principle (static files) |
| Main attack surface | Login page, plugins, PHP | Almost none |
| Routine updates | Mandatory, dangerous if skipped | Minimal |
| Page speed | Server-side processing | Served instantly from a CDN |
| Running cost | Hosting plus maintenance fees | Mostly free or low-cost hosting |
Three destinations, chosen to fit your site
We never push a heavier setup than you need. We pick the easiest-to-defend shape that matches how often you publish and who does it.
For sites that rarely change
For: Corporate sites, shop sites, landing pages, recruiting pages, portfolios
- Your current design reproduced almost as-is as a static HTML/CSS site
- Served from a CDN such as Cloudflare Pages or Vercel
- Contact and download forms rebuilt serverless, with email, Slack, or Discord notifications
- Optional update service: send us the copy and we publish it
The safest, cheapest, and fastest option. For most corporate sites it is all you need.
For sites your staff update
For: Corporate sites where staff publish news and blog posts themselves
- A CMS developed and operated by Oflight
- Write in an admin panel; pages are exported as static files on publish
- No login screen on the public server, which removes most of the attack surface WordPress has
- Existing posts and images migrated from WordPress in bulk
For serious blogs and owned media
For: Sites with many articles that run categories, tags, search, and SEO in earnest
- Architecture designed to your needs: Cloudflare-based CMSs, or a headless CMS with static generation
- URL structure preserved, with redirect design so SEO equity carries over
- Articles, categories, and metadata converted in bulk with migration tooling plus AI
How It Works
Free assessment (30 min online)
We check your WordPress and PHP versions, plugin set, update frequency, and any unused sites, then recommend the best destination.
Quote and migration plan
Priced by page count, features, and destination. We inventory URLs, forms, and external integrations.
Backup and migration
A full backup of the existing site first, then the new environment, with a preview so you can check the look and URLs.
DNS cutover and launch
Domain, SSL, and email settings switched over with minimal downtime.
Shut down and delete the old WordPress
Once the migration is confirmed, the old site is safely stopped and removed. Only then is the risk actually zero.
Care and monitoring (optional, monthly)
Content updates, uptime monitoring, and usage and billing checks after the move.
Pricing
Migration (one-time)
| Plan | What's included | Price (excl. tax) |
|---|---|---|
| Free assessment | Current-state review, risk check, migration recommendation (30 min online) | ¥0 |
| Abandoned site cleanup | Back up, archive as static, and delete an unused WordPress site | ¥30,000 / site¥15,000 each from the 2nd site |
| Landing page migration | One-page static build, contact form, DNS cutover | ¥60,000 |
| Corporate site migration | Up to 10 pages: static build, forms, redirects, DNS cutover | ¥150,000+¥60,000 per additional 10 pages |
| Own-CMS migration | Corporate migration plus our CMS, up to 100 posts migrated, and training | from ¥300,000 |
| Media migration | Move to EmDash or similar, theme rebuild, bulk article migration, SEO handover design | from ¥600,000Quoted individually |
Monthly care
- Uptime monitoring
- Usage and billing monitoring
- SSL checks
- Minor fixes up to 30 min/month
- Everything in Light
- Content updates up to 2 h/month
- CMS maintenance
- Monthly report
- Everything in Standard
- Content updates up to 5 h/month
- Priority response
- Cost estimates before adding features
- * Hosting fits the free tier for most corporate sites. If a paid plan is needed it is billed at cost (from about $5/month).
- * Design renewals, new pages, and integrations with external systems are quoted separately.
- * Small projects are built by our founder personally; larger ones are shared with partner firms at the same price and quality standard, with Oflight responsible for acceptance. Care plans are staffed by more than one person.
Why it costs this little
Agencies typically charge ¥20,000–80,000 per page, or ¥300,000–1,500,000 per site, to rebuild from WordPress. We specialise in converting the existing design as-is rather than redesigning it, and use AI for conversion and verification, which cuts the labour dramatically.
How much cheaper is it? (10-page corporate site)
| Stay on WordPress | Migrate with Oflight | |
|---|---|---|
| Up-front cost | ¥0 | ¥150,000 |
| Hosting | ¥1,500 / month | ¥0 (free tier) |
| Maintenance | ¥15,000 / month (typical WordPress care) | ¥6,000 / month (Light) |
| Annual running cost | ¥198,000 | ¥72,000 |
| Two-year total | ¥396,000 | ¥294,000 |
About ¥126,000 saved per year. The up-front cost pays back in roughly 15 months, and you are about ¥100,000 ahead after two years. And WordPress and plugin vulnerability work disappears altogether.
Cost and usage monitoring after the move
Cloud services such as Cloudflare are usually pay-as-you-go. A normal corporate site will almost never run up a bill, but adding member features or heavy processing later can push usage past what you expected, depending on configuration.
Regular checks of usage and billing
Email or Slack alerts when a threshold is crossed
Cost impact reviewed before any feature is added
All designed in as a set, so “it was supposed to be cheaper” never turns into a surprise invoice.
Start with a free assessment
“Is our site OK?” is reason enough. Send us the URL and we will reply with the current state, the risks, and a rough migration estimate.
Request a free assessmentFrequently Asked Questions
Will the design change?
As a rule we reproduce the current look exactly. If you want a redesign at the same time, we can do that too.
Will our search rankings drop?
We keep the URL structure or set up redirects, and carry over metadata. The faster page speed also helps SEO.
Will we lose the ability to update posts ourselves?
Depending on how often you publish, choose between sending us the copy to publish, or updating in-house with our CMS.
Can we still have a contact form?
Yes. Forms are rebuilt serverless with email and chat notifications and spam protection.
Doesn't our hosting provider update PHP for us?
Even when the host updates PHP itself, WordPress core, themes, and plugins remain your responsibility. Old plugins left in place are the most dangerous case.
Do we really have to leave WordPress?
Not always. Large e-commerce or membership sites can be a good fit for WordPress. In those cases we recommend hardening and a better maintenance setup rather than migration. We never push a move that isn't needed.