Migrate from ConvergeHub to Salesforce Sales Cloud

ConvergeHub's Lead module maps directly to Salesforce Lead. The source Lead ID is preserved in a custom field ch_lead_id__c for audit and cross-reference. Lead Status, Lead Source, and any custom fields migrate as typed Salesforce fields. If the ConvergeHub Lead has already been qualified and moved to a Contact in the source, we flag it for the Lead-Contact split decision during scoping.

ConvergeHub Account records map to Salesforce Account. Account is the parent of Contact in Salesforce, so we load Accounts first and establish the AccountId lookup before any Contact imports. The ConvergeHub Account ID is preserved in a custom field ch_account_id__c. Industry, size, address, and billing information migrate directly. Any ConvergeHub Account without a name receives a placeholder value and is flagged for customer review.

ConvergeHub Contact records map to Salesforce Contact. The Contact-to-Account relationship is resolved by matching the ConvergeHub account_id foreign key to the Salesforce Account ID we loaded in the previous phase. Contact roles, lifecycle stage equivalents, phone, email, and custom fields migrate directly. Any Contact referencing a deleted or missing Account in the source CSV is placed in a reconciliation queue with the Account IDs preserved for manual resolution.

ConvergeHub Deals map to Salesforce Opportunity. Stage, value, probability, expected close date, and owner assignment migrate. The ConvergeHub deal-to-account linkage is resolved by matching the account_id foreign key to the Salesforce Account ID. Deal-to-contact linkage maps to the OpportunityContactRole junction object, which we load after both Contact and Opportunity are in place. Pipeline stage names from ConvergeHub map to a Salesforce Sales Process that we configure before migration.

ConvergeHub pipeline stage values map to Salesforce Opportunity Stage values. We configure a Salesforce Sales Process per ConvergeHub pipeline and create StageProbability entries matching the source stage probabilities. Stage probability percentages are rounded to the nearest integer allowed by Salesforce.

ConvergeHub Cases function as support tickets and map to Salesforce Case. Case status, priority, subject, description, and the linked Contact and Account references migrate. If the destination Salesforce org does not include Service Cloud, Cases map to a custom Case object that we provision during schema design. Custom case fields and status values require explicit picklist mapping.

ConvergeHub Invoices carry line items, totals, tax, and payment status. Invoice data migrates to a custom Invoice object or to custom fields on the related Opportunity depending on the destination org's configuration. Payment gateway history and partially paid invoice states may not transfer fully; we flag payment status gaps and document them in the reconciliation report. Fully paid and voided invoices migrate with their status preserved.

ConvergeHub Product records map to Salesforce Product2. Product name, SKU, unit price, and description migrate. Standard Price Book entries are created during import. Product associations to Deals map to OpportunityLineItem records that we load after Pricebook2 and Product2 are established.

ConvergeHub Quotations carry product line items, pricing, and terms linked to Deals. They map to Salesforce Quote, which is a standard object from Professional tier. Quotation PDF attachments migrate as ContentDocument records linked to the Quote via ContentDocumentLink.

ConvergeHub Targets are a platform-specific module for tracking sales goals or quotas. They have no direct Salesforce standard equivalent, so we map them to a custom Goal object provisioned during schema design. Goal name, target amount, period, owner, and status migrate. The customer chooses whether to provision this as a custom object or a custom report type.

ConvergeHub Activity records cover calls, tasks, events, and logged communications. Calls migrate to Task with TaskSubtype = Call and CallDurationInSeconds in a custom field. Tasks migrate directly to Task with Status, Priority, and ActivityDate preserved. Events migrate to Event with StartDateTime, EndDateTime, and Location preserved. Attendee links migrate as EventRelation records. Activity-to-record linkages (linked Contact, Deal, Account) are resolved by foreign-key matching against the loaded Contact and Opportunity records.

ConvergeHub stores document metadata and file blob references attached to records. We extract file metadata and download attachments, then upload to Salesforce as ContentVersion records with ContentDocumentLink pointing to the parent Account, Contact, Opportunity, or Case. Large files are chunked and uploaded via the Salesforce REST API with multipart support.

ConvergeHub custom fields on Accounts, Cases, Contacts, Deals, Leads, Products, Invoices, Quotations, and Targets are inventoried during scoping. We pre-create each custom field in Salesforce with the matching field type: text fields to Text, picklists to Picklist (with value substitution mapping), multi-select to Multi-Select Picklist, dates to Date, and numbers to Number. Picklist value substitution tables are built during scoping for each multi-value field.

ConvergeHub Owner references on Deals, Cases, Contacts, and Activities are resolved by email match against the Salesforce destination User table. Any Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Salesforce Users are matched but flagged; migration proceeds with the OwnerId pointing to the inactive User record for manual reassignment post-migration.

ConvergeHub User records (name, email, role, ACL assignment) are exported for reference. Role names from ConvergeHub map to Salesforce Permission Set or Profile assignments that we document in the mapping table. Active versus inactive status is preserved. We do not create Salesforce Users; the customer's admin provisions Users directly in Salesforce before migration begins.