# Can you edit a field value while merging duplicates? | Dedupely

> Sometimes neither duplicate has the right value. When to type the correct value during the merge instead of fixing it later, and how to keep a record of it.

- URL: https://dedupe.ly/blog/duplicates/edit-field-value-while-merging
- Section: blog
- Published: 2026-11-15
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

Skip to content
[New Dedupely Intelligence Now on every paid plan, monthly or yearly.](https://dedupe.ly/ai-deduplication)
[Blog](https://dedupe.ly/blog)
[Duplicates](https://dedupe.ly/blog/duplicates)

## Can you edit a field value while merging duplicates?

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated November 15, 2026
#
min read
TL;DR
- A merge usually picks each value from one of the duplicates.
- Sometimes neither has it right: an old title on both, a typo in both, a phone with a missing digit.
- Editing the value during the merge saves a second step and leaves one clean record.
- Keep hand edits for one-off sets, and record them so the next person knows the value came from neither record.
- In Dedupely, Custom Merge lets you edit a value before merging, and Merge History marks it "Edited by hand".
When two records merge, each field normally takes its value from one of them: the newest email, the current owner, the longest company name. That works when one of the records has the right value.
Sometimes neither does. Both records show the person's old job title. Both have the company name misspelled the same way. One phone is missing a digit and the other is blank. You can merge and fix it afterwards, or you can type the right value during the merge. This post covers when to do which.

### When neither duplicate has the right value

| Field | What both records say | What you know is right |
| --- | --- | --- |
| Job title | "Sales Manager" (old) | "Head of Sales" |
| Company name | "Acme Corproation" | "Acme Corporation" |
| Phone | "555 201 334" and blank | "555 201 3344" |
| Address | Old office on both | The new office |
Picking one of the two values carries the mistake into the merged record. You'd have to remember to fix it later, and often nobody does.

### Edit during the merge or after?

**Edit during the merge when:**
- You're merging a single set by hand anyway.
- You know the right value for sure, from the customer, a recent email or their website.
- The field matters for the next step, like the email a rep is about to use.
**Fix it after, or not at all, when:**
- You're merging in bulk. Hand edits don't scale, and a rule should decide.
- You're not sure what the right value is. Leave it and flag it for the owner.
- The value comes from another system that will overwrite it on its next sync.
Example
Say a rep is merging two records for the same customer before a renewal call. Both show "Sales Manager", but the customer's email signature says "Head of Sales". Editing the title during the merge means the renewal record is right before the call, without a second edit.

### Keep a record of hand edits

A value typed by hand didn't come from either duplicate. If someone later checks the merge, they need to know that, or the value looks like it appeared from nowhere. Make sure your tool or process records:
- That the value was edited by hand.
- Who edited it and when.
- What the original values on each record were.
Pro tip
If you find yourself editing the same field by hand on many sets, that's a sign you need a merge rule or a data fix at the source, not more hand edits.

### How Dedupely handles hand edits

In Dedupely, Custom Merge lets you open a duplicate set, pick the winning value field by field and edit a value by hand before you preview and merge. It works in every connected CRM and in spreadsheets. For multi-value fields, you can keep values from more than one record. Merge History marks those values "Edited by hand", and its CSV export keeps the original values from every merged record. For bulk merges, Merge Rules decide each field instead, so hand edits stay for the sets that need them.
[Merge with the right values](https://v2.app.dedupe.ly/signup)

### Fix it once, during the merge

When neither duplicate has the right value, picking one keeps the mistake. For one-off sets, edit the value during the merge and keep a record that it was edited by hand. For bulk merges, let rules decide and fix recurring problems at the source.

### Frequently asked questions

#### Can I edit a field when merging duplicates?

In many tools, yes, when you merge a single set by hand. In Dedupely, Custom Merge lets you edit a value before merging, in every CRM and in spreadsheets.

#### Should I edit values during a bulk merge?

No. Bulk merges should follow rules. Keep hand edits for single sets where you know the right value.

#### How will others know a value was edited by hand?

Use a tool that records it. In Dedupely, Merge History marks those values "Edited by hand" and keeps the originals.

#### What if I'm not sure which value is right?

Don't guess. Merge with the best available value, or leave the set unmerged, and ask the record owner.

#### Why did my edited value change back after the merge?

Another system may have overwritten it on its next sync. Fix the value in the system that owns that field.
Behind the article

### Gaby Salinas

Marketing Assistant at Dedupely
Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start.
As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes.
[Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns)

### Contact us

We’d be happy to help you get this set up.

#### Write us a message

We probably know the answer to your question already
help@dedupe.ly
Email copied to your clipboard!
[Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler)

### Discover Related Blog Posts

Stay updated with our latest articles and insights.
- [Duplicates Merge CRM records without losing data Field-level merge rules let you control how each value is kept or replaced during a CRM merge. More accurate merges, fewer reviews, and logic you can scale. Gaby Salinas February 12, 2026](https://dedupe.ly/blog/duplicates/merge-crm-records-without-losing-data)
- [Duplicates How do I know which duplicate record is the real one? When a contact exists several times, each record holds part of the history. How to pick the right one today, and how merging puts calls and notes on one. Gaby Salinas October 30, 2026](https://dedupe.ly/blog/duplicates/which-duplicate-record-is-the-real-one)
- [CRM Organization Why you need a record of every merge in your CRM A merge record shows which records went in, which values won, who merged them and when. It answers questions from sales, security and leadership. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-organization/crm-merge-history)

### Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.
[Try for free](https://v2.app.dedupe.ly/signup) [Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)
[Or sign up with Google](https://v2.app.dedupe.ly/signup/google)
Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)
