Migrate from Honcho CRM to Twenty CRM

Honcho Lead records map to Twenty Person. The Honcho lead source and lead status properties migrate as select fields on the Person object. We parse the CSV export of the Lead Management module, map name, email, phone, company name, and custom fields to their Twenty Person equivalents, and use the email address as the dedupe key during import. Any Honcho Leads that represent organizations rather than individuals are flagged during scoping for reassignment to the Organization object.

Honcho Contact records map directly to Twenty Person. All standard fields (name, email, phone, address fields) migrate as typed fields on Person. Custom contact fields defined in Honcho are detected during scoping and recreated as matching fields on the Twenty Person object via the /metadata API before import begins.

Honcho Company records map to Twenty Organization. The company domain becomes the Organization's website field and is used as the dedupe key. Organization is created before any Person import so that the Person-Organization relation is satisfied at the moment of Person insert. Custom fields on Honcho Companies migrate as typed fields on the Twenty Organization object.

Honcho Deals map to Twenty Opportunity. The dealstage property maps to Twenty's Opportunity stage field. Pipeline stage names extracted from Honcho's visual pipeline configuration are recreated as Opportunity stage values in Twenty, or mapped to existing Twenty pipeline stages if the customer chooses to align with a standard pipeline structure. Deal value, close date, and associated contact and company references migrate with parent-record lookups resolved at load time.

Honcho's named pipeline stages are extracted from the pipeline configuration export. We recreate these as Opportunity stage values in Twenty's Opportunity pipeline. If the customer wants to align to Twenty's default pipeline (Qualification, Proposal, Negotiation, Closed Won, Closed Lost), we map Honcho stages to the closest matching defaults rather than preserving non-standard stage names that would confuse a new user base.

Honcho's Deal Timeline is a proprietary activity tracker with no standard CRM equivalent. We flatten each timeline entry into a dated Task record in Twenty with the original action description, timestamp, and associated Deal (Opportunity) reference. Timeline entries land in Twenty's Task object with the Opportunity as the WhatId. Customers should verify that activity history meets their requirements after migration since timeline entries are not first-class activity objects in Twenty.

Honcho custom fields on Contacts are detected during scoping and recreated as typed fields on Twenty Person via the /metadata API before import. Field types (text, number, date, select) are preserved. If Honcho uses a field type not supported by Twenty Person (e.g., multi-select), we map to the nearest equivalent (text) and flag for the customer to confirm the behavior.

Honcho custom fields on Companies migrate as typed custom fields on Twenty Organization. We pre-create the Organization custom fields via Twenty's /metadata API before the Organization import phase begins. Custom field definitions are documented in the migration scope so the customer can rename or re-type fields before data loads if desired.

Honcho User records (name, email, role) export from the user management export. We map users to Twenty WorkspaceMember by matching email address. Any Honcho Owner assignment on Deals or Contacts resolves to a WorkspaceMember reference in Twenty at migration time. Owners without a matching WorkspaceMember are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Honcho's QuickBooks sync settings and linked invoice references do not export from the Report Builder. We flag any Deals with QuickBooks associations during scoping and document them in a separate reconciliation artifact for the customer's admin to manually re-link after cutover. Invoice data should be reconciled directly in QuickBooks; we do not migrate invoice records as CRM data.