Salesforce allows 500 custom fields per object on Enterprise Edition and 800 on Unlimited and Performance; Professional allows 100. Type your edition, a field count or the error you hit, and the tool above gives your edition's number, the hard limit and who can raise it.
How to read the result
Name an edition and the verdict answers for that edition; without one, it checks your count against every edition and says which ones it fits. The rows under it show the limits that sit beside the main one: the hard limit per object, custom fields on activities, lookups, master-detail, roll-up summary and external ID fields.
Some fields count for more than one. Compound fields such as geolocation and custom address fields each count as several custom fields, so an object can run out sooner than its field list suggests.
To see where an object stands, open Setup, then Object Manager, pick the object and open Object Limits. The Custom Fields row shows how many you use and how many your edition allows.
When an object is full
Salesforce Support can't raise your edition's custom field limit; only a higher edition does. So the fixes are on your side: delete fields nobody uses, move rarely used data to a related object, or merge fields that hold the same thing in different places. Lookups have a separate cap, and that one Salesforce Support can raise on request.
Before a sync or an import adds fields, plan them. A field you add to match records on import, an external ID, counts toward its own limit as well; upsert or update explains when you need one. A sync that writes many fields at once also spends API calls, so check the API rate limits for your edition too.
If the new fields would hold enriched data, try the columns in a table first. In Oneprofile you shape each enriched column in a table and write only the ones you keep to the Salesforce field you pick, so no field is created for a column you end up dropping.
