Migration Checklist

A sequenced cutover plan. Each step is independently safe — stop at any point and remain fully supported.

1
Inventory your usageGET /usage
Check usage per endpoint to learn what you actually call — especially whether Person Search appears anywhere.
2
Point test at /v3/
Flip your test environment integration suite to /v3/ paths. Mock responses have full v3 parity, so failures here are real findings. Discover is the one area where a path swap alone won’t pass — its request body is reshaped.
3
Adopt additive fields
Wire confidenceScore gating, isCurrent, and staleProfile handling — the highest-value v3 wins.
4
Migrate Search → Discover
Use the query mapping table. Hard deadline: January 31, 2028.
5
Flip live traffic
Endpoint by endpoint, behind a config flag. Both versions share credits and rate limits, so there’s no billing cliff.
6
Monitor deprecation headers
Alert on Deprecation: true in responses to catch any code paths you missed.