Methodology

How the comparison data is built

The comparison pages show two kinds of fact: what a migration from a competitor actually imports, and what that competitor charges. This page says exactly how each kind is collected, and nothing more than that.

Rows we could not verify are shown as "not yet verified". We never fill a gap with an estimate.

The dataset currently holds 12 competitors, 126 import rows and 29 price rows. Last updated 2026-10-17.

Import coverage

For each competitor and each type of content (posts, pages, tags, authors, media and so on) a row records two separate facts. First, whether the competitor's own export contains that content, taken from the competitor's own documentation and linked as the source with the date we read it. Second, whether the VeloCMS importer brings it in: imports, partly, not supported, or not applicable.

Every row that says VeloCMS imports something points at a function in our importer code. Before the data can be published, a check confirms that the named function still exists in the named file. A row has no such pointer only when it says VeloCMS does not import that content.

Each row carries the date it was last confirmed against the code. Where we have not yet read the competitor's export documentation, the cell reads "Not checked yet" and makes no claim either way.

This is a statement about what the code does, not a test run against a live account at the competitor.

Price facts

Each price is copied as the competitor shows it on its own pricing page. Every figure carries that page's URL and the date we read it. We do not use review sites, aggregators or third-party summaries.

We do not convert currencies. A price is shown in the currency the competitor lists it in, and the billing basis (monthly, or annual billing shown per month) is stated next to it.

Where a competitor's page gave no number we could use, such as quote-based pricing, or where we have not yet read the page, we show "not yet verified" or no table at all. We do not estimate.

A price fact expires after 120 days. A fact older than that fails our publishing check, so it has to be read again from the competitor's page before the data can ship.

VeloCMS list prices come from our own plan definitions, so the two sides of a comparison are always the same date.

Performance

We do not publish a speed comparison against other platforms yet, so none appears in this dataset. The only performance figures we publish are about VeloCMS itself, with their method and date, on the performance page.

See our own performance figures

Download the dataset

The same rows that appear on the comparison pages are available as one JSON file. It carries the source URL and the date for every fact. It does not include the audit notes we keep internally.

Download vs-evidence.json

Last updated:

SHA-256 checksum

b508d50fbbdae2892d285c1e63d082036fdcc81a3c25a020727e0a74cbe530cb

To check your copy, compute the SHA-256 of the file and compare it with the value above.

See the comparisons this data supports.