Learn how to design and create a data model that reflects how you operate.
A data model is the structure that defines how information is organized in your CRM. It determines what objects exist (like companies, people, or deals), what properties they have (those are the fields), and how they relate to each other. You can think of it as the map of your customer data.
Every business works differently. Being able to fully customize your data model means you can shape Twenty around your processes instead of forcing yours into a rigid system.
Twenty offers the flexibility you need to shape the data model that will best support your day-to-day. You can create as many custom objects and fields as you need - the price won't change.
There is rarely only one way to build a data model. Below are a few tips to help you build yours.
1. Start with your core objects.
Identify the main things you work with (e.g. Companies, People, Opportunities). Those are already available as they are used very often. But think of any other you might need.
2. Use fields for variations, not new objects.
If something is just a characteristic of an existing object (e.g. “Industry” for a Company, or “Status” for an Opportunity), make it a field. Fields are best for categories, labels, and attributes.
3. Create a new object when it stands on its own.
If the concept has its own lifecycle, properties, or relationships, it usually deserves an object. For example:
These go beyond a single field because they carry their own data and relationships.
4. Create an object when the number of related records is open-ended.
If something can be linked multiple times and you don’t know how many, it’s better as its own object. For instance, instead of creating fields like “Product 1,” “Product 2,” etc., define a Product object and relate it to the original record. This way, you can support one, two, or a hundred products without changing your model.
5. Keep it simple first.
Start with fields. Move to new objects only when you feel the limits — too many fields, repeated records, or relationships that don’t fit neatly.
Person Type
. Avoid creating a Partner object, since you wouldn’t be able to access email threads from it. Instead, create different views under People — one showing Partners, another showing Prospects.Person Type = Partner
. That’s okay — you can hide this field from views where it doesn’t matter.Ask yourself:
If the answer is “yes” to one or more of these, it’s probably time for a new object.
Our team can assist you designing and creating the data model you need. Discover our Onboarding Pack here.
Settings
.As an open-source company, we welcome contributions through Github. Help us keep it up-to-date, accurate, and easy to understand by getting involved and sharing your ideas!