Enterprise · Platform history

Platform migration data

We have tracked online stores since 2017, and our platform history goes back to 2013. 2.2M European stores have platform history and 86,255 have a detected platform change; changes detected since mid-2025 come with the date we saw them. Find merchants worth reviewing for migration, integration or sales opportunities.

A detected platform change is a reason to investigate, not confirmation of a completed migration.

Synthetic example — proposed report format

Domain: merchant.example
Earlier snapshot: Platform A detected
Later snapshot: Platform B detected
Snapshot dates: included in the agreed report
Observation dates: included where available
Interpretation: review the detected difference
Commercial relationship: not verified

Agree the comparison before ordering

1. Choose the population

Define markets, categories and the platforms to compare. Historical availability and coverage are checked for that scope.

2. Review a sample and scope

Agree before/after values, snapshot dates, available observation dates and merchant context. Source URLs are included only where available and explicitly agreed; a URL documents an observation, not a commercial contract.

3. Investigate candidate changes

Use the agreed file to prioritize account research. Missing observations, website changes and detection coverage can affect differences between snapshots.

For custom datasets, we agree the available fields, scope, price, permitted use and delivery date before purchase. Coverage varies by field and market. A missing payment or carrier signal means we did not detect it, not that the merchant does not use it.

Example scenario — illustrative workflow, not a customer case study

Investigate a possible platform migration

A software vendor reviews stores that changed platform in its markets, checks the merchant websites and prioritizes accounts that fit its integration requirements.

This describes a possible workflow, not measured customer results.

Questions before ordering

How often is the underlying data updated?

We rebuild the searchable index typically every 2–4 weeks. Observation dates vary by source and field; a rebuild does not mean every website was observed again. Delivery dates and any recurring schedule are agreed separately for your project.

Does a missing platform mean the merchant left it?

No. A missing observation can reflect a page change, a failed observation or a detection gap. Verify candidate changes before treating them as a migration.

Is this included in a self-service subscription?

Platform migration datasets require an Enterprise agreement. We confirm historical availability, fields, format, permitted use, price and delivery before purchase.

Do you verify checkout operation or transactions?

No. These reports compare observed website signals and available history. They do not verify purchases, checkout availability, parcel volumes or provider contracts.

Unlock full access to ShopRank

Login now to explore merchant intelligence including:
  • Merchant size bands and scoring
  • PSP, carrier, and technology filters
  • Exports, saved lists, and API access
By login to our system you are accepting Terms & conditions and Privacy Policy