I have always thought "Sprint 0" a stupid name for something that can very rarely be time boxed.

My advice to teams is to do enough in that thinking phase (in terms of identifying requirements, architecture, technology constraints etc.) to avoid making big, expensive mistakes; you'll make plenty of small ones later on. If your thinking surfaces numerous assumptions, create PBIs to validate those assumptions and mitigate risk early.

Then start.