Migrate from Bigin by Zoho CRM to HubSpot

Bigin contacts map directly to HubSpot contacts. The primary company association (stored as Account_Name in Bigin) translates to a Company association in HubSpot via the association API. Multi-company contacts require a primary selection rule — by default the most recently modified company is assigned as the primary, with secondary companies surfaced as additional company associations.

Bigin companies map to HubSpot companies. Parent-child company hierarchies in Bigin (represented via a Parent Company field) translate to HubSpot's subsidiary association model, preserving the corporate structure. All standard company fields including phone, website, industry, employee count, and address components map directly to their HubSpot counterparts. Bigin's industry pick-list values undergo value mapping to align with HubSpot's industry taxonomy before import.

Bigin deals map to HubSpot deals (internally called Opportunities). Each Bigin Team Pipeline translates to a named HubSpot pipeline. The deal name, amount, expected close date, owner, and description fields carry over directly. Stage mapping is value-by-value per pipeline, handled in the Pipeline Stage value mapping row.

Bigin stage names (e.g., 'Qualification', 'Proposal Sent', 'Closed Won', 'Closed Lost') map to HubSpot deal stage names. HubSpot allows different stage sets per pipeline, so if Bigin has multiple pipelines, each pipeline's stage set is created as a separate HubSpot pipeline with its own stage sequence. Stage probabilities are applied per HubSpot's pipeline configuration.

Bigin tags are module-level labels (a contact can have different tags than a deal). HubSpot has no native tag object for CRM records, but tags translate to a multi-value custom property called Tags__c on each object. Up to 20 tags per module migrate from Bigin; if a record has more than 20, the first 20 by modification date are retained per Bigin's import limit.

Bigin tasks map to HubSpot tasks with subject, due date, status, priority, and owner preserved. Task status values (Not Started, In Progress, Completed, Deferred) map to HubSpot task status equivalents. HubSpot tasks do not have a native priority field — priority is stored as a custom pick-list property if needed.

Bigin events (meetings, calls) map to HubSpot engagements of type MEETING or CALL. Original start time, end time, and location fields are preserved. HubSpot stores these as engagements on the associated contact or company record. Recurring events in Bigin are 'squashed' into a single event entry per Bigin's export limitation.

Bigin notes map to HubSpot notes attached to the parent record (Contact, Company, or Deal). Note body text and the associated record link are preserved. Bigin notes that contain attachments re-upload those files as HubSpot file attachments; inline images in rich-text notes are extracted and re-hosted.

Bigin products map to HubSpot products with name, unit price, and description preserved. Bigin's product-to-deal line item relationship translates to HubSpot's deal-to-product association via line items. Products that exist only as deal-level descriptions (without a formal product record) are created as HubSpot products before the deal migration runs.

Bigin user records are resolved by email address against HubSpot portal users. If a Bigin owner email matches a HubSpot user email, the record is assigned to that HubSpot user. If no match is found, records are flagged before migration and assigned to a designated fallback HubSpot user of your choice. We do not create HubSpot users — that requires an admin action in the destination portal.

Bigin custom fields (up to 25 per module on Premier) map to HubSpot custom properties. For each custom field we inspect the field type (text, pick-list, date, number, checkbox) and create a matching HubSpot property of the same type. Bigin's custom field API naming convention (<namespace>__<field_label>) is preserved as the HubSpot property internal name for traceability.

Bigin file attachments on Contacts, Companies, and Deals are downloaded and re-uploaded to HubSpot Files, then attached to the corresponding record. Bigin's 10 export limit per module and per-file size limits are respected during extraction. HubSpot's file size limit is 25MB per file.