How to Use Dropcontact to Clean and Enrich Your CRM

The short answer: if your HubSpot or Pipedrive CRM has grown through imports, forms and several sales tools, start with Dropcontact's free 14-day test before talking price: tell your users, connect with admin rights, let it clean contacts whose first names start with A to D, read the emailed report, spot-check a sample, and only then ask for the annual licence, which is priced by CRM size, per the CRM test article and the CRM terms article.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

A CRM rarely breaks in one go. It drifts: a webinar import with first and last names swapped, a sales rep's spreadsheet, a form that accepts personal addresses, two records for the same buyer created a year apart. Dropcontact's CRM integration cleans, enriches and merges inside HubSpot or Pipedrive without a database of its own. This guide covers the test, which shows you what it would change. For what Dropcontact is and its file prices, see the Dropcontact glossary entry.

Before you connect it:

1. Size the test against the base. For example, if 1,800 of your 12,000 contacts have first names starting with A to D, the test touches 1,800 / 12,000 = 15 in every 100 records, plus their companies. Count yours from a contact export; the test article explains the A to D rule. A slice that size shows the effect without staking the whole base.
2. Back up what you hold. Dropcontact makes a backup before the test and can restore it on request, per the restore article. Export contacts and companies to CSV yourself as well, so you can compare before and after without asking anyone.
3. Take three baseline counts. Contacts with no email, contacts with an email your sending tool has marked as bounced, and duplicate pairs your CRM already flags. The report you get later means little without these.

Step 1: Tell everyone who uses the CRM

The deployment article asks you to inform every CRM user first, because new fields will appear, such as LinkedIn, SIREN, number of employees and civility. Send a short note with the dates of the test and one rule: no manual edits to contact or company records during the 14 days. The restore article warns that if you revert, manual changes made during the test are not kept.

Step 2: Launch the test with admin rights

You, or whoever starts the test, need administrator rights in the CRM. Log in to the Dropcontact app, open the CRM integration section and click the 14-day test button. The deployment article says the sales team then helps configure the integration before the connection starts. No bank details are needed for the test, per the test article.

Step 3: Know what the test does and does not do

During the test, Dropcontact processes contacts whose first names start with A, B, C or D, and their companies, including new ones created in those 14 days. It does not detect or merge duplicates during the test, and it adds phone numbers from email signatures only after you subscribe. It maps to your existing fields and creates the ones that are missing, per the CRM changes article. So the test shows enrichment and cleaning, not deduplication, and you judge it on that.

Step 4: Read the report, then the records

When the first pass ends, you receive a performance report by email on what was enriched and cleaned. Then open the records. In HubSpot, each change leaves a note in the activity section, such as "Dropcontact added a LinkedIn profile", per the HubSpot changes article. In Pipedrive, the fields change and the changelog shows the history, with notes on People and Organizations, per the Pipedrive changes article. Pick 20 records from the A to D slice at random and compare each with your CSV backup.

Step 5: Let Claude spot-check the changed emails

For the records where the email changed, a second opinion is cheap. Create a Dropcontact account for files, which comes with 50 free credits, and connect its MCP server to Claude by adding https://mcp.dropcontact.com/mcp/ as a connector and completing the sign-in, per the API and MCP documentation. Paste in the changed addresses and ask: "Validate each of these email addresses with Dropcontact and list any that do not come back as nominative and verified." Each verification uses 1 credit.

Claude reports; the account owner decides. Nothing it returns goes back into the CRM automatically. Where a result disagrees with what the test wrote, the owner checks the person's current role on the company site before changing the record.

Step 6: Decide, and know what the licence covers

After 14 days you subscribe or you do not. Without a subscription, the enrichments and the fields made during the test stay in your CRM, per the test article. With one, the full pass over all existing records starts once payment arrives, merging switches on, and every record is processed: the records article says none can be excluded. The licence runs for 12 months and its price is revised at each renewal by CRM size, per the CRM terms article. Credits from a Files & API plan cannot be used for the CRM, per the pricing page.

Step 7: Keep deletion requests from coming back

When a contact asks to be deleted but you need to keep the record's history, the GDPR request article suggests replacing their email with a gdpr@ address on your own domain, which stops Dropcontact from processing it. Their right to object to direct marketing comes from Article 21 of the GDPR, so log the request where your team will see it.

How to know it worked

Repeat the three baseline counts on the A to D slice at the end of the test and compare them with the same slice before it. Then watch the bounce rate of the next campaign that uses those contacts. The free test keeps its enrichments even if you leave, which is generous and also good selling: a CRM that already carries Dropcontact's fields is easier to renew than to unwind, so decide on your counts, not on the new columns.

What Dropcontact's help articles warn about

• Surprising your users. New fields and changed values arrive without notice unless you give it.
• Testing without admin rights. The test cannot start without them.
• Editing during the test. A restore drops manual changes made in the test period.
• Expecting exclusions. After subscribing, every record is processed; you cannot leave some out.

If the duplicates come from three tools all writing to one CRM, the stack is the problem rather than the data, and a one-week Startup Fixer review, which I sell, maps who writes what before you pay to clean it.

FAQ

Does the test modify my CRM?

Yes. It changes and adds fields on A to D contacts and their companies, and creates fields that do not yet exist, per the CRM changes article. You can ask for a restore at any time during the test.

Can I see what Dropcontact changed?

Yes. HubSpot shows a note in each record's activity for every enrichment, and Pipedrive shows the changes in the changelog and notes, per the HubSpot changes article.

Which CRMs does it support?

HubSpot and Pipedrive are live; the homepage lists Salesforce as coming soon. For other CRMs, the file upload and the API work on exported contacts.