Notes Not Working in Salesforce Starter? It's Chatter, and There's No Switch

CWT Studio · July 2026

If you found this page, you likely typed something like "Salesforce Starter notes not showing" or "cannot create notes Salesforce Starter" into a search bar late at night, and the results gave you nothing. I ran the same searches during a client migration last week and assembled the answer from three separate Salesforce documents that never mention each other. This post puts them in one place, with the receipts.

The short version: the Notes feature in Salesforce Starter depends on Chatter. As of the Summer '26 release, Salesforce ships every new org with Chatter turned off, and Starter provides no way to turn it on. A Starter org created after roughly June 2026 cannot run the modern Notes feature, and your org is behaving exactly as Salesforce currently ships it.

The long version follows, because the reasoning is what saves you the hours.

The symptoms

The problem announces itself through some combination of the following:

• The Enable Notes checkbox in Setup, under Notes Settings, is checked and has no effect.
• No Notes section appears on any contact, account, or opportunity page, even after the Notes related list is added to the page layout.
• Loading notes through the API or Data Loader as ContentNote records, the .snote method every migration guide describes, fails on every row.
• Searching Setup's Quick Find for "Chatter" returns No matching items found.
• The direct URL to Chatter Settings (/lightning/setup/CollaborationSettings/home) returns Page not found. The page you requested was not found, or you do not have permission to view this page.

Each of those is the same underlying condition surfacing in a different place.

The cause, assembled from three sources

No single Salesforce page states the problem outright, so the diagnosis requires putting three documents together.

Source one. Salesforce Knowledge Article 000383410, "Users unable to use the enhanced Notes related list," states that the modern Notes feature functions only when two conditions hold at once: the Notes related list sits on the page layout, and Chatter is enabled. The modern Notes system is built on Chatter's content engine, which means the feature inherits Chatter's availability. This dependency has existed for years without drawing attention, because Chatter has been on by default in every org since the feature shipped.

Source two. The Salesforce Summer '26 release notes announce that, beginning with that release, Chatter is turned off by default in all new orgs. For features that require Chatter, the notes direct administrators to Setup, Chatter Settings, and the Enable checkbox.

Source three. A Starter org, where that instruction cannot be followed, because the Chatter Settings page is absent from Starter. Quick Find returns nothing and the direct URL returns Page not found, which establishes that the edition removed the page outright.

Assembled, the three sources describe a platform-wide decision that larger orgs can reverse with one checkbox, applied to the one edition that lacks the checkbox. Any Starter org born after the Summer '26 release came into the world with its notes engine permanently dark, while an org created a month earlier works normally. The difference between the two is the org's creation date.

What fails, so you can skip it

I worked through the plausible paths in order, and each one ends at a documented wall.

Attempt one: load notes as ContentNote records. This is the standard method for note migration, inserting ContentVersion records with a .snote file extension. On an affected Starter org every insert fails, because ContentNote belongs to the Chatter-dependent content system, and the state of the Enable Notes checkbox has no bearing on an engine that is absent.

Attempt two: load notes as classic Note records. Salesforce still carries the Note object from the pre-Chatter era, and those records insert successfully. Two constraints govern the attempt. The classic Note object lacks Bulk API support, so Data Loader must run in SOAP mode to avoid the error "Async API not enabled." The decisive constraint appears after the load: the records exist and nothing displays them, since Starter's Lightning record pages omit the Notes and Attachments related list and the edition withholds the Edit Page option that would add it. Ten thousand classic notes can load cleanly and remain invisible to every user, and records the team cannot see create an audit liability with no working feature attached.

Attempt three, the one that holds: a Legacy Notes field. Create a custom field on Contact, type Long Text Area, maximum length 131,072 characters, then concatenate each contact's note history into that field as dated entries, newest first:

[2024-03-11] Moved to the in-house team at the client
[2022-01-21] was @ the agency downtown
[2019-06-02] Met at the trade show, prefers email

A standard Data Loader upsert against an external ID carries it in. The field displays on the contact page unconditionally, because ordinary custom fields are among the things Starter renders without argument. The contents are reachable through global search, and the approach depends on nothing that a future release can switch off, which after this episode is a property worth paying for.

Run the numbers on your data before committing. In the migration that prompted this post, roughly 23,000 contacts carried about 98,000 notes between them, and the largest single contact's combined history stayed under 37,000 characters, comfortably inside the limit. Confirm your own maximum first, and where a handful of contacts exceed it, truncate the oldest entries or split the overflow into a second field.

The honest tradeoff

The notes become one dated list per person with no individual clickable records, which surrenders per-note authorship display and per-note sharing. For most small teams, whose notes serve as quick context on who a person is and what happened last, the dated list reads faster than a related list of forty separate records, and the tradeoff still deserves to be named to your team in plain terms.

A later move to Pro Suite or above brings Chatter and the modern Notes feature with it, at which point the contents of the Legacy Notes field can be migrated into real note records. The field is a bridge built on the one piece of ground Starter guarantees, and it remains passable in both directions.

The bigger lesson about Starter

This episode is Starter in miniature. Starter is the full Salesforce platform operating behind a permission mask, and the mask works by omission: settings pages for withheld features do not exist, and the error messages their absence produces never mention your edition. Debugging it resembles archaeology, inferring buried infrastructure from surface failures, while documentation written for the full platform describes switches your org has never had.

The same platform underneath is what makes the workaround possible. Real Data Loader, real custom fields, and real external IDs all function on Starter, and together they route around most of what the edition withholds, provided you know where the fences actually stand. Mapping those fences is the purpose of this post.

The constraint is documented as a hard wall. In practice, it is a line that can be built around, once you locate it accurately.