Migrate from Honcho CRM to Pipedrive

Honcho Lead records map directly to Pipedrive Lead. Standard fields (name, email, phone, source, status) migrate 1:1. Any custom lead properties detected during scoping are created as matching Pipedrive custom fields before import and mapped by name and type. Lead assignment to owner resolves via email match against Pipedrive User records provisioned before migration.

Honcho Deals map to Pipedrive Deals with all standard fields (title, value, stage, expected close date, owner) preserved. Pipeline stage names extract from Honcho's pipeline configuration and map to matching Pipedrive stages; if stage names differ, we rename during migration per the customer's naming convention choice during scoping.

Honcho Company records map to Pipedrive Organizations. We export Company IDs alongside Contact associations and resolve the Organization ID at migration time so that Contact-Company relationships reconstruct correctly in Pipedrive. Domain and address fields migrate as standard text fields.

Honcho Contact records map to Pipedrive People. All standard fields (name, email, phone, title, organization) migrate directly. Custom fields on contacts are detected during scoping, created in Pipedrive by type (text, numeric, date, dropdown), and mapped by name. Contact-Company links resolve via email-domain or explicit Company ID during import.

Honcho pipeline stage names and order extract from the pipeline configuration during export scoping. We recreate the stage structure in Pipedrive as a matching pipeline with equivalent stage names and order, or rename per customer direction. Stage probabilities can be carried over or set to Pipedrive defaults during configuration.

Honcho Deal Timelines are a proprietary activity tracker with no direct Pipedrive equivalent. Each timeline entry flattens into a dated activity row with the deal ID, action description, timestamp, and actor (owner). At Pipedrive, these land as Note records or Activity Log entries attached to the corresponding Deal. Users should verify activity history completeness post-migration as timeline structure may differ from native Pipedrive activity views.

Honcho custom field definitions (name and type) export alongside their parent records during scoping. We create matching custom fields in Pipedrive by field type before data import: text fields to text, numeric fields to numeric, date fields to date, dropdown fields to set or enum. Field-level security in Pipedrive is set to editable for all migrating users by default.

Honcho User records (name, email, role) export as part of the scoping export. Owners on Deals and Contacts resolve by email match against Pipedrive User accounts. Any Honcho Owner without a matching Pipedrive User is flagged in the reconciliation report; the customer provisions missing Users before record import resumes.

Honcho QuickBooks sync settings and linked invoice references do not export. We flag any Deals with QuickBooks invoice associations during scoping so the customer can manually re-link relevant records after cutover. Invoice data itself should be reconciled directly in QuickBooks. This is a data loss for the sync settings only; the customer documents the original mapping configuration during scoping.

Honcho Google Calendar sync configuration is stored per-organization and does not export. We do not migrate sync settings. Pipedrive's Google Calendar integration is configured independently post-migration using standard OAuth flow. The customer sets up the connection in Pipedrive Settings > Integrations > Google Calendar after cutover.

Honcho Report Builder configurations and saved reports do not export. We deliver a written inventory of all active Honcho reports during scoping, documenting the report name, object, filters, and columns. The customer rebuilds these as Pipedrive dashboards and custom reports post-migration. This is out-of-scope for data migration but included as a deliverable artifact.