Keep in mind
Mapping needs a connected CRM and a portal Admin. See our pricing for what each plan includes.
Set up a mapping
In the portal, open Custom Fields and find the CRM Integration section on the same page.
Open the tab for your CRM. For each custom field, choose the CRM field it should fill in the CRM Field column (it starts as — Not mapped —), then click Save Mappings. Saving saves every mapping for that CRM at once.
If your CRM has a field with the same name, you’ll see Same name in your CRM with a Use button. One CRM field can be used by only one Covve field.

Only an admin can connect a CRM and map fields. A Viewer sees the mappings but can’t change them. If no CRM is connected, a Viewer sees An admin can connect a CRM to map fields and sync lead data. An admin sees Map your custom fields and sync lead data automatically. with a Get started button.
You can map custom fields for Salesforce, HubSpot, Zoho CRM and Microsoft Dynamics 365. Pipedrive isn’t available for mapping yet.
What Covve maps for you
The standard fields, name, company, job title, email, phone, website, address are mapped already. You don't need to do anything for those.
Mapping is only for the custom fields you've defined yourself, since Covve has no way of knowing where "Where we met" belongs in your CRM.
Fields that aren’t sent automatically
The standard fields (name, company, job title, email, phone, website, address) are mapped for you. Each CRM guide’s Data Transmitted table shows exactly where each one lands.
Who captured the lead and when (Scanned by / Scanned on) aren’t part of the standard mapping. To get them into your CRM, create custom fields for them (for example Scanned by as a dropdown of team members, or Event date) and map them here.
On Enterprise, Salesforce can be configured to create Leads or Contacts. Custom fields apply to both.
See our integration guides.
Choose how leads sync
Under CRM Integration, Auto-sync leads to CRM appears once a CRM is connected. Choose Users decide (each person turns it on in the app), On for everyone or Off for everyone. Custom fields go with the lead either way.
Getting it right
Map to a field that already exists in your CRM. If there isn't one, create it in the CRM first
Match the types. A Covve dropdown mapping to a CRM free-text field usually works; the reverse often doesn't, and a mismatch fails quietly rather than loudly.
Same values. Make sure you have the same values in Covve and CRM. Different value will end up not being matched and thus staying empty in CRM.
Test with one lead before an event, not after. Capture a test contact, send it, and look at the record in your CRM. Ten minutes now beats discovering at the end of a conference that four hundred leads have an empty column.
A field you delete in Covve is dropped from the mapping when you save.
If the CRM fields don’t load, make sure the CRM is still connected to your account.
Your existing values are safe
Mapping controls where data goes, not whether it overwrites.
Covve never overwrites existing values. Depending on the CRM it fills in empty fields (Salesforce, Dynamics) or adds a note with the differences (HubSpot). See your CRM’s integration guide.
Check out our plans
The portal is available on Pro and Enterprise. See our pricing for what each plan includes.
