Plan for a settling period of roughly a few weeks to a couple of months, treated as a working window rather than a fixed deadline. A traffic dip after a migration is normal: it reflects the time Google needs to re-crawl the new URLs, process the redirects, and re-establish signals on the changed addresses. How deep the dip goes and how long it lasts depends mostly on two things, the size of the site and the cleanliness of the redirects, so the honest framing is a range to watch, not a date to count down to.
The dip is a settling process, not a punishment. When URLs change, Google has to discover the new ones, follow the redirects to understand what moved where, and recompute how the new pages should rank. While that reprocessing is underway, rankings and traffic wobble, often down first, then recovering as the picture stabilizes. A small, clean migration with a tight redirect map can settle in a couple of weeks because there is little for Google to work through. A large or messy one, with many thousands of URLs or imperfect redirects, can take a couple of months or more, because the reprocessing is bigger and any redirect gaps slow the recovery. These are working ranges drawn from observed behavior and worth verifying against your own situation, since recovery speed varies.
What this means in practice is that the early dip is not a verdict. Judging a migration by week one is judging it mid-process, before Google has finished re-establishing the new URLs. The right move is to decide in advance how long you will give it before you treat a shortfall as a real problem.
Set a recovery window before launch, a clear span, sized to your site, during which a dip is expected and tolerated. Monitor crawling, indexing, and rankings inside that window calmly instead of reacting in the first few days. If traffic has not meaningfully recovered by the end of the window, then investigate, starting with the redirects. Until then, watch and wait rather than panicking.