Migrate from CompanyHub CRM to Microsoft Dynamics 365 Sales

CompanyHub Contacts with a sales-qualified lifecycle stage (or explicit won-deal association) map to Salesforce-style Dynamics 365 Contact tied to an Account. Unqualified prospects remain as Lead. We resolve the split by examining CompanyHub deal associations and custom lifecycle stage values during scoping, and we preserve the original CompanyHub lifecycle stage as a custom field ch_lifecycle_stage__c on both Lead and Contact for audit trail and reporting continuity.

CompanyHub Company records map directly to Microsoft Dynamics 365 Sales Account. The Company domain name becomes the Account Website field and is used as the dedupe key during import. Account records are created before Contact imports so that the ParentAccountId lookup is satisfied at the moment of Contact insert.

CompanyHub Deals map to Microsoft Dynamics 365 Sales Opportunity. The dealstage property maps to Opportunity StageName, and the pipeline assignment maps to a Record Type and Sales Process that we configure in Dynamics 365 before migration. Deal custom fields map to typed Opportunity custom fields.

Each CompanyHub pipeline becomes a Microsoft Dynamics 365 Sales Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage names and probability percentages migrate from CompanyHub to Microsoft Dynamics 365 Sales stage definitions. Closed-Won and Closed-Lost reasons from CompanyHub custom fields become Opportunity custom fields in Dynamics.

CompanyHub Tasks map to Microsoft Dynamics 365 Sales Task records with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving CompanyHub owner references to Microsoft Dynamics 365 Sales User records via email matching.

CompanyHub Custom Tables are mapped to Dataverse custom entities with matching column definitions. Because CompanyHub's API does not expose table schema definitions programmatically, we request customers to provide Custom Table field layouts during discovery before provisioning the Dataverse entity schema. Custom Table rows are imported last, after all parent Account and Contact records are in place to satisfy lookup relationships.

CompanyHub custom fields on standard objects (Contacts, Companies, Deals) map to typed custom fields on the corresponding Microsoft Dynamics 365 Sales entities. We export field definitions alongside values during discovery. Picklist-type custom fields in CompanyHub map to OptionSet fields in Dynamics 365 with the same option labels preserved.

CompanyHub Quotes migrate to Microsoft Dynamics 365 Sales Quote records, which are available from the Professional tier upward. Quote line items, totals, and template references map to Quote Detail rows. We note that Quote PDFs are file attachments migrated separately via ContentDocument if the customer requires document preservation.

CompanyHub Users map to Microsoft Dynamics 365 Sales User records by email address match. Owner references on Contact, Company, Deal, and Task records resolve to Microsoft Dynamics 365 Sales OwnerId. Any CompanyHub User without a matching Microsoft Dynamics 365 Sales User goes to a reconciliation queue for admin provisioning before record import resumes.

CompanyHub email activity logs migrate to Microsoft Dynamics 365 Sales EmailMessage records linked to an Activity Task. We flag during scoping that CompanyHub API responses may return email metadata without full body content in some cases; we inform customers of this gap and offer to supplement from an IMAP or email platform export if available.

CompanyHub Notes migrate to Microsoft Dynamics 365 Sales Note records linked via Annotation to the parent Contact, Account, or Opportunity. Note body text and any embedded attachments migrate as separate Note and File records respectively.