Migrate from Honcho CRM to HubSpot

Lifecycle stage defaults to 'lead' on all migrated contacts

Honcho CRM has no contact lifecycle model — every contact is treated as a static record regardless of where they are in the buyer's journey. HubSpot's entire automation and contact-based billing model relies on lifecycle_stage values like subscriber, lead, MQL, SQL, opportunity, and customer. When contacts migrate from Honcho, they all land with a default HubSpot lifecycle_stage of 'lead' unless your team specifies a different default. This means HubSpot workflows triggered by lifecycle stage changes will not fire for migrated contacts until the team manually updates their lifecycle stage or runs a bulk re-enrollment. We preserve the original Honcho contact create date and last-modified date in custom fields so your team can prioritize recategorization by recency.

HubSpot marketing contact billing does not activate automatically

HubSpot bills based on the count of marketing contacts in your portal — contacts who have received or are eligible to receive marketing emails. Migrations from Honcho often bring over a large contact list that was managed without distinguishing between marketing-eligible and sales-only contacts. If your HubSpot subscription tier limits marketing contacts, importing all Honcho contacts as marketing contacts could push you over the billing limit or trigger upsell prompts. We flag all migrated contacts as non-marketing by default and let your HubSpot team mark individual contacts as marketing contacts after reviewing the list for duplicates and relevance. This prevents billing surprises on day one of the new CRM.

Google Calendar sync associations do not transfer to HubSpot

Honcho CRM's native Google Calendar sync links meetings and deal activities to the user's Google Calendar bidirectionally. When meetings migrate from Honcho to HubSpot, the calendar event itself and its HubSpot meeting record are created, but the Google Calendar event association is not replicated because HubSpot's Google Calendar integration must be re-authenticated and re-configured by each user in their HubSpot account settings. We migrate the meeting data (title, attendees, start/end time, notes) completely, but each user must reconnect their Google account to HubSpot to get calendar reminders and bidirectional sync working again.

QuickBooks integration links have no HubSpot equivalent

Honcho CRM's QuickBooks integration allows users to associate deals or contacts with QuickBooks records for accounting and invoicing visibility. HubSpot does not have a native QuickBooks integration at the CRM level — it exists in HubSpot's Operations Hub but functions differently, primarily syncing financial data rather than associating records. Any QuickBooks record IDs stored in Honcho as custom fields will migrate to HubSpot as text values in a custom property. Your team will need to re-establish QuickBooks associations manually or via a third-party integration like HubSpot's native QuickBooks connector if available in your Operations Hub tier.

Honcho deal pipelines map 1:1 but HubSpot pipeline defaults apply

Each Honcho visual sales pipeline transfers as a separate HubSpot deal pipeline with stage names and order preserved. However, HubSpot applies default probability percentages and forecast categories to each stage name based on HubSpot's conventions, not Honcho's. If your Honcho pipeline had custom probability weights assigned to stages, those values do not transfer — the HubSpot defaults apply and your admin must update the pipeline configuration to reflect your actual close rates per stage. We document the Honcho stage order and names in the migration plan so the admin can remap probabilities accurately.