# DupliKit merge history

DupliKit creates a history record each time a merge is run.

To navigate to the DupliKit merge history pages, **open the Kyloe DataTools menu** from the top-left button and expand the 'History' section:

![](https://2344826204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV6boouX1p6N26pjOx7RO%2Fuploads%2FwxQtYLC4TxAbSDEFjp3x%2FPicture3.01.png?alt=media\&token=86d1f036-6e05-42b5-9efa-2d1dca91588b)

Selecting '**DupliKit**' will open the DupliKit merge history pages. Please select the correct entity to see the merge history for the specific entity.

![](https://2344826204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV6boouX1p6N26pjOx7RO%2Fuploads%2FgpmP0g8DRWdjLtNSLCWF%2FPicture4.01.png?alt=media\&token=16ab711a-3c7b-45e1-8716-c93afecf9910)

1. **Select an entity** to show related records for this entity.
2. **Review DupliKit merges:** Entering values in any of the filters here will restrict the history to just those records that match the filters.
3. Clicking the Show full details link will open a screen showing the details of each duplicate record merged into the master record.
4. **The last column will show one of the following statuses**:
   1. Merging shows that this record is currently be merged.
   2. Revert is a button that allows the merge process to be reversed. This can be pressed at any time after the merge is complete.<br>

      <mark style="background-color:yellow;">**NOTE**</mark><mark style="background-color:yellow;">: This will re-link all records and restore the archived duplicate. If field-level merging is enabled for any entity, information from a duplicate may have been added to the master record. This information will</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">**not**</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">be removed during the revert process.</mark><br>
   3. Reverting shows that this record is in the process of being restored to the pre-merged state.
   4. Reverted shows that this merge has been successfully restored to the pre-merged state.

{% hint style="info" %}
We do not recommend reverting a merge whilst other records are being processed. DupliKit will run both routines at the same time but if the same record is targeted in both a merge and a revert, unexpected results may occur. This is very unlikely, but we suggest only reverting when no merges are running.
{% endhint %}