Share picklist values between Zoho CRM Leads and Contacts

Your Leads and Contacts modules both have an Industry picklist. Someone adds a new industry to Leads, then forgets to add it to Contacts. Records now describe the same thing in different ways, and reports become harder to compare.

Our original tip suggested maintaining duplicate lists or replacing them with a custom module. Zoho CRM now has a native option for shared lists: global sets. Use that option first when the values genuinely mean the same thing across modules.

Choose the right kind of field

A global set is a reusable collection of picklist values. Several picklists can use the same set, so administrators maintain those choices in one place. Zoho explains the behaviour and edition availability in its global sets overview.

Requirement	Useful starting point
The same industry or enquiry category across modules	A shared global set
Values specific to one process, such as a call outcome	A local picklist
A related item with its own details and history	A module linked through a lookup

Sharing a label does not necessarily mean sharing its meaning. A contact's relationship to your company and an opportunity's sales stage are different concepts, even if a few choices overlap.

Clean the values before sharing them

Compare the existing lists and decide which spelling and meaning you want to keep. For example, “Professional services”, “Prof. Services” and “Consultancy” might be inconsistent labels, or they might represent intentionally different categories. Resolve that with the people using the records.

Make a small mapping table of existing values and their intended replacements. Check blank values, old choices and values used by integrations. Identify reports and workflow rules that rely on those choices before changing them.

When a choice no longer fits, decide how historical records should be represented. Renaming a value and deleting a value have different effects; neither should be an accidental side effect of tidying the dropdown.

Associate Leads and Contacts with one global set

In Setup, open Customization, then Modules and Fields, and look for Global Sets. Create the approved set, then associate the relevant picklists in the Leads and Contacts layouts with it. Check the available options for your edition, permissions and field type before making the change.

For existing local picklists, review the value mapping during conversion rather than assuming every old choice has an exact match. Start with a representative field and inspect the result before changing the other layouts.

Once the fields use the shared set, maintain its values centrally. Leave a clear owner for that list so users do not solve the next missing choice by creating another independent field.

Check lead conversion separately

A shared list keeps the available choices consistent. It does not, by itself, decide which lead field transfers into which contact field.

Review Lead Conversion Mapping in the Leads module settings. Zoho's lead conversion documentation describes mapping compatible fields between Leads, Accounts, Contacts and Deals.

Create a test lead with a known choice, convert it using your normal process and inspect the resulting contact. Also check the route that merges into an existing contact, if your team uses it. Verify the actual result rather than treating matching dropdowns as proof of a complete conversion setup.

Test the change with your everyday work

Before rolling it out, check that a new choice is available in both modules, existing records still make sense, and relevant filters and automations behave as intended. Include records arriving through an import or integration if those are part of your process.

Keep a custom module and lookup for categories that have become entities in their own right: an industry with assigned specialists and separate reporting, for example. For a simple shared vocabulary, a global set usually gives you less to maintain.