I’m a former junior software developer who recently transitioned into running my family's business. Right now, literally every record is kept via pen, paper, and physical registers. It works, but it's wildly inefficient, completely un-queryable, and doesn't scale.

I want to build a digital system, but I am terrified of breaking what already works. When I sat down to map out the data model, the scope exploded. Tables and fields multiplied fast, and I quickly got overwhelmed trying to ensure the model would support future business questions without painted-in corners.

The Hurdles:

• Scope Creep: Simple CRUD apps are fine, but modeling an entire, intertwined legacy business is causing massive analysis paralysis.
• Fear of Failure: Since it's production for a live business, an incorrect schema choice could actively hurt day-to-day operations or result in missing data down the line.
• Lack of Advanced Practice: I can design basic relationships, but I lack confidence in advanced, production-grade domain modeling.

My Questions for the Community:

1. How do you approach modeling a messy, real-world domain from scratch without getting overwhelmed by the sheer volume of tables?
2. Are there any specific frameworks, books, or resources that bridge the gap between "beginner textbook database design" and "production-grade enterprise modeling"? (e.g., Database Design for mere mortals ?)

Appreciate any advice from folks who have transitioned legacy businesses or designed complex domains solo!

Planning on buying the next AW but wanna know how well it integrates with the google health app, already have a Google One subscription so want to use the Google health app with the AW.

Any Sync issues or any minor bugs ?

From what I have read, the app can read the data from Apple Health fine, so hoping there will be no issue ?