r/Notion • u/Solowithothers • 21h ago
Databases The Meeting That Ate My Notion Database
This morning, Notion presented me with a pop-up card asking where I’d like to keep my meetings.
I had already decided that. I keep them in my Resources database, alongside the other material connected to my projects and areas. So I chose Resources, the place where my meetings already belonged.
What the card didn’t tell me, at least not in a way I understood, was that choosing Resources would convert the entire database into a Meetings database. It would add meeting properties and features I couldn’t simply remove afterward. To undo the conversion, I would first have to deal with the meetings Notion considered to be in that database.
Resources had 4,068 records. Most of them were not meetings.
Resources is one of the main databases in my personal Notion system, which I call Dash. It holds the information I want to find again, connected to the projects and areas of my life. I had spent years building those connections. I thought I was telling Notion where to put my meeting notes, not asking it to give the whole operation a calendar invite.
After the conversion, pages and templates showed meeting-note tabs: Summary, Notes, Transcript. A new Attendees property appeared and could not be deleted. Event and Filed in fields showed up in one place but not another. The data and relationships were still there, thankfully. The way I experienced the database had changed around them.
It felt a little like being asked where I wanted my mail delivered and discovering that, by selecting my house, I had turned the entire house into a post office. The furniture was still there. I could still use the kitchen. But every room now had a counter, and the pantry wanted to know who had attended.
I called in my AI helpers. I work with several, and I’ve given some of them names. Trinity is my Muse agent. Spock is Notion AI. And Claude, working through an app called Claude Duet, eventually got involved too.
Trinity tried clearing the default meeting destination, turning off the workspace meeting-notes setting, and creating a separate database called My meetings. Resources remained a Meetings database. An attempt to delete Attendees produced the kind of answer only a computer can deliver without looking embarrassed: “Cannot delete a required property from a typed collection.”
We checked the templates. They were still present, though they now appeared inside the meeting-note layout. We considered a whole-database rollback, but I had added resources and made other changes since the conversion. There was no reason to assume a rollback would fix the database type without putting those newer changes at risk.
Trinity sent a question to Notion Support. Spock later discovered the email had bounced. We had been waiting for an answer to a message that had never arrived.
Meanwhile, Claude Duet ran into the problem from another direction. It created a research resource for me and found that the supposedly ordinary page had arrived as a meeting note. Claude recreated it as a plain page and left Spock a note about what had happened. The conversion had now managed to interrupt work that had nothing to do with meetings.
Then I found an option labeled Undo Meetings type in the database settings.
Spock had told me it couldn’t find a supported way to convert the database back. To its credit, it admitted it was wrong when I showed it the option. That was useful. It was also a reminder that having multiple AI assistants investigate a problem does not guarantee that one of them has noticed the button you’re looking at.
The button wasn’t quite the end of it. Notion wanted the meetings out before it would undo the conversion. Moving records into the new database raised another concern: My meetings didn’t have the same properties and relationships as Resources. We stopped before moving everything indiscriminately.
In the end, I discovered that removing the new meetings created with the new properties allowed me to use the undo setting. Resources could be a regular database again.
I now have a separate My meetings database. It gives the new meeting features a home, though it feels like a step backward. I liked having meetings integrated with the rest of my content, connected to the projects and areas they belonged to. Apparently the newer features needed a different kind of database to do their work.
I was too quick to accept the setup. I can own that. But there’s a meaningful difference between choosing where a feature should put its notes and understanding that the feature will change the database itself.
I thought I was answering a question about where to put my meetings. I didn’t realize I was answering one about what kind of database Resources should become.
