Our methodology

Advice is cheap.
Evidence is useful.

Every published playbook is built from primary documentation, an explicit operating profile, recorded version targets, and checks that produce evidence. “Tested” is reserved for routes with recorded hands-on validation.

01

Define the profile

We state the site, publication, or account size and the access assumptions behind every estimate.

02

Inventory the loss

Every feature is marked clean, partial, manual, or lost before the procedure is written.

03

Review, then test

Two independent agents can verify documented claims and promote a route to “reviewed.” “Tested” still requires recorded hands-on validation with representative data.

04

Capture proof

A migration is complete only when the blocking checks pass and the required evidence is recorded.

Review policy

Versions are part of the answer.

Each guide displays its platform profiles, documentation or test date, review window, status, and source list. “Reviewed” means a research agent and an independent verifier checked the route against its cited primary documentation with no unresolved blockers. “Tested” is reserved for recorded hands-on validation. “Needs review” means that documentary review is incomplete, blocked, or no longer current.

Affiliate disclosure

Recommendations do not buy conclusions.

Some destination links may earn migrating to a commission. Affiliate relationships are disclosed beside the recommendation, never change loss or risk ratings, and never hide a safer non-affiliate option.