{"id":3408,"date":"2025-06-18T12:50:22","date_gmt":"2025-06-18T17:50:22","guid":{"rendered":"https:\/\/www.teamdesk.net\/blog\/?p=3408"},"modified":"2025-06-18T12:50:23","modified_gmt":"2025-06-18T17:50:23","slug":"merge-duplicate-customer-records-with-child-records","status":"publish","type":"post","link":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/","title":{"rendered":"Merge Duplicate Customer Records with Child Records"},"content":{"rendered":"\n<p>You have accidentally created multiple records for the same customer. Each of these records may already have related child records (e.g., order history, communications). Once you detect the duplication, you want to: <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep one master customer record<\/li>\n\n\n\n<li>Move all related child records from the duplicates to this master<\/li>\n\n\n\n<li>Delete the duplicate customer records afterward<\/li>\n<\/ul>\n\n\n\n<p>Let`s create a database that will identify all the parent records with matching names and allow us merge those records into one with a button click. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identify Duplicate Parents<\/h2>\n\n\n\n<p>In the Parent table create a <a href=\"https:\/\/www.teamdesk.net\/help\/relations\/many-to-many-relations\/\">many to many relation<\/a> with itself. This relation is needed to identify duplicate parent records and collect those records in a recordset column.<\/p>\n\n\n\n<p>First column under this relation will calculate the duplicate count. Create a <a href=\"https:\/\/www.teamdesk.net\/help\/columns\/creating-a-new-summary-column\/\">summary column<\/a> [Duplicate Count] with the following filter condition: [Name]=Related[Name]&nbsp;and&nbsp;[Id]&lt;&gt;Related[Id]<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-1.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"489\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-1-1024x489.png\" alt=\"\" class=\"wp-image-3411\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-1-1024x489.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-1-300x143.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-1-768x367.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-1.png 1276w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>In our example a record is considered to have a duplicate if another record with the exact same name exists. Therefore, we will create a second column &#8211; <a href=\"https:\/\/www.teamdesk.net\/help\/columns\/creating-a-new-recordset-column\/\">recordset<\/a> &#8211; will pick up all the existing duplicates.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-2.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"379\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-2-1024x379.png\" alt=\"\" class=\"wp-image-3412\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-2-1024x379.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-2-300x111.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-2-768x284.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-2.png 1273w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Collect the Child Records<\/strong><\/h2>\n\n\n\n<p>We need to identify the child records that need to be moved to the main record when the duplicate parents are deleted.<\/p>\n\n\n\n<p>Our Parent &#8211; Child tables already have a relation. Now let`s add a Child Records <a href=\"https:\/\/www.teamdesk.net\/help\/columns\/creating-a-new-recordset-column\/\">Recordset<\/a> column that will keep our details.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-7.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"379\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-7-1024x379.png\" alt=\"\" class=\"wp-image-3420\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-7-1024x379.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-7-300x111.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-7-768x284.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-7.png 1272w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Create a Button To Merge Duplicates<\/strong><\/h2>\n\n\n\n<p>Set up a <a href=\"https:\/\/www.teamdesk.net\/help\/rules\/custom-buttons\/custom-button-with-actions\/\">custom button<\/a> named <code>Merge Master<\/code> on the Customer table. By clicking this button user can initiate merging of duplicate records.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image.png\"><img loading=\"lazy\" decoding=\"async\" width=\"778\" height=\"754\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image.png\" alt=\"\" class=\"wp-image-3410\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image.png 778w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-300x291.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-768x744.png 768w\" sizes=\"auto, (max-width: 778px) 100vw, 778px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Identify Master and Remove Duplicates<\/strong><\/h2>\n\n\n\n<p>Now we need to add the workflow actions.<\/p>\n\n\n\n<p>The first action \u2014 &#8220;Fill Merge Id&#8221; \u2014 will assign the ID of the main record (the one we will keep after merging) to each duplicate record. We will use the recordset of duplicates created in step 1. If you don\u2019t have that yet, a <code>[Master ID]<\/code> text field must be created in the parent table to store the ID of the main record that will be kept after the merge.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-3.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"448\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-3-1024x448.png\" alt=\"\" class=\"wp-image-3415\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-3-1024x448.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-3-300x131.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-3-768x336.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-3.png 1269w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>This second <a href=\"https:\/\/www.teamdesk.net\/help\/rules\/workflow-actions\/\">workflow action<\/a> can optionally either mark duplicates as inactive or delete them entirely (based on your data retention policy).<\/p>\n\n\n\n<p>We will configure it to delete the remaining duplicates.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-4.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"278\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-4-1024x278.png\" alt=\"\" class=\"wp-image-3416\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-4-1024x278.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-4-300x81.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-4-768x208.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-4.png 1275w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Move Child Records to Master Record<\/h2>\n\n\n\n<p>Now we need to make sure that all the child records &#8220;migrate&#8221; to the main parent record.<\/p>\n\n\n\n<p>Whenever the button is clicked and the [Master Id] is populated on the parent record, the trigger calls an action to change the &#8220;owner&#8221; of the details (child records).<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-5.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"564\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-5-1024x564.png\" alt=\"\" class=\"wp-image-3417\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-5-1024x564.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-5-300x165.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-5-768x423.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-5.png 1268w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>In the workflow:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In all child records where <code>\"Parent\" = \"Duplicate Parent<\/code>&#8220;<\/li>\n\n\n\n<li>We need to update those child records to set <code>\"Parent\" = \"Master Parent<\/code>&#8220;<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-6.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"444\" src=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-6-1024x444.png\" alt=\"\" class=\"wp-image-3418\" srcset=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-6-1024x444.png 1024w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-6-300x130.png 300w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-6-768x333.png 768w, https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/image-6.png 1268w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>With the <code>Merge Master<\/code> button and a carefully crafted workflow trigger, you can handle duplicate customer records in TeamDesk cleanly and automatically. This is a powerful way to maintain data hygiene in any application that involves complex relationships between parent and child tables.<br>Check out the template with all the settings <a href=\"https:\/\/www.teamdesk.net\/merge_records\">here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In real-world usage of your CRM or data management system, duplicate records are almost inevitable. Whether due to manual input errors or data imports, you may find yourself with two or more customer records representing the same entity. Often, these records already have associated child records\u2014such as orders, interactions, or other related data\u2014which complicates cleanup.<\/p>\n","protected":false},"author":11,"featured_media":3422,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[132,327,326,127,36],"class_list":["post-3408","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tips-tricks","tag-database","tag-merge-duplicates","tag-merge-records","tag-online-database","tag-teamdesk"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Merge Duplicate Customer Records with Child Records - TeamDesk Blog<\/title>\n<meta name=\"description\" content=\"Merge duplicate customer records with child records. Helps maintain data hygiene in any application that involves complex relationships between parent and child tables.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Merge Duplicate Customer Records with Child Records - TeamDesk Blog\" \/>\n<meta property=\"og:description\" content=\"Merge duplicate customer records with child records. Helps maintain data hygiene in any application that involves complex relationships between parent and child tables.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/\" \/>\n<meta property=\"og:site_name\" content=\"TeamDesk Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-18T17:50:22+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-18T17:50:23+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/Merge-accounts.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Kateryna Dmytrenko\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kateryna Dmytrenko\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/\"},\"author\":{\"name\":\"Kateryna Dmytrenko\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#\\\/schema\\\/person\\\/a285defcf13a83e100cc66ebfdada2e9\"},\"headline\":\"Merge Duplicate Customer Records with Child Records\",\"datePublished\":\"2025-06-18T17:50:22+00:00\",\"dateModified\":\"2025-06-18T17:50:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/\"},\"wordCount\":495,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/06\\\/Merge-accounts.png\",\"keywords\":[\"database\",\"merge duplicates\",\"merge records\",\"online database\",\"TeamDesk\"],\"articleSection\":[\"Tips &amp; Tricks\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/\",\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/\",\"name\":\"Merge Duplicate Customer Records with Child Records - TeamDesk Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/06\\\/Merge-accounts.png\",\"datePublished\":\"2025-06-18T17:50:22+00:00\",\"dateModified\":\"2025-06-18T17:50:23+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#\\\/schema\\\/person\\\/a285defcf13a83e100cc66ebfdada2e9\"},\"description\":\"Merge duplicate customer records with child records. Helps maintain data hygiene in any application that involves complex relationships between parent and child tables.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/06\\\/Merge-accounts.png\",\"contentUrl\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/06\\\/Merge-accounts.png\",\"width\":1024,\"height\":1024,\"caption\":\"Merge duplicate records with details\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/merge-duplicate-customer-records-with-child-records\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Merge Duplicate Customer Records with Child Records\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/\",\"name\":\"TeamDesk Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#\\\/schema\\\/person\\\/a285defcf13a83e100cc66ebfdada2e9\",\"name\":\"Kateryna Dmytrenko\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/43d699ece76026402ebdbc9196f3f24de5dc93ffa6597e96b3d91bf256044877?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/43d699ece76026402ebdbc9196f3f24de5dc93ffa6597e96b3d91bf256044877?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/43d699ece76026402ebdbc9196f3f24de5dc93ffa6597e96b3d91bf256044877?s=96&d=mm&r=g\",\"caption\":\"Kateryna Dmytrenko\"},\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/author\\\/kateryna\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Merge Duplicate Customer Records with Child Records - TeamDesk Blog","description":"Merge duplicate customer records with child records. Helps maintain data hygiene in any application that involves complex relationships between parent and child tables.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/","og_locale":"en_US","og_type":"article","og_title":"Merge Duplicate Customer Records with Child Records - TeamDesk Blog","og_description":"Merge duplicate customer records with child records. Helps maintain data hygiene in any application that involves complex relationships between parent and child tables.","og_url":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/","og_site_name":"TeamDesk Blog","article_published_time":"2025-06-18T17:50:22+00:00","article_modified_time":"2025-06-18T17:50:23+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/Merge-accounts.png","type":"image\/png"}],"author":"Kateryna Dmytrenko","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kateryna Dmytrenko","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#article","isPartOf":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/"},"author":{"name":"Kateryna Dmytrenko","@id":"https:\/\/www.teamdesk.net\/blog\/#\/schema\/person\/a285defcf13a83e100cc66ebfdada2e9"},"headline":"Merge Duplicate Customer Records with Child Records","datePublished":"2025-06-18T17:50:22+00:00","dateModified":"2025-06-18T17:50:23+00:00","mainEntityOfPage":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/"},"wordCount":495,"commentCount":0,"image":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#primaryimage"},"thumbnailUrl":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/Merge-accounts.png","keywords":["database","merge duplicates","merge records","online database","TeamDesk"],"articleSection":["Tips &amp; Tricks"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/","url":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/","name":"Merge Duplicate Customer Records with Child Records - TeamDesk Blog","isPartOf":{"@id":"https:\/\/www.teamdesk.net\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#primaryimage"},"image":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#primaryimage"},"thumbnailUrl":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/Merge-accounts.png","datePublished":"2025-06-18T17:50:22+00:00","dateModified":"2025-06-18T17:50:23+00:00","author":{"@id":"https:\/\/www.teamdesk.net\/blog\/#\/schema\/person\/a285defcf13a83e100cc66ebfdada2e9"},"description":"Merge duplicate customer records with child records. Helps maintain data hygiene in any application that involves complex relationships between parent and child tables.","breadcrumb":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#primaryimage","url":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/Merge-accounts.png","contentUrl":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2025\/06\/Merge-accounts.png","width":1024,"height":1024,"caption":"Merge duplicate records with details"},{"@type":"BreadcrumbList","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/merge-duplicate-customer-records-with-child-records\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.teamdesk.net\/blog\/"},{"@type":"ListItem","position":2,"name":"Merge Duplicate Customer Records with Child Records"}]},{"@type":"WebSite","@id":"https:\/\/www.teamdesk.net\/blog\/#website","url":"https:\/\/www.teamdesk.net\/blog\/","name":"TeamDesk Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.teamdesk.net\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.teamdesk.net\/blog\/#\/schema\/person\/a285defcf13a83e100cc66ebfdada2e9","name":"Kateryna Dmytrenko","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/43d699ece76026402ebdbc9196f3f24de5dc93ffa6597e96b3d91bf256044877?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/43d699ece76026402ebdbc9196f3f24de5dc93ffa6597e96b3d91bf256044877?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/43d699ece76026402ebdbc9196f3f24de5dc93ffa6597e96b3d91bf256044877?s=96&d=mm&r=g","caption":"Kateryna Dmytrenko"},"url":"https:\/\/www.teamdesk.net\/blog\/author\/kateryna\/"}]}},"_links":{"self":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts\/3408","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/comments?post=3408"}],"version-history":[{"count":28,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts\/3408\/revisions"}],"predecessor-version":[{"id":3445,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts\/3408\/revisions\/3445"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/media\/3422"}],"wp:attachment":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/media?parent=3408"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/categories?post=3408"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/tags?post=3408"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}