We did some data reconciliation on our DB however some duplicates needed to be done manually on HS. In one instance we had more than 300 duplicates. After failing to merge support told me there’s an all-time limit of 250 merge on companies or contacts. I don’t see that being used often but would great if this could be removed.
Status: Idea Submitted
100% agreed on this one. I’ve dug into the technicals on this one, and I think I know how this could work.
The current process (which is frankly less than I’d expect from HubSpot development, all considered?):
All associations table records remain exactly as they were before.
Merged IDs get dumped (comma-separated) into a field on the final record, called ‘Merged Record IDs’ (which obviously has a limit on length, being a text field).
The merged record gets deleted.
The associations lookup checks via this ‘Merged Records ID’ field if it can’t find the right record ID in the normal place.
This means the only real limitation is a) lookup speed on this comma-separated text field, and b) the allowable length of this comma-separated text field.
The better way to do it is as follows:
All associations table records get updated to the correct new record ID on the database (this needs to take into account things like association labels etc, but is certainly possible).
The merged record gets deleted.
We’re working on this ourselves, with the following process:
1. Make an API call to the associations definitions read all endpoint.
2. Make an API call to the batch read associations endpoint for each object the mergee record may be associated to, from point 1.
3. On our end, filter down the results to where it’s regarding the mergee or merger record.
4. Run validation on our end, to check there’s no primary association conflicts etc.
5. Make an API call to batch create associations endpoint, to add the mergee associations to the merger record.
6. Make an API call to archive basic endpoint to delete the mergee record.
It’s a shame this functionality is just a little limited in the standard setup.
Yes, that would be great if that could be removed.