Migrate from ConvergeHub to Microsoft Dynamics 365 Sales

ConvergeHub treats Leads as a distinct top-level module separate from Contacts, carrying status, source, and assignment fields. We extract all Lead records from the ConvergeHub Leads module and load them into the Dynamics 365 Lead entity via Dataverse API. Lead Status maps from ConvergeHub leadstage to a configured Dynamics 365 Lead Status picklist. Owner assignment resolves by email match against the Dynamics 365 User table. Any ConvergeHub custom fields on Leads require pre-creation in Dataverse before import.

ConvergeHub Companies map to Dynamics 365 Accounts. The company name, industry, size, address, and any custom properties extract from the Companies module CSV and load into the Account entity. Account is the first object loaded in production migration because Contacts and Opportunities carry AccountId lookups that must resolve at insert time. We reconstruct the ConvergeHub Company ID to Account ID mapping to use as a reference table for all dependent records.

ConvergeHub Contacts link to Accounts and carry name, email, phone, role, and custom fields. We extract Contacts with their parent Account reference (ConvergeHub accountid), resolve the AccountId using the mapping table built during the Account phase, and insert Contacts into Dynamics 365 with the Account lookup satisfied. Contact roles and lifecycle stage from ConvergeHub custom fields migrate to custom Contact fields in Dynamics 365.

ConvergeHub Deals represent pipeline opportunities tied to Accounts or Contacts. We extract deal name, stage, value, probability, expected close date, and owner assignment. Stage names map to a Microsoft Dynamics 365 Sales Process that we configure before migration. Probability percentages from ConvergeHub map to the corresponding stage probability in Dynamics 365. Closed-Won and Closed-Lost status from ConvergeHub become Dynamics 365 Opportunity Stage values in the configured Sales Process.

ConvergeHub pipeline stages map to a Microsoft Dynamics 365 Sales Process with corresponding stage values and probabilities. We configure the Sales Process in Dataverse before the Opportunity load so that StageName references resolve correctly. Each stage in ConvergeHub becomes a stage option in the picklist, with the probability percentage rounded to the nearest integer allowed by Dynamics 365.

ConvergeHub Cases function as support tickets linked to Contacts or Accounts. We extract case status, priority, subject, description, and the linked Contact or Account. Case status values map to Dynamics 365 Case Status picklist values. Priority maps to Priority field in Dynamics 365. Cases are loaded after Accounts and Contacts so that the RegardingObjectId lookup resolves at insert time. Custom case fields require pre-creation in Dataverse.

ConvergeHub Invoices carry line items, totals, tax, and payment status. Microsoft Dynamics 365 Sales does not serve as a full invoicing or financial system; Invoice records are typically recreated in Dynamics 365 Business Central if the customer runs ERP alongside CRM. For migration scoping, we extract invoice data and map invoice headers to Microsoft Dynamics 365 Sales Quotes or Sales Orders as a customer choice, and we flag that line item totals and tax are informational pending Business Central recreation.

ConvergeHub Products hold the catalog used in Deals and Invoices: product name, SKU, unit price, and description. We extract Products and load them into the Dynamics 365 Product entity via Dataverse API. ProductCode maps from the ConvergeHub SKU field. Standard Price Book entries are created during the Product phase so that Line Items can reference price book entries at Opportunity load time.

ConvergeHub Activities cover calls, tasks, events, and logged communications linked to Contacts, Leads, Deals, or Accounts. We extract activity type, timestamp, notes, and owner assignment. Call activities map to Task with TaskSubtype=Call and duration preserved in a custom field. Meeting and event activities map to Event with StartDateTime and EndDateTime preserved. Activity records resolve their RegardingObjectId to the appropriate Contact, Lead, Account, or Opportunity using the ID mapping tables built during earlier phases.

ConvergeHub stores documents and files attached to records. We extract file metadata and blob storage references. Files are downloaded from ConvergeHub and re-uploaded to the Dynamics 365 connected SharePoint site (SharePoint integration must be enabled in the destination environment). If SharePoint is not configured, file metadata and associations are documented in the migration report for manual re-upload post-migration.