He gone.

Next year when he nets 12 goals you’ll be a convert.

A great film that I rewatch almost yearly.

I'm not going to be lumping every data source I have into one monster database to rule them all. Some databases will continue to only have a single source while others, where it makes sense, will be going the route of my CRM.

After playing with it throughout today I’m very glad I made the change. When working on the backend of my CRM I no longer have to bounce between multiple pages. Instead each main source is just a tab click away.

Third, I knew that I could undo it all very easily and go back to separate databases any time.

Fourth, I have a suspicion that this new structure by Notion is laying the groundwork for something much bigger. And on the off chance I'm right, I want to start getting familiar with this way of working.

First, the workspace I made the change on is only used by myself. I don’t have to worry about training anyone else on the new way of doing things.

Second, I was only using a single view each (within the database) for the 9 sources that I merged under that new single “CRM” database umbrella.

Yesterday I moved all 9 of the databases that were powering my CRM in Notion into a a single CRM database with 9 different sources.

I bucked the common recommendations for a couple reasons.

I can see a path forward where the new architectural layer may power some significant advances that weren’t possible under the previous structure.

By itself, I don’t see the need to shift the way I structure my current databases in my workspaces to have multiple sources contained in each. However…

Love this, exactly what I’ve been wishing for!