Multi-value Fields
Multi-value fields are CRM fields built to hold more than one value on a single record, such as secondary email addresses, a list of phone numbers, or multi-select checkboxes and tags. When duplicate records are merged, these fields make it possible to append values when merging: the values from each record are combined in the field, instead of one value replacing the others.
A single-value field, such as a job title or a lifecycle stage, keeps only one value, so a merge has to choose a winner. A multi-value field can keep them all. That's why the field type matters in a merge: it decides whether a contact's second email address or a company's extra phone number stays on the merged record, or leaves the CRM with the record that was removed.
See how Dedupely appends multi-value fields in your CRM
What Are Multi-value Fields?
Multi-value fields, also called multiple values fields, are fields whose type lets one record store a list rather than a single entry. Which fields support this depends on the CRM. Common examples are additional email addresses, such as HubSpot's "Additional email addresses" field, several emails and phone numbers on a person in Pipedrive, tags on a contact, and multi-select checkbox or picklist fields that let a record carry more than one option.
A simple example: two contacts for Maria Lopez. One has maria@acme.com and the tags "Webinar" and "Customer." The other has maria.lopez@gmail.com and the tags "Customer" and "Newsletter." If the merge picks one winner for each field, the merged record keeps one email address and two tags. If the values are appended, it keeps both addresses, one in the main email field and one as an additional address, and the tags "Webinar," "Customer" and "Newsletter," with "Customer" listed once where the tool drops repeated values.
There are a few ways to treat these fields in a merge. Appending keeps the unique values from each record, which suits fields where every value stays useful, such as working email addresses or interest tags. Keeping the primary record's values keeps the field short and predictable, which suits lists that should reflect one source, such as tags managed by one team. Rule-based handling sets the choice field by field, so emails can be appended while a status-like multi-select keeps one record's selection.
How Multi-value Fields Work
A merge handles multi-value fields as part of its field rules, in roughly this order:
- Check the field type. The CRM's own field definitions decide which fields can hold several values. A text field that happens to contain two emails separated by a comma is still a single-value field to the CRM, and a merge treats its contents as one value.
- Choose to append or pick a winner. For each multi-value field, the merge either appends the values from every record in the duplicate set or keeps the values from one record. Single-value fields always end with one value, chosen by the primary record or a field rule.
- Gather and compare the values. Appending collects the values from each record. Some tools keep a repeated value only once, while others list it twice, so "Jon@Acme.com" and "jon@acme.com" may both stay unless one is removed.
- Set the main value. Many records that hold several emails or phone numbers still mark one as the main one. The merge decides which value takes that spot, often the primary record's, and the rest are kept alongside it.
- Save the result to the surviving record. The combined list is written to the merged record. In some CRMs this happens for certain fields: when people are merged in Pipedrive, all unique emails and phone numbers are combined.
Appending can only keep what the field accepts. Some fields limit the number of values or allow only a fixed list of options, so a value from another record that doesn't fit the field's definition can't be added to it.
Why Multi-value Fields Matter for CRM Teams
Multi-value fields decide whether a merge keeps a customer's full set of contact details. People often use more than one email address or phone number: a work and a personal email, a direct line and a mobile. When the merge keeps only one, the others leave the CRM with the removed record. Replies from a dropped address can then arrive with no record to match, which can lead to a new duplicate, and sales or support lose a working way to reach the customer.
Tags and multi-select fields carry segmentation. A contact tagged for a product interest on one record and for a region on another belongs in both segments. If the merge keeps only one record's tags, the lists, reports and automated emails that rely on the others stop including that customer, and the gap is hard to spot because the record still looks complete.
Appending has its own cost when it isn't controlled. Repeated values, old addresses and placeholders such as "N/A" can stay in the field, so emails go to outdated inboxes and a long list makes it harder to tell which address is current. In many systems a merge is hard or impossible to reverse, so a value dropped by the merge is often hard to get back. The rule for each multi-value field decides whether the merged record ends up complete, cluttered or missing data.
Getting Started With Multi-value Fields
Start by listing the fields that hold several values in each object you merge. Check the CRM's field types rather than the field names, because a field called "Other emails" may be a plain text field, and only true multi-value fields can take appended values. Note which of them matter for outreach and segmentation, such as additional emails, phone numbers and tags.
Then decide, field by field, whether to append values when merging or keep one record's values. Appending suits contact details and interest tags, where every working value is useful. Keeping one record's selection suits fields that describe a single current state, even when they allow several options. For single-value fields, such as the main email address, choose a winning value instead, for example the one from the most recently worked record.
Before merging in bulk, preview a few merged records and look closely at the combined fields. Watch for the same value saved in two formats, placeholder values and old addresses that shouldn't carry forward, and clean them up on the records first or set a rule that makes them lose.
In Dedupely, Merge Rules carry out this choice field by field: Append combines the values of the CRM's own multi-value fields, such as Additional email addresses in HubSpot, while single-value fields keep one value through Primary, a Custom rule or a Best option such as Primary or best email. A preview of the merge result while you build a rule shows the outcome, with the winning values in bold, before anything changes in the CRM.
Key Takeaways: Multi-value Fields
Multi-value fields hold several values on one record, such as additional emails, phone numbers and multi-select tags. When duplicates merge, their values can be appended, so the merged record keeps the values from each record instead of one replacing the others. Whether a field can take appended values depends on how the CRM defines it, and single-value fields always end with one value. Appending suits contact details and interest tags, while keeping one record's values suits fields that reflect a single source. In Dedupely, Merge Rules set the choice field by field: Append, available for the CRM's own multi-value fields, keeps every unique value, so a repeated value isn't added twice, while Primary, Custom and Best options pick one value for the rest. Previews show the merged result before merging, and Merge History keeps each merge's original records and values.
Frequently Asked Questions About Multi-value Fields
Does merging duplicate contacts keep both email addresses?
It can, when the CRM has a field for more than one email and the merge appends to it. A contact has one main email field, so one address takes that spot, and the second is kept only if it moves into a field built for extra addresses. CRMs handle this differently. Pipedrive combines all unique email addresses and phone numbers when people are merged, and HubSpot has an "Additional email addresses" field that can hold the others. In a CRM with no such field, the second address is dropped unless you save it somewhere else first, such as a note or a custom field. Check how your CRM handles a pair of records before merging in bulk. In Dedupely, the main email field can use Primary or best email to choose which address leads, and Append adds the other addresses to the CRM's own multi-value field, such as Additional email addresses in HubSpot. Without Merge Rules, Dedupely follows the CRM's own merge logic.
What counts as a multi-value field in a CRM?
A multi-value field is one whose field type lets a single record store several values. Common examples are additional email addresses, lists of phone numbers, tags, and multi-select checkboxes or picklists. What decides it is the field type the CRM assigns, not the field's name or its contents. A text field named "Other emails" that holds two addresses separated by a comma is still one value to the CRM, and a merge treats it as one: the whole text is kept or replaced. Each CRM has its own set: Pipedrive stores several emails and phone numbers on a person, HubSpot has an Additional email addresses field, and many CRMs offer multi-select fields for tags or interests. In Dedupely, Append is available only for the CRM's own multi-value fields. Every other field is a single-value field, where Merge Rules choose one value through Primary, a Custom rule or a Best option, such as Primary or best phone.
Should you append values when merging, or keep one record's tags and selections?
Append when every value in the field stays useful, and keep one record's values when the field should reflect one source. Additional emails, phone numbers and interest tags suit appending, because each working value adds a way to reach or segment the customer. Fields that describe a current state, such as a multi-select of active products kept up to date by one team, are often better taken from one record, so old selections don't come back. A shared tag, such as "Customer" on both records, only needs to appear once on the merged record. Make the choice field by field, and preview a few merged records before merging in bulk. In Dedupely, Primary is the default for each field, Append is available for the CRM's own multi-value fields, and Custom rules use Win Rules and Lose Rules to choose the winning value from the fields you pick. Lose Rules run before Win Rules. A Custom merge, done by hand for one set, can also keep values from more than one record in a multi-value field.
Can you append values to a single-value field when merging?
No, a single-value field holds one value, so a merge keeps one value and drops the rest. That applies to fields like job title and lifecycle stage, and to the main email address and phone number in many CRMs. If the other values matter, there are a few options: move them to a multi-value field the CRM offers, such as an additional email field, add a dedicated field for them before merging, or record them in a note. Joining two values into one text field keeps both, but the result is hard to search, filter or use in automation. For single-value fields, the useful decision is which value wins. In Dedupely, Append isn't available on single-value fields, and Merge Rules can't be set on fields that are read-only in the CRM. For the rest, Primary, Custom rules and Best options choose the winning value, and suggested rules such as Placeholders lose or Newest wins can be applied field by field.
How do you avoid duplicate values when appending values on merge?
Clean up the formats before the merge, and preview the result before merging. Appending combines lists, so the same email saved as "Jon@Acme.com" on one record and "jon@acme.com" on another, or a phone number saved with and without a country code, can end up in the field twice. Some tools and CRMs keep only unique values, but what counts as unique varies, so formatting differences can slip through. Using one format first, such as lowercase emails and one phone format, makes repeated values easier to catch. Placeholders such as "N/A" or "none" are worth removing too, because appending keeps them alongside the real values. After the merge, check a sample of records. In Dedupely, Append keeps every unique value, so a repeated value isn't added twice. A preview of the merge result while you build a rule shows what will be kept, and the Preview Merge panel shows it again before you merge. Each field also has a "Send incorrect formats to manual review" checkbox, off by default, that sends invalid or filler values to Manual Review automatically.
