CRM Naming Conventions: Keeping Company and Deal Names Clean
CRM naming conventions are a short written rulebook. It says how every company, person, deal, project and tag gets named, so search, filters and reports give you one clear answer instead of five partial ones. Adopt the rules below and a small team can stop guessing which record is the right one.
Table of Contents
Why CRM naming conventions decide whether you can find anything
Without CRM naming conventions, search and reporting break, because the same thing ends up stored under different names. You’ve seen it. One client shows up as “Baker Logistics”, “BAKER LOGISTICS LTD” and “Baker - Tom”, and the deals are titled “offer”, “new deal” or “call John”. Search misses any record spelled differently from what you typed. Pipeline reports split one client into several rows. And a colleague who can’t find the existing record? They just create a new one, so the mess keeps growing. Below is a ready rulebook you can agree on in one team meeting.
How should you format company names in a CRM?
Use the legal name as the record name and put the trading name or brand in a separate field or note. The legal version comes from invoices or the company registry. The brand is what your team actually calls the client day to day. Both need to be searchable. Decide these once and stick to them:
- Legal form suffixes such as Ltd, GmbH or Sp. z o.o. are written one way only, every time.
- Normal capitalization. Never ALL CAPS.
- No city, no contact person, no labels like “NEW” or “OLD” in the company name.
- Branches and subsidiaries get one fixed pattern: parent name plus location, for example “Baker Logistics - Leeds”.
If some clients already exist twice, don’t start renaming yet. First work through the separate guide on deduplicating contacts safely.
Rules for person names and consistent contact data
First and last names go in separate fields, spelled exactly the way the person writes them. Titles and job roles get their own fields too. Keep diacritics and native spelling, so “Łukasz Wójcik” never turns into “Lukasz Wojcik”. Nicknames and notes like “John from accounting”? Not in the name field. Emails go in lowercase, phone numbers in one international format, which is what lets records match on import. EpicCRM imports contacts from CSV, XLSX and Fakturownia, and in practice cleaning names in the source file before the import costs far less than fixing them afterwards. While you’re choosing required CRM fields, decide which contact details can never be left empty.
Naming rules for deals: client + what + month
Every deal follows one pattern: client, then what’s being sold, then month and year. For example “Baker Logistics - website redesign - 2026-10”. The client name makes the deal show up in search. The scope tells two parallel deals with the same client apart. The date helps with renewals and period reports. Here’s how to name deals in a CRM:
- Use the short client name the team has agreed on.
- Describe the product or service in two to four words.
- Write the date as YYYY-MM.
- Separate the parts with a plain hyphen.
- Never put the stage or status in the name.
So “offer” becomes “Baker Logistics - fleet software licence - 2026-11”, and “new deal” becomes “Mill & Co - bookkeeping support - 2026-10”. Stage, value and owner live in the pipeline fields. And “Call John”? That’s a task, not a deal.
Project, task and tag names that stay readable
Projects copy the deal pattern, tasks start with a verb and an object, and tags come from a short fixed list. That’s basically it. A project should mirror the name of the won deal, so the history from sale to delivery links up without anyone digging. Task names combine verb, object and client, like “Send contract draft - Baker Logistics”, while due dates and assignees sit in their own fields.
With tags, pick singular or plural once, keep everything lowercase, and don’t let synonyms like “vip” and “key client” live side by side (they always multiply if nobody’s watching). Tags in EpicCRM are configurable, so an admin can keep the approved list tidy. If an attribute needs a value rather than a label, think about custom fields or tags before you add anything new.
Who owns the rulebook and how do you enforce it?
One named person owns the CRM data standards. They keep the one-page rulebook and approve new tags. Keep the document short, heavy on examples and light on theory, and pin it wherever the team works every day. Conventions only hold if the team is disciplined, so my advice is to build them into onboarding, look over recently created records briefly once a month, and correct mistakes gently in comments. No public shaming. Roles and permissions can limit who creates tags or edits key records, which cuts down drift. Any change to the rules gets announced and dated. Never applied silently.
Fixing old records gradually without stopping work
New records follow the rules from day one. Old ones get cleaned in small batches, starting with active clients and open deals. Archived records can wait until someone opens them again. Export your data and variant spellings of the same company jump out in a spreadsheet, so you can fix names in one pass. True duplicates go through the separate merge guide. Stopping duplicates from then on comes down to one habit: search by legal name before creating anything. CRM naming conventions pay off when the whole team applies them consistently and the owner keeps the rulebook current.
FAQ
Should the CRM store the legal name or the brand name?
The legal name goes in as the record name, since it matches invoices and registry data. Put the brand or trading name in a separate field, so both versions find the record in search.
What is a good format for deal names?
Client, scope, then YYYY-MM, separated by plain hyphens, for example “Baker Logistics - website redesign - 2026-10”. Stage, value and owner stay in the pipeline fields, not in the title.
Do we need to rename all old records at once?
No. Start with open deals and active clients, then fix the rest the next time someone uses them. New records follow the rules from the first day.
