Skip to main content

Fixing "Attempting to map an already mapped contact"

Error: "Attempting to map an already mapped contact"

Written by Antonio Sierra

This error means the email address you're using is already on another contact record. Every contact in Gigwell needs its own unique email address, so the same address can't sit on two cards.


​

Find the duplicate

  1. Go to the Contacts tab.

  2. Paste the full email address into the search box. Search by email, not by name — duplicates usually hide behind slightly different names, so a name search won't find them.

  3. Look at how many results come back. More than one card sharing that address is the cause of the error.


​

What to do about it

If one person genuinely works with several of your artists — a manager or an agent representing multiple acts — they should be one contact card linked to several artist profiles, not several cards sharing an address. Link the existing card to the additional artists rather than creating a second card for the same person.

If the second card is a true duplicate that was created by mistake, don't delete it. Contact records are shared across every booking they appear on, and the deletion is not cleanly reversible. Instead, leave the duplicate in place and use the correct card going forward.

If you need the details on one of the cards corrected so the addresses no longer clash, follow the article on changing a contact's name or email — editing a contact inline won't hold, and that article explains the revert-and-recreate steps that do.


​

If that doesn't work

If the email search returns only one card and you're still seeing the error, this one needs our team — start a chat from the messenger and we'll sort it out. Mentioning the email address you're trying to use and where in Gigwell the error appears will speed things up.


​

Good to know

You'll also hit this when importing artists and agents if the same person is listed under two addresses in your Google Contacts. De-duplicating by email in the linked Google account before you import saves a lot of cleanup afterwards.

Did this answer your question?