Custom Fields and Entities in CRM: Tailored to Your Process
An off-the-shelf CRM knows that a client has a name, a phone number and a deal. But a furniture maker has order dimensions, an agency has a contract and a project deadline, and a wholesaler has suppliers. If there's no place for this in the CRM, the data drifts back to Excel and notebooks. In emyCRM, you can add your own fields to a card, and for things the CRM doesn't have at all, create your own entity — no developer needed.
Contents
- New
- Negotiation
- Invoice sent
- Paid
Field types
| Field type | Example |
|---|---|
| Single-line and multi-line text | Contract number, the measurer's comment |
| Number and money (amount + currency) | Floor area of the site, the client's budget |
| List (single) and list (multiple) | Acquisition channel, services of interest |
| Date and date + time | Measurement date, warranty end date |
| Checkbox | Has a contract, needs delivery |
| URL, email, phone | Partner's website, accountant's email |
| Link to an employee | Measurer, installer |
| Link to a CRM record | Contract on a deal, supplier on a product |
| File | Passport scan, drawing, up to 100 MB |
A field has a hint, a default value (for a date, “Today”), the “Required” and “Multiple” checkboxes, plus “Show in the list” and “Show in the filter” — with these, you can filter and sort records by the field. Built-in fields can be configured too: you can rename them and make them required.
How to add a field
- Open “Settings → Fields & entities,” the “Fields” tab, and choose a CRM section — for example, “Deals.”
- Click “+ New field,” choose the type, enter a name and, for a list, its options.
- Put the field on the card: on the card, click “+ Pick a field.” A field created in settings doesn't appear on cards by itself, so that cards don't get cluttered for everyone.
- It's faster to do it right from the card: “+ New field” there adds the field to the card view you're working in.
Fields are grouped into card sections: “General” is always there, and you add the rest as needed — “Measurement,” “Delivery,” “Documents.” Card views can be personal, shared or assigned to a department: a sales rep and an accountant can see the same deal differently.
Required fields by stage
A field can be required at all times, or only from a certain stage onward. In the pipeline settings, open “Required fields by stage” and mark the stage from which your field is needed: for example, “Contract amount” from the “Invoice sent” stage. Further down the pipeline, the field is required automatically, you can't skip the stage, and when a deal moves, the CRM asks you to fill in what's missing right in the window. This way, the head of sales gets completed cards, not promises to “add it later.”
Stage marks work in deals, invoices and custom entities, and each pipeline has its own. More on stages in our article on the sales pipeline in CRM.
Custom entities: when fields aren't enough
A field describes a property of a record, while an entity is a separate object with its own history. If you have contracts, projects, properties, vehicles or suppliers that live longer than a single deal, they need an entity of their own.
- Creating one: “Settings → Fields & entities,” the “Entities” tab, “+ New entity.” Enter a name, tick “Show in the CRM menu” and, if needed, “Kanban board.”
- Card and list: just like companies — custom fields, columns, filters, search, import and export.
- Kanban: with the stages “New,” “In progress,” “Won” and “Lost,” which you can rename and add to. Required fields by stage and robots work here too.
- Relations: with “Relate to entities,” a contract is linked to a company or a deal, and their card gets a tab with contracts.
- Permissions: in roles, the entity has its own group — read, add, edit, delete, import and export — with a scope from “Own” to “All employees.”
A workspace can have up to 20 active entities, and the limit doesn't depend on your plan. How to give people access to them is covered in our article on CRM roles and permissions.
Emy AI will set it up for you
The administrator can ask Emy AI: “Add a ‘Measurement date’ field to deals” or “Make ‘Contract number’ required from the ‘Invoice sent’ stage.” Emy shows a “before → after” card and makes the change only after you click “Confirm.” Emy adds fields to deals, companies, contacts and leads, but it doesn't delete anything or create entities. By default, only the administrator can do this; other employees get access in “Settings → Emy AI access.”
Where to start
- Write down what your sales reps currently keep in notebooks or Excel outside the CRM.
- Turn properties of a deal or a client into fields, and separate objects into entities.
- Make the fields you can't issue an invoice or close a deal without required from the right stage.
- Show key fields as columns in the list — that makes reviewing easier for the head of sales.
If your data is already in a spreadsheet, you can import it along with your custom fields — step by step in our article on importing clients from Excel.
Do I need a developer to add a custom field?
How many custom fields can I add?
How is a custom entity different from a field?
Can I make a field required at only one stage?
Can I change a field's type after creating it?
Tailor the CRM to your process
14 days free on the “Standard” plan. No card required.