Migrate from Enrich-CRM to Pipedrive

HubSpot Company records enriched by Enrich-CRM map to Pipedrive Organizations. Every enriched firmographic field from Enrich-CRM (industry, employee count, revenue estimate, technology stack, location data) maps to a Pipedrive custom field that we create during schema setup. The HubSpot company domain becomes the Organization's Website field and acts as the dedupe key during import to prevent duplicate Organizations from being created.

HubSpot Contact records enriched by Enrich-CRM map to Pipedrive People. Every enriched contact field (title, seniority, LinkedIn URL, phone, location, department) maps to a Pipedrive custom field. The Person is linked to the Organization via the organization_id field, which we resolve at import time using the Organization dedupe key (domain/website) so the relationship is satisfied at insert.

Enrich-CRM job-change alerts are not CRM records in the traditional sense. We capture each detected job change as a Pipedrive Activity of type Note, stamped with the alert timestamp, the previous employer, and the new employer as free-text fields. This preserves the buyer-intent signal in the activity timeline against the relevant Person record. The customer admin can optionally create custom Pipedrive fields for previous_role and new_role if they want structured data.

Custom lead scoring models and contact segments built inside Enrich-CRM are not accessible via public API. We document the scoring criteria (thresholds, conditions, data sources used) during scoping via screen captures and customer interviews. We then rebuild equivalent scoring in Pipedrive using custom numeric fields for each scoring dimension and Automation rules (Advanced tier) to update scores when relevant fields change. This is a manual configuration step that the customer admin must approve and budget separately from data migration.

Automation paths triggered by Enrich-CRM enrichment signals (for example: enrichment complete > update CRM field > fire email sequence > create task) cannot migrate as code. We audit every active Zapier, Make, or n8n workflow triggered by Enrich-CRM and deliver a written handoff document describing each automation's trigger, conditions, and actions with a recommended Pipedrive Workflow Automation equivalent. The customer admin rebuilds these in Pipedrive's Automation engine post-migration.

If a customer used Enrich-CRM's API to attach custom metadata to enrichment results, we preserve those as Pipedrive custom fields. For JSON blob metadata, we either flatten key-value pairs into individual custom fields (if the schema is known) or store the full JSON as a long-text custom field that Pipedrive's API can read. The customer chooses the strategy during scoping based on how the custom metadata is used downstream.

Since Enrich-CRM has no standalone export, we extract enriched records directly from the connected HubSpot instance via the HubSpot API. We use the HubSpot CRM Lists and Companies/Contacts API endpoints to pull all enriched records, preserving the Enrich-CRM enrichment properties that were appended as HubSpot custom properties. We then map those HubSpot properties to the equivalent Pipedrive custom fields during the transform step.

If the connected HubSpot instance has Deals attached to the enriched Contacts and Organizations, we migrate those Deals to Pipedrive Deals. HubSpot deal stages map to Pipedrive Stages, and the HubSpot pipeline maps to a Pipedrive Pipeline that we configure before migration. Each HubSpot deal's associated Company and Contact lookups resolve to the corresponding Pipedrive Organization and Person IDs generated during the primary record import.

HubSpot engagement records (calls, emails, meetings, tasks, notes) attached to the migrating Contacts and Companies are extracted from HubSpot and mapped to Pipedrive Activities. Calls map to Activity type Call, emails to type Email, meetings to type Meeting, and tasks to type Task. The activity timestamp is preserved so the Pipedrive timeline reflects the original interaction date. We use Pipedrive's Activities API with batch inserts and parent record resolution to maintain the activity-to-person and activity-to-organization linkage.

Enrichment credits are a billing artifact and do not migrate. We document the customer's credit consumption rate and average credits-per-record ratio from the Enrich-CRM dashboard so the customer can estimate the volume of records they need to re-enrich in Pipedrive's Smart Contact Data. Pipedrive's enrichment is included at the Advanced tier and above with no per-enrichment credit cost, which typically reduces the ongoing enrichment spend compared to Enrich-CRM's credit model.