Migrate from Enrich-CRM to Microsoft Dynamics 365 Sales

Enriched firmographic data (industry, employee count, revenue estimate, tech stack, location) from Enrich-CRM maps to Account custom fields in Dynamics 365. We create custom fields on the Account entity with a naming convention such as ec_industry__c, ec_employee_count__c, ec_revenue_estimate__c, and ec_tech_stack__c. The enrichment source flag (enrichment_vendor__c = 'Enrich-CRM') and enrichment_timestamp__c are added to every Account so reporting can distinguish enriched records from natively-entered ones. Schema is deployed to a Dynamics 365 Sandbox before production migration.

Enriched contact data (title, seniority, LinkedIn URL, phone number, location, department) from Enrich-CRM maps to Contact custom fields. We create fields such as ec_job_title__c, ec_linkedin_url__c, ec_seniority_level__c, and ec_phone_confidence__c on the Contact entity. The original enrichment date is stored in ec_enrichment_date__c. Parent Account resolution happens before Contact import by matching the HubSpot Company domain to the Dynamics 365 Account Website field.

Enrich-CRM job-change alerts are not a native CRM object — they are signal records without a standard Dynamics 365 equivalent. We capture the alert as a Note attached to the Contact record with a custom date field ec_last_job_change__c and a text body describing the previous and new employer. This preserves the buyer-intent signal for sales reps without creating a custom entity. The Note activity type is used because Dynamics 365 Activity has a closed-ended schema for standard types.

Custom lead scoring models and segmentation rules built inside Enrich-CRM are not accessible via public API. We document the scoring criteria during scoping through screen captures and customer interviews, then deliver a written scoring rebuild specification that maps to Dynamics 365's native lead scoring (available in Sales Hub Professional with Sales Insights) or a Power Automate scoring flow. This is a manual configuration step outside the data migration scope.

If the customer used Enrich-CRM's API to attach custom metadata to enrichment results (beyond the standard firmographic and contact fields), we preserve those as either typed custom fields on Account/Contact or as a JSON blob in a text field ec_custom_metadata__c, depending on the metadata structure. Dynamics 365's Dataverse allows flexible custom field creation via the maker portal or the metadata API, so we prefer typed fields where the data format is consistent.

Since Enrich-CRM's native HubSpot Marketplace app means enriched records live in HubSpot (not in Enrich-CRM itself), the migration source is the HubSpot CRM, not Enrich-CRM directly. We export Contacts, Companies, and associated enrichment properties from HubSpot using the HubSpot CRM API or CSV export, then transform and load into Dynamics 365. If the customer is simultaneously migrating from HubSpot to Dynamics 365, we handle the CRM migration as a parallel scope with its own object mapping.

Automation paths triggered by Enrich-CRM enrichment signals (for example, 'new enrichment complete → update CRM field → fire notification in Teams') are not transferable to Dynamics 365 because Power Automate uses a different trigger and action model from Zapier, Make, and n8n. We deliver a written inventory of every active automation with its trigger, conditions, actions, and recommended Power Automate equivalent. The customer's Power Platform admin or a Microsoft partner rebuilds them post-migration.

Enrichment credits are a billing artifact in Enrich-CRM and do not represent user data. They do not migrate. We document the customer's credit burn rate during scoping so they can estimate the number of LinkedIn Sales Navigator lookups they will consume in Dynamics 365 and right-size their Sales Navigator seat count accordingly.