Inventory the screens before anyone picks the destination SDK

A surprising amount of a migration calendar is spent on vendor calls. The SDK will matter, but it does not tell you what ‘Home’ is called in the current Android flavour, or that the iOS client still has a webview whose title never reaches the analytics property.

We start with a screen list taken from the live app, not from Figma. Product files drop flows that still ship. Support still gets tickets from those screens. If a screen is reachable, it either emits a name you can find in the property, or it is already a hole. Both facts belong in the baseline.

Only after that list exists is it useful to ask what the destination SDK can send. Some vendors cap custom events. Some rewrite screen titles. Some refuse Malay characters in event names. Those constraints are easier to absorb when you already know you have forty-two screens and eleven of them are named in a language the new property will reject.

Teams that reverse the order — SDK first, inventory later — spend freeze week renaming things under pressure. The inventory is unglamorous and it is the one artefact we have never regretted asking for early.