What kind of review this is
phone-to-phone.com publishes documentation-first reviews. For each tool we read the vendor's own feature documentation, licence terms, refund policy and store page, then score what the documentation commits to on the record. Where we have run a tool ourselves, the review says so in the text.
We do not invent benchmark numbers, we do not claim hands-on testing we did not do, we do not add rating aggregates we did not compute, and we do not publish a "speed score" without a stated transfer size and device pair. Where a page relies on vendor documentation alone, it says so at the top of that page.
The four dimensions
Each is scored 0–10, then weighted equally into the final score.
1. Data coverage per direction (35%). We score each of the four migration paths separately — Android→Android, Android→iPhone, iPhone→Android, iPhone→iPhone — against eleven data types: contacts, SMS, call logs, photos, videos, music, documents, apps, calendars, bookmarks, books. A tool that is complete in one direction and empty in another scores in the middle, and the review names the gap.
2. Setup friction (25%). Cables, computers, permission prompts, whether the target phone must be factory-reset, and how many decisions the user has to make. A tool that needs a factory reset loses points even if its coverage is perfect.
3. Licence reality (25%). The price after any promotional period, devices per licence, auto-renewal terms, refund window, and whether a cheaper plan exists for a single migration.
4. Privacy model (15%). Local versus cloud processing, read-only versus write access to the source device, telemetry and account requirements.
What we do not score
- Interface aesthetics beyond the point where it changes step count.
- Transfer speed claims taken from vendor marketing.
- Customer support responsiveness, unless it is a documented policy (refund window, support hours).
Sources
Every page lists the date the vendor's store and documentation were checked. Prices are taken from the vendor's own purchase page, not from coupon sites or resellers. Where a vendor regionalises pricing or runs a permanent discount, the page says so instead of quoting a number that will be wrong next month.
Corrections and updates
Pages are re-checked monthly. If a vendor changes a price, adds or drops a supported direction, or changes its refund policy, the page is updated and the "updated" date changes. If you find something out of date, mail editors@phone-to-phone.com and we will correct it, with the correction noted on the page.
Commercial policy
Some outbound links are affiliate links. They never affect a score, a ranking position, or whether a tool is recommended. We score first, monetise second — and a tool we do not recommend does not get a "best of" placement because it pays better. Any page carrying affiliate links says so at the top.
What we have actually run
Eight Windows tools have been through our bench, and the raw numbers — detected versus transferred item counts, run times, connection failures — sit in the hands-on section of each of those reviews rather than in a separate log. The two tools we could not run end to end say so in the review itself. Where a review is documentation-based rather than measured, it says so in a section called "Where the evidence comes from".
That distinction matters more than it sounds. A coverage table copied from a vendor's feature page is a claim; a run with a stopwatch and a count on the target phone is evidence. We are moving every review toward the second category, and we publish the ones still in the first rather than hiding the gap.
What we cannot tell you
Whether a specific tool will work with your specific phone, carrier firmware, corporate MDM profile or unusual Android skin. No review can. That is why every review ends with the vendor's own compatibility list, and why we recommend a free trial before paying wherever one exists.
On vendor testimonials
We do not use testimonials published on a vendor's own site as review content or as evidence. They are curated by the seller, cannot be verified, and usually have no date or device context — which makes them marketing copy, not user experience.
Where a product cannot be tested (paywalled builds, no public download), the review says the evidence is documentation-only and the score is capped. If enough independent user reports exist elsewhere — app store reviews, Trustpilot, forum threads — we summarise the recurring themes and name the source, labelled as user-reported rather than measured. Quotes are attributed, never blended into our own voice.