Can your WordPress site move to the edge?
Enter your address and you will get one of three answers, with the reasoning attached: we can transfer this, we can transfer it with some custom work, or it is not a fit as it stands.
The scan reads your robots.txt, your home page, the WordPress
API index, your sitemap, a handful of your pages, and the theme and plugin
readme files those point to — around two dozen requests, and it keeps none
of your content. No public address? That is fine: a
repository and a database dump tell us more than a scan ever can.
How the scan knows what it knows
Most WordPress scanners read one page's markup and guess. That finds very little: on a real site we measured, 13 plugins were installed and the markup revealed one, because a plugin only appears in markup if it loads a front-end asset on the page you happened to fetch.
So this reads the WordPress API index instead, which names every plugin that
registers routes — including the ones that draw nothing — then confirms each
against its own readme for a real name and version. It reads your theme's
style.css to get the theme actually in use rather than its
parent, and it samples several of your pages so a form on your contact page
is not missed.
What no scan can reach: your form field definitions, which live in the database and have no public route at all. So the verdict is a qualification, not a plan — scoping a transfer needs the WordPress files and a database dump, both onboarding-scoped and both revocable.
Get a real assessment
A scan reads your public pages. An assessment reads the two things that actually decide a migration — your files and your database — and neither is visible from outside. What we need from them is structure: which plugins are active, which theme is running, how many pages of each kind, and what fields your forms have.
What we never take
- No database access, and no credentials. You run one command; we never connect to anything.
- Your users, comments and form submissions are never read. They are counted so we can size the job, and not opened.
- The options table is read by option name, never wholesale — that is where WordPress keeps SMTP passwords and payment keys.
- You see the file before you send it. Redaction happens on your machine, and the result is a few kilobytes of JSON you can read.
The file is checked for email addresses, password hashes, IP addresses, API tokens and raw option values before it is written — and again when it arrives. If anything like that is in it, nothing is written and nothing is stored.
Sign in. No password — we send a link that works once.
Signed in as ·
Point us at your files and database — by running this where they are.
npx edgewpsync manifest --dump your-database.sql --files /path/to/wordpressEither flag on its own works. A dump answers the database questions; a file tree answers the plugin and theme questions. Together they cover almost everything.
Read it, then send it. It writes edgewpsync-manifest.json — open it first.