Help for owners
Notion has become my business system and it is straining
Short answer
Notion is built for documents and light databases. Used as a CRM or order system, the limits that appear are its API request limits, 429 errors from integrations, limits on relations and rich text, and weak control over who changes which record. Back up the data, find which workflow hurts, and move only that part to a proper database.
Does this sound like your situation?
- Notion databases take a long time to open since they grew.
- An integration or automation reading Notion fails with a rate limit error.
- Anyone can change records that should be controlled, such as prices or order status.
- Reports from Notion need manual copying into a spreadsheet.
- I need customers to see or update some of the data and Notion does not fit.
Why does this happen?
Automations and integrations hit request limits
Notion's API allows 600 requests per 60-second window per connection on Business and Enterprise plans, and 180 on all other plans. Going over returns an HTTP 429 rate limited error, and the workspace also has a shared limit across connections. Loops over many records hit this quickly.
Confirmed by developers.notion.com
Notion limits the size of what a request can carry
A single request is capped at 1000 block elements and 500KB, a relation can point at up to 100 related pages, and text fields have character limits. Larger loads fail with a validation error.
Confirmed by developers.notion.com
Writes that time out may still have been saved
Notion's guidance says a write that returns a 503 may have been saved, so the object should be read before retrying. Without that check, retries can create duplicate records.
Confirmed by developers.notion.com
A document tool has no business rules
Notion does not enforce things like unique order numbers, required links between records or approval steps the way a database with an application on top can. Mistakes enter quietly.
Reporting needs structure
Totals across tables, history and filters over many records are the jobs a database is for, and they are what Notion starts to struggle with as the data grows.
What can I do about it today?
- Back up the workspaceUse Notion's export for the important databases and keep the files outside Notion.
- Name the one workflow that hurts mostOrder tracking, a customer list or approvals. Moving everything at once is not necessary.
- Check who can edit whatList who has edit access to the sensitive databases and reduce it where you can, without deleting anything.
- Note any integration that reads or writes NotionForms, automations, reporting. Ask who made them and what they need.
- Keep Notion for what it is good atDocuments, wikis and meeting notes can stay put whatever you decide.
When should I bring someone in?
- Records in Notion drive orders, payments or customer promises.
- Integrations fail often and fixes keep breaking something else.
- You need access rules or customer logins that Notion cannot give.
How do I handle it?
- Separate documents from recordsI sort the content into what is documentation, which can stay, and what is structured data.
- Choose the smallest moveOften only one database moves to a proper table with a simple screen, and the rest stays where it is.
- Import with checksData is loaded from the export and counted against the original, with a list of what did not fit.
- Keep a link to the old pagesNotion pages can link to the new system so people are not lost during the change.
- Add rules and historyThe new system enforces required fields and keeps a record of who changed what.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is Notion bad for a CRM?
Not for a small list. The strain appears with growth: more records, more integrations and a need for rules about who changes what.
What does a 429 error from Notion mean?
Notion states it means a rate limit was exceeded, and the wait time is given in the Retry-After header. Slowing the integration down or queueing requests fixes it.
Do I have to leave Notion entirely?
No. Many businesses keep Notion for documents and move only the operational records.
Will the team lose their history?
Not if the export is taken first and the old pages are kept until the new system is checked.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.