Migrate from CompanyHub CRM to HubSpot

CompanyHub contact fields map directly to HubSpot contact properties. All standard fields (name, email, phone, job title, address) translate 1:1. The HubSpot contact record is created first, then associations to companies and deals are established after the related records exist in HubSpot.

CompanyHub company records map to HubSpot company records. Company domain, industry, employee count, and annual revenue translate as HubSpot standard properties. CompanyHub parent-child hierarchies map using HubSpot's parent company association. Multi-company associations on a single contact collapse to one primary association in HubSpot with additional companies surfaced via company-to-contact associations.

CompanyHub deals map to HubSpot deals (deals in HubSpot are also called opportunities internally). Deal name, amount, stage, close date, owner, and notes migrate directly. CompanyHub deal-stage names map value-by-value to HubSpot deal pipeline stages during import. Multiple CompanyHub deal pipelines map to multiple HubSpot deal pipelines.

CompanyHub tasks migrate as HubSpot engagement tasks (internal tasks, not tickets). Task subject, body, due date, owner, and completion status are preserved. Tasks associated with a specific contact or deal carry the association forward in HubSpot so activity history remains linked to the correct record.

CompanyHub notes migrate as HubSpot engagement notes attached to the relevant contact, company, or deal record. Note body text, create date, and owner are preserved. Notes associated with multiple records carry the primary association; secondary associations are documented in the migration plan for manual recreation if needed.

CompanyHub user records resolve to HubSpot owners by email address match. All records (contacts, companies, deals, tasks) carry their assigned owner in HubSpot. Unmatched owners (CompanyHub users without a HubSpot account) are flagged in the migration plan for team assignment before the full run. No record lands in HubSpot without an assigned owner.

CompanyHub custom tables are mapped per-table based on complexity. Simple custom tables with primitive fields (text, number, date) are recreated as HubSpot custom properties on the related standard object. Complex custom tables with multiple columns and many-to-many associations are flagged for HubSpot custom object creation (requires Enterprise). A mapping plan is delivered before migration so custom object schemas are pre-created in HubSpot.

CompanyHub freeform custom fields on any standard object migrate as HubSpot custom properties with the same label and field type. Text fields map to single-line or multi-line text properties. Number fields map to HubSpot number properties. Date fields map to HubSpot date properties. Pick-list fields in CompanyHub map to HubSpot dropdown or radio-button properties with the same options.

CompanyHub's one-click hotness meter (very hot / hot / warm / cold) does not translate to HubSpot's lifecycle stage model. The numeric or label-based hotness value migrates as a HubSpot custom property (e.g., Hotness_Score__c or Hotness_Label__c). Post-migration, teams can use HubSpot's property-based scoring actions to build automated scoring workflows aligned to their sales process.

CompanyHub email tracking data (opens, clicks, sent timestamps) migrates as engagement records attached to the contact. Bulk mail campaign headers and send dates are preserved in a custom property or as engagement notes. The email body content is not included in the migration unless the email was stored as a note. Individual email send/receive logs migrate as engagement timeline entries.

CompanyHub file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files, then associated to the relevant record. File size limits apply (HubSpot default: 25MB per file). Inline images in notes are downloaded and rehosted in HubSpot's file storage.

CompanyHub UTrons cannot be exported or migrated. Each Utron is documented in full with its trigger conditions, action steps, and branching logic so a HubSpot administrator can rebuild it in the workflow builder. The migration plan includes a Utron audit export that lists every active workflow, its trigger event, and the sequence of actions it performs. Workflow rebuild is outside the migration scope.