Custom objects in CRM: model the records your business already uses

What custom objects are

Custom objects are record types you define beyond the default contact, company, and deal shapes. Properties, jobs, candidates, retainers, trials, matters, and viewings are common examples.

Without them, teams bury industry reality in notes and tags. With them, the CRM can speak the same nouns the business already uses in meetings.

Why custom objects matter

Filters, pipelines, permissions, and reporting only work well when important things are real records. A viewing that is only a free-text note cannot power a board of this week's appointments.

Custom objects also reduce shadow systems. When the CRM cannot hold the work, people invent spreadsheets that quietly become the real source of truth.

• Represent industry-specific work without fake deal metaphors
• Relate people to the things they buy, visit, or hire for
• Keep stages and ownership on the right record type
• Make handoffs possible when someone is out

How SchemaDesk approaches custom objects

SchemaDesk is built around a schema you can shape. Objects, fields, and relationships are first-class, so CRM templates for contacts or deals are starting points, not a ceiling.

That design matches agencies, recruiters, real estate teams, and operators whose process does not fit a single SaaS sales skeleton. You define the nouns, then attach views and pipelines to them.

SchemaDesk plans and unlimited data model

SchemaDesk has no limits on objects, fields, and records on Free and on Pro, and no fair-use ceiling. Templates are starting points only. Import CSV or Excel into any object (mapping uses existing custom fields; import creates no new fields or objects during the import). Export any list to CSV. Whole-workspace export is coming soon. API keys and webhooks are included for every team until April 2027; from April 2027 they stay on Pro.

"No limits" refers only to objects, fields, and records. It never means unlimited automations or workspaces. Until April 2027 every team gets full Pro features free (including automations and API); from April 2027 those stay on Pro.

Until April 2027, every team gets full Pro features free. Unlimited people, up to 3 workspaces per person, automations, API keys and webhooks, full history, roles and permissions, plus unlimited objects, fields, and records. In April 2027, choose Pro or move to Free forever. Billing starts in April 2027 for everyone, no matter when they joined. Teams with no plan chosen move automatically to Free forever. SchemaDesk sends notices 30, 7, and 1 day before. No data is deleted. From then, Free forever is up to 2 people and 1 workspace (unlimited objects, fields, and records; no automations; no API; 30-day history), and Pro is 10 EUR per seat per month. Anyone who joins before April 2027 can lock 5 EUR per seat per month for life while subscribed, as long as they start paying by 30 April 2027.

See SchemaDesk pricing for the full Free vs Pro table. Pro includes up to 3 workspaces per person.

Each person can hide, reorder, and group their sidebar into named sections. Objects can be renamed and given an icon from a set of 30. Home dashboard widgets cover numbers, record lists, and bar, pie, or line charts from any object, with grouping, date ranges, and filters. Widgets can be personal, or pinned for everyone by admins.

What good implementation looks like

Start with the smallest set of objects that removes daily pain. Name them the way staff already talk. Add relationships before you add decorative fields.

Resist cloning your entire company wiki into objects on week one. A clean Properties and Viewings model beats twenty half-used record types.

Common mistakes

Teams often create objects that duplicate each other, skip relationships, or require too many fields. Adoption dies, and people return to Sheets.

• Too many objects before any workflow is stable
• No clear primary record for each process
• Using custom objects where a field would do
• Ignoring naming so two teams invent parallel types