Cost calculator

Doing it yourself vs. paying a fixed price.

Plug in your migration scope and engineer rate. The calculator estimates the hours an experienced engineer spends end-to-end — research, scripting, video re-uploads, QA, cutover — and compares the labor + AWS infrastructure cost against our fixed-price tier. Numbers are conservative; first-time-through teams should multiply DIY hours by 1.5–2×.

Matches our Professional tier — see what's included.
Doing it yourself
$13,545
≈ 105 engineering hours at $125/hr = $13,125 + $420 AWS over 12 months
  • API research8h
  • Infra setup (S3 + CloudFront)10h
  • Scripting + edge cases67h
  • Video protection polish6h
  • QA + reconciliation8h
  • Cutover6h
With us
$3,420–$7,920
$3,000–$7,500 fixed-price + $420 AWS over 12 months. Deposit: $1,500, balance after staging approval.
  • · No engineering hours from your team
  • · Zero data loss (vs. roughly typed migration)
  • · 2–14 business days vs. 4–8 calendar weeks
  • · 79-point verification on the way out
You save $5,625–$10,125 and get 105 engineering hours back. The time-to-launch difference (weeks vs. days) usually matters more to the business case than the dollars do.

What's in the DIY hours estimate

The hour totals you see come from real numbers we hit on actual migrations, normalized to "experienced engineer." API research is a flat 8 hours regardless of scope — every project pays that toll before the first import runs. Infrastructure setup is another flat 10 hours: bucket policies, CloudFront with signed cookies, the mu-plugin to whitelist controlsList, key pair rotation. Scripting scales with content volume — 2.5h × courses + 0.05h × videos + 12h enrollment logic — because the bug-prone bits (cross-course enrollment contamination, hook suspension during bulk import) live in those loops. Testing scales with courses. Cutover is a fixed 6 hours: DNS, cache flush, monitor.

What it leaves out: management overhead, team meetings, the rebuilds that follow when staging-day reveals an enrollment mismatch nobody anticipated. The real DIY cost is usually higher than what this widget shows.

What's in the AWS estimate

Storage in S3 plus CloudFront egress for video delivery. The math uses ~200GB per 1,000 videos for storage and a back-of-envelope $5/100-videos/month delivery floor — accurate within ~30% for a typical course catalog with moderate viewing. Heavy-traffic catalogs run higher; cold catalogs run lower. Either way, the AWS line is the same whether you migrate yourself or we do it — we're not marking up infrastructure. Full breakdown: Vimeo vs. S3 cost analysis →