Migrate from Honcho CRM to Freshsales

Honcho CRM Lead records map directly to Freshsales Lead. All standard lead fields (name, email, phone, source, status) transfer with custom fields preserved as matching Freshsales custom fields. Freshsales applies its own lead conversion logic (Lead → Contact, Account, Deal) after migration; we flag the conversion mapping configuration for the customer's admin to review during Freshsales setup.

Honcho Company records map to Freshsales Account. The Company ID is preserved in a custom field honcho_company_id__c for audit and relationship reconciliation. Accounts are imported before Contacts so that the Company lookup is satisfied at Contact insert time. If multiple Honcho Companies share the same domain, we deduplicate by name and create a single Account with the first address on record.

Honcho Contact records map to Freshsales Contact with the Account lookup resolved via Company ID matching. Email serves as the primary dedupe key. Custom fields on Honcho Contacts migrate as typed Freshsales custom fields. If a Contact has no associated Company in Honcho, it lands as an Account-less Contact in Freshsales pending manual review.

Honcho Deals map to Freshsales Deals. Deal value, stage, owner, and close date transfer directly. The honcho_company_id and honcho_contact_id custom fields on the Freshsales Deal preserve source references for reconciliation. Closed-Lost and Closed-Won status migrate with the original stage names preserved in a custom field for post-migration pipeline reporting.

Honcho pipeline stage names and ordering extract from the pipeline configuration and map to Freshsales Deal Stages. If Honcho uses custom stage names not present in Freshsales by default, we create matching stages in Freshsales during schema setup. Stage probability defaults are applied per Freshsales conventions unless the customer specifies custom probabilities during scoping.

Honcho Deal Timeline entries are flattened into dated activity rows during export parsing. Each row carries the Deal ID, action description, and timestamp. At Freshsales, these land as Notes attached to the corresponding Deal, or as Tasks with the original timestamp and an 'Imported from Honcho Timeline' label. We preserve the chronological ordering of timeline entries so the deal's history reads correctly in Freshsales. Customers should verify that activity volume meets their needs post-migration.

Honcho custom fields on Contacts and Companies are detected during scoping, their field types are recorded, and matching Freshsales custom fields are created before migration. We map text fields to text, number fields to number, date fields to date, and dropdown fields to Freshsales picklist. Custom field API names are prefixed to avoid collision with Freshsales standard fields.

Honcho User records (name, email, role) are extracted and matched to Freshsales Users by email during migration. Owners on Deals and Contacts resolve to Freshsales OwnerId via this User lookup. If a Honcho Owner email has no matching Freshsales User, the record is held in a reconciliation queue and the customer provisions the User before import resumes. Honcho seat cap constraints are flagged during scoping to confirm the Freshsales plan accommodates the user count.