Status and Timing of Merge Operations
When you submit a duplicate merge operation, it is placed in a queue and is executed when operations ahead of it in the queue are completed. Go to Lists > Mass Update > Duplicate Resolution Status to view the Duplicate Resolution Status page. Here you can view the status of duplicate merge operations, the number of records merged, and the number of records that could not be merged. You can view possible errors that occur during the operation by clicking the Details link in the Errors column.
After you submit a duplicate merge operation, you can continue to work in NetSuite without waiting for the merge operation to finish. Records you have marked as duplicates cannot be edited during the time that the duplicate operation is queued or running. The primary record is locked only for a brief time when the merge operation begins.
System notes are not transferred from duplicate entity records to the primary entity record during a merge. Merging entities updates the system notes and last modified date for all transactions associated with the duplicate entity or entities. The system notes for these transactions will indicate that they were updated by the Duplicate Resolution process.
Merging entities is a data-intensive operation, and complex merges of many records such as transactions, custom fields, or workflows may time out when processing. You should test the merge process in a sandbox account first to ensure that it can be completed.
You should designate the entity with the most transactions as the primary record and entities with fewer transactions as duplicates to reduce the time it takes to complete the merge. You should also avoid merging entities with large numbers of transactions whenever possible.
Historical log records for duplicate merge tasks are saved in NetSuite for only seven days before the information is permanently erased.