Import Scraped Contact Lists into HubSpot or Salesforce

A CSV export and a native CRM integration are different workflows. This guide covers a manual export-and-import handoff. It does not assume that SocLeads provides a native HubSpot connector, Salesforce sync or a public automation API.
Prepare the export and a field map
Keep an untouched copy of the exported results. In a working copy, inspect the actual column names and choose the CRM object you want to update. Different sources and exports can contain different fields, so build the map from the file you have rather than assuming a universal schema.
Scroll horizontally to compare all columns →
| Working field | Purpose | Check before importing |
|---|---|---|
| Contact identifier where appropriate | Normalise and review duplicates | |
| Name or business name | Human-readable context | Do not split a business name into a guessed personal name |
| Source link | Research provenance | Use a suitable property or note supported by your CRM |
| Review owner and date | Internal workflow | These are team-added fields, not claimed export fields |
For HubSpot’s supported formats and identifiers, use the official import-file guide.
When this handoff needs to run regularly, Albato is an option to consider for connecting the applications in your workflow. Check its connector catalog against your source app and CRM, and carry the field map from your test import into the automation setup.
Test a small HubSpot import
Select the intended objects and a small representative file. Map each included column to an appropriate property and inspect how identifiers will match existing records. Keep unknown or unwanted columns out of the import. Follow the options shown in your account because available tools and permissions can vary.
After the test, inspect sample records, associations and the import error report. Confirm that source context and owner assignments arrived as intended. Do not treat the presence of an email address as evidence of marketing consent.
Check the equivalent Salesforce workflow
In Salesforce, first decide whether the records belong in Leads, Contacts or another supported object. Check your edition, permissions, required fields and duplicate-management settings. Use Salesforce’s Data Import Wizard documentation to confirm the available path.
Test with a small file, then check created versus updated records, validation errors and ownership. Keep the original source file available so the team can trace and correct a mapping mistake.
Keep imports and outreach controls connected
- Use a batch label and retain the import summary.
- Document the duplicate key and the rule for updating existing values.
- Carry suppression and opt-out handling into the system used for sending.
- Separate imported contacts from qualified opportunities.
- Before scheduling recurring runs in Albato, verify support for your source and CRM, then test duplicate handling and failure notifications.
Start with a reviewed B2B contact list and continue through the pipeline workflow.
Turn this research into a lead list
Collect verified emails from Google Maps, Instagram, Facebook and LinkedIn — free to start.
Start free with SocLeads →