Migrate from Honcho CRM to Salesforce Sales Cloud

Honcho Contact records map to Salesforce Lead or Contact based on qualification status. We use Honcho's lead_status and source fields during scoping to determine the split. Records with clear buying intent signals (deal association, recent activity) land as Salesforce Contact attached to an Account. Unqualified or early-stage records land as Salesforce Lead. The original Honcho contact record is preserved in a custom field honcho_contact_id__c on both Lead and Contact for audit and reconciliation.

Honcho Lead records map directly to Salesforce Lead. All standard fields (name, email, phone, company, lead source, status) migrate 1:1. Any custom fields defined in Honcho become matching custom fields on the Salesforce Lead object with the same API naming convention (honcho_ prefix to avoid collision). Lead score or rating values from Honcho migrate to a custom field honcho_score__c.

Honcho Company records map to Salesforce Account. The company name becomes Account Name; domain data becomes Website. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Honcho company IDs are preserved in a custom field honcho_company_id__c for reconciliation.

Honcho Deals map to Salesforce Opportunity. The Honcho dealstage value maps to a Salesforce StageName value we configure during scoping. Closed-Lost and Closed-Won status migrate as explicit StageName values. Deal value maps to Amount. The Honcho deal_id is preserved in honcho_deal_id__c on the Opportunity. Deals without an associated Company in Honcho are flagged during scoping for Account creation or linking before Opportunity import.

Honcho pipeline stage names are extracted from the pipeline configuration and mapped to Salesforce stage values you choose during scoping. We recommend a direct 1:1 mapping where possible to preserve pipeline analytics continuity. If Honcho has more stages than your target Salesforce sales process allows, we consolidate and document the mapping. Stage probability percentages are set on each StageName via the Salesforce metadata API or Setup UI after migration.

If Honcho has multiple named pipelines (available on Professional and Enterprise Honcho tiers), each maps to a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. This keeps stage values scoped per business line. Record Types also drive Page Layout assignments so different sales teams see different field arrangements without affecting the data model.

The Honcho Deal Timeline is a proprietary activity tracker with no direct Salesforce equivalent. We export each timeline entry as a dated Task record with Subject describing the action, Description carrying the notes, and ActivityDate set to the original Honcho timestamp. WhatId on the Task points to the migrated Opportunity ID. This preserves chronological order but loses the Honcho-specific timeline formatting. Users should verify activity history meets their requirements after migration.

Honcho User records (name, email, role) map to Salesforce User records by email address match. We extract every distinct owner referenced on Contact, Company, Deal, and Timeline records and attempt to match against the destination Salesforce org's User table. Users without a matching Salesforce User go to a reconciliation queue for your admin to provision before record import resumes. OwnerId references on Opportunities and Contacts cannot be satisfied without an active User record.

Honcho custom fields on Contacts are detected during scoping and recreated as matching custom fields on both Salesforce Lead and Contact objects. Field types are preserved (text, number, date, picklist, checkbox) and mapped to Salesforce field types. Multi-select picklists in Honcho map to Salesforce multi-select picklists. We do not migrate calculated or formula fields as formulas; these are re-implemented post-migration by your admin if needed.

Honcho custom fields on Companies are recreated as matching custom fields on the Salesforce Account object before Account import begins. All custom field API names are prefixed with honcho_ to avoid collision with any existing Salesforce custom fields in your org. Custom field validation rules (required, format) are documented separately for your admin to configure or adjust post-migration.

Honcho QuickBooks sync settings and linked invoice references are stored locally and not exported in the CSV. We flag any Deal records with QuickBooks invoice associations during scoping so you can manually re-link relevant records after cutover. Invoice data itself should be reconciled directly in QuickBooks. The link between a Salesforce Opportunity and a QuickBooks invoice requires manual re-establishment via the QuickBooks connector in your target system.

Honcho Deal Timeline entries with file attachments are exported separately from the activity rows. Files are mapped to Salesforce ContentDocument records and linked via ContentDocumentLink to the parent Opportunity record. The original Honcho file name and any inline notes are preserved in ContentVersion metadata. File attachments that cannot be parsed from the Honcho export are documented in a missing-attachments inventory for your admin to manually re-upload if needed.