# Why export, fix and re-import makes duplicates worse | Dedupely > Exporting your CRM, cleaning it in a spreadsheet and importing it back looks simple. Why the round trip often adds duplicates, loses history and breaks links. - URL: https://dedupe.ly/blog/duplicates/export-fix-reimport-makes-duplicates-worse - Section: blog - Published: 2026-11-11 - 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) ## Why export, fix and re-import makes duplicates worse By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated November 11, 2026 # min read TL;DR - Export the CRM, remove duplicates in a spreadsheet, import it back: one of the most common cleanup plans. - A spreadsheet doesn't merge records; it only decides which rows to keep. - Import the cleaned file and the CRM may create new records, update the wrong ones or leave the old duplicates. - Activities, deals, owners and links stay on the records you meant to remove. - Dedupely merges duplicates inside the CRM, so history and links move to the record you keep. It sounds like the simplest cleanup there is. Export all contacts to a spreadsheet, sort by email, delete the repeated rows, then import the clean file back. No new tool, and spreadsheets are familiar. Many teams try it once. Most end up with more duplicates than they started with, or with records that lost their history. This post covers why the round trip goes wrong and what to do instead. ### What a spreadsheet can and can't do A spreadsheet can find rows that look the same and delete some of them. It can't touch anything that isn't in the export: - **Activities:** calls, emails, notes and meetings stay on the CRM records. - **Links:** deals, tickets and companies linked to a record stay linked to that record. - **History:** form submissions, email engagement and changes over time aren't in the file. - **IDs and ownership rules:** the file has the values, not how the CRM uses them. Deleting a row in the spreadsheet doesn't delete or merge anything in the CRM. It only decides what you'll import. ### What happens on the way back in | What you import | What can happen | | --- | --- | | The cleaned file, as new records | The CRM creates a fresh record for every row, next to the old ones | | The cleaned file, matched on email | Rows update existing records, but the duplicates you removed from the file are still in the CRM | | The cleaned file, matched on record ID | Only the kept records update; the removed duplicates stay untouched | | A file with columns mapped differently | Values land in the wrong fields, or overwrite good data with blanks | In every case, the duplicates you deleted in the spreadsheet are still in the CRM, unless someone deletes them there too. And deleting them there throws away their activities and links. Example Say a team exports 12,000 contacts, finds 1,500 duplicate rows, deletes them in the spreadsheet and imports the 10,500 left. The import updates the matching records, so the CRM still has all 12,000. Someone then deletes the 1,500 duplicates in the CRM by hand, and the calls and deals logged on them disappear with them. ### Why it can make things worse **New records instead of updates.** If the import doesn't match on a field the CRM recognizes, every row becomes a new record. The CRM now has the original duplicates plus a new set. **Blanks overwrite good data.** If the cleaned file has an empty cell where the CRM had a value, some imports write the blank over it. **The wrong record survives.** Sorting and deleting rows keeps whichever row came first, not the one with the most history or the right owner. **It doesn't last.** The next form submission or sync creates new duplicates, and the round trip has to happen again. Pro tip If you do use a spreadsheet, use it to find and review duplicates, not to fix them. Note which records belong together, then merge them in the CRM so history and links move with them. ### When spreadsheets are the right place Some lists don't live in a CRM: an event list, a purchased list, a file from a partner. Clean those before they're imported, so the duplicates never reach the CRM. For data already in the CRM, merge it where it is. ### How Dedupely handles it Dedupely merges duplicates inside the CRM, so activities and associations like linked companies, deals and contacts move to the record you keep. Merge Rules decide which value wins in each field, blank values never win, and the Primary Record setting decides which record survives. For lists that aren't in a CRM yet, you can upload spreadsheets to Dedupely and dedupe them before importing; spreadsheets don't count toward your record limit. [Merge duplicates where they live](https://v2.app.dedupe.ly/signup) ### Merge in place A spreadsheet decides which rows to keep; it can't merge records. The round trip leaves the old duplicates in the CRM, risks new ones and strands history on records you delete. Clean outside lists before they're imported, and merge everything else inside the CRM. ### Frequently asked questions #### Can I export my CRM, remove duplicates in a spreadsheet and import it back? You can, but it doesn't merge anything. The duplicates stay in the CRM, and deleting them there loses their activities and links. #### Why did my re-import create more duplicates? The import probably created new records instead of updating existing ones, because it didn't match rows to records the CRM recognized. #### Does deleting duplicate rows in a spreadsheet delete them in the CRM? No. The spreadsheet is a separate file. The records stay in the CRM until you merge or delete them there. #### What do I lose if I delete duplicates instead of merging them? The activities, deals, notes and links on the deleted records. #### When should I clean data in a spreadsheet? Before a list is imported, like an event or partner list, so its duplicates never reach the CRM. 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. - [CRM Organization Should You Clean Spreadsheets Before Uploading or Clean Your CRM After? Cleaning the file first stops duplicate rows and triggered workflows. Cleaning the CRM after links new records to the accounts you already have. Gaby Salinas September 10, 2026](https://dedupe.ly/blog/crm-organization/clean-spreadsheets-before-uploading-or-clean-your-crm-after) - [Duplicates Should you merge duplicates or delete them? Merge duplicates that carry history, associations or attribution. Delete only junk, test and spam records. A simple rule for each case. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/duplicates/merge-or-delete-duplicates) - [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) ### 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)