Custom Object

What it is

Standard CRM objects — company, contact, deal, ticket — cover most B2B selling. A custom object is one you define when your business has a durable thing those four cannot represent: a subscription with its own term and renewal date, a property, a vehicle, a legal matter, a shipment.

When it is justified

• The thing has its own lifecycle, independent of any single deal.

• It has attributes nothing else owns, and stuffing them onto a deal would distort the deal record.

• You need to report on it directly, not merely as a field on something else.

• It relates to several other records at once — one subscription spanning many contacts, for instance.

When it is not

If the answer is a handful of extra fields on an existing object, use the fields. A custom object introduces its own permissions, its own associations, its own reporting surface and its own migration problem later. The cost is not the creation; it is that every integration, report and automation downstream now has one more shape to know about.

The governance point

Custom objects are where CRM complexity compounds fastest, because each one invites custom properties, which invite custom workflows, which invite custom reports. Create as few as the business genuinely requires, and write down why each exists — the person who inherits the portal will otherwise have no way to tell a deliberate design from an accident.