Navigation

When Entities Go Wrong

The four things that actually happen.

Nearly everything here traces back to one of two facts.

Duplicate detection matches names exactly, so it misses most real-world duplicates.

A merge cannot be undone, so a merge done in haste is a repair job rather than a retry.

Troubleshooting Guide

Is the problem a duplicate the scan did not find?

Yes → Check whether the two names are spelled identically. If not, that is why — merge them by hand from the consolidation screen.
No → Check whether the problem is a merge that has already happened.

Did a merge keep the wrong record?

Yes → It cannot be reversed. Rename the surviving record and move contacts back by hand.
No → Check whether an entity is refusing to delete.

Is an entity refusing to delete?

Yes → It has contacts linked. Move or delete them first, or merge it into another record instead.
No → Check whether a contact is missing its organisation tab.

Is the organisation tab missing from a contact?

The contact has no organisation linked. This is normal in B2C, where Skip entity starts on. Link one from the contact's own page.

Did an organisation disappear when you deleted a contact?

Deleting the last contact at an organisation deletes the organisation too. The confirmation says so. It cannot be recovered — recreate it and relink.

Known Issues

Symptom

The scan says no duplicates but I can see duplicates

Cause

The names are not spelled identically.

Solution

Zyntro groups organisations whose names match exactly once capitalisation and surrounding spaces are ignored. Acme Ltd and Acme Limited are different names and will never be grouped.

Find them yourself from the Entities list — sorting by Entity Name puts near-identical names next to each other — then merge from the consolidation screen.

The best long-term fix is at entry: on the Add Contact form, always pick the organisation from the suggestions rather than typing it out.

Symptom

Delete Selected is greyed out

Cause

At least one selected entity has contacts linked.

Solution

An organisation with contacts cannot be deleted, because deleting it would leave those contacts pointing at nothing.

Either deselect the ones with contacts, or deal with their contacts first — move them to another organisation, or delete them. If the organisation is a duplicate, merge it instead: that moves the contacts across and retires the record in one step.

The contact count column shows which rows will block a delete before you select them.

Symptom

A merge kept the wrong record

Cause

The primary was chosen for you, or chosen in haste.

Solution

There is no undo, and Zyntro does not record which contacts came from which record.

The practical repair: rename the surviving record to the name you wanted, correct its fields, and move any contacts that should not be there to another organisation from the consolidation screen.

If this happened through Auto-Merge, lower the group-size limit to 2 and review larger groups by hand in future — Auto-Merge always keeps the record with the most contacts, which is not always the best record.

Symptom

Contacts I expected are not on the organisation

Cause

They are linked to a second copy of it.

Solution

Open the Entities list and sort by name. If the same company appears twice, the contacts are split across both.

The contact count on each row links straight to the contacts on that record, which is the quickest way to confirm. Then merge, keeping whichever record is more complete.

Symptom

A contact has no organisation tab

Cause

No organisation is linked.

Solution

In B2C this is the normal state — Skip entity starts switched on, so contacts are created without one.

Link one from the contact's own page. If many contacts are missing organisations and should not be, the consolidation screen's Orphaned Contacts panel assigns them in bulk.

Symptom

Entity data in an import was ignored

Cause

The CRM is in B2C mode.

Solution

In B2C, entity data supplied to an import or to the Add or Update Contact API is ignored rather than creating an organisation. This is stricter than the Add Contact form, which lets you switch Skip entity off per contact.

If you routinely need organisations on imported contacts, Hybrid is the mode that fits — changing it is a support request rather than a setting.

Symptom

Entity Score shows zero on every organisation

Cause

Nothing has set it.

Solution

Entity Score is not calculated by Zyntro. It is a number you supply through an import or the API, and it stays at zero until something sets it.

It is easy to confuse with contact engagement scores, which Zyntro does work out for you.

Frequently Asked Questions

No. The merged-away record is kept as a tombstone, but Zyntro does not record which contacts came from it, so they cannot be separated again. Decide which record to keep before merging.

No. Contacts, invoices, recurring invoices, revenue, leads and payment contracts all move to the surviving record. The losing record is marked Merged rather than deleted — purging is a separate step that removes only those tombstones.

No. Matching is exact once capitalisation and surrounding spaces are ignored. Those differ, so they are two organisations as far as the scan is concerned. Merge them by hand.

Organisations are created by whatever creates contacts — forms, imports, the API and the business-card scanner all create one when entity data arrives with a contact and the CRM is not in B2C mode.

No. A contact belongs to at most one, or to none.

No. Entities and contacts both belong to your organisation, so several brands share one set of them.

Tip: The habit that prevents most of this: pick, do not type. On the Add Contact form the organisation box offers matches as you type. Choosing an existing organisation instead of typing its name again is what stops duplicates being created, and it costs nothing at the moment you are already filling the form in.

Need More Help?

Still need help? Reach out to our support team.

Contact Support

Was this article helpful?

NotebookLM Overviews