How it works
The estimator combines five inputs — source platform, destination, custom event count, custom dimensions, and team size — with four flags (e-commerce, CAPI, BigQuery export, Consent Mode v2). It returns a phased breakdown of audit / map / dual-tag / cutover hours plus a risk band based on the combinatorics of your stack.
Why estimates differ
Most blog estimates assume a single domain with no e-commerce. That’s rarely real. The estimator surfaces three things blog posts skip: parallel-run cost (always underbudgeted), CAPI work for ad platforms (huge swing), and BigQuery archival (often forgotten until the last week). Calibrated against migrations from GA4 to Plausible, Matomo, PostHog, Fathom, and Umami.
What the report tells you
Hours per phase, weeks at your team size, cost band at 0–60 blended dev rate, risk level, and a list of flags that surface common pitfalls. Copy as plaintext — paste into your project tracker.