Migrate from ConvergeHub to Freshsales

ConvergeHub Leads map directly to Freshsales Lead records. The ConvergeHub Lead Status and Source fields map to Freshsales Lead Status and Lead Source picklists. Any custom fields on ConvergeHub Leads are created in Freshsales as matching field types before import. Lifecycle stage information from ConvergeHub custom fields is preserved in a Freshsales custom field for segmentation and reporting continuity.

ConvergeHub Accounts map to Freshsales Accounts. The Account name, industry, size, address, and custom fields transfer directly. Account is imported first in the dependency chain because Contacts and Deals both require a valid AccountId lookup. We resolve any orphaned ConvergeHub Accounts that have no linked Contacts by creating the Account record and attaching the orphan Contacts during the mapping phase.

ConvergeHub Contacts map to Freshsales Contacts. The Contact-to-Account linkage is preserved by resolving the ConvergeHub Contact-Account relationship chain before import. ConvergeHub contact roles, lifecycle stage values, phone, and email data transfer to Freshsales Contact fields. Any ConvergeHub Contacts that lack an Account parent are linked to a default Account record created during staging.

ConvergeHub Deals map to Freshsales Deals. Freshsales Deals require an Account association; Deals linked directly to Contacts in ConvergeHub are remapped to the Contact's parent Account during transformation. Deal stage, value, expected close date, owner, and custom fields transfer. Pipeline stage mapping is configured in Freshsales before migration based on the customer's ConvergeHub pipeline structure.

ConvergeHub Cases map to Freshsales Cases. Case status, priority, subject, description, and linked Contact and Account transfer. Custom case fields and status values require explicit picklist mapping to Freshsales Case Status and Priority values. Conversation history within Cases does not migrate as a linked timeline; we extract case records with their core field data and flag the conversation history limitation before migration begins.

ConvergeHub Invoices map to Freshsales Invoice records where the Freshsales Pro or Enterprise plan is the destination. Invoice data, line items, totals, and tax amounts transfer. Payment gateway history and partially paid invoice payment records do not migrate because ConvergeHub stores this data outside the exportable record set. We flag any invoice with partial payment status for customer review before import.

ConvergeHub Products map to Freshsales Products with SKU, unit price, and description preserved. Product associations to Deals are restored through line-item linking during the Deal import phase. We verify that all products referenced by ConvergeHub Quotations and Invoice line items exist in Freshsales before those modules import.

ConvergeHub Activity records split by type: call and task activities map to Freshsales Tasks, and meeting or event activities map to Freshsales Events. The original timestamp is preserved as ActivityDate for timeline ordering. Activity associations to Contacts, Leads, Deals, or Accounts are resolved by matching the ConvergeHub foreign-key IDs to Freshsales record IDs generated during the import phase. Call recording URLs do not transfer as file attachments without explicit customer instruction due to size and format variability.

Every ConvergeHub custom field across Accounts, Cases, Contacts, Deals, Invoices, Leads, and Products is inventoried during discovery. We create the equivalent custom field in Freshsales with the matching field type before any module import begins. Picklist values are explicitly mapped between ConvergeHub and Freshsales, and date formats are reformatted to match the Freshsales instance date format documented in Admin Settings. Required field status is enforced during import rather than at the field-creation level to prevent blocked loads.

ConvergeHub User records (name, email, role, ACL assignment) map to Freshsales User records by email match. ConvergeHub role names are mapped to Freshsales permission roles during configuration. Owner assignment on Deals, Cases, and Contacts is updated to point to the corresponding Freshsales User after User provisioning is complete.

ConvergeHub Automation rules defined in the Tools section have no export path. We do not migrate automations as code. We capture screenshots and structured notes during discovery documenting each automation's trigger, criteria, and action sequence, and deliver this as a written automation inventory to the customer. Freshsales Workflows (Pro and above) serve as the rebuild target, and the customer's admin or a Freshworks partner handles the rebuild post-migration.

ConvergeHub Quotations map to Freshsales Quotes with product line items, pricing, and terms. Product references are mapped to Freshsales Products during the Product import phase. Quote status and custom quotation fields are preserved as Freshsales custom fields where applicable.