Migrate from Convert Wire to HubSpot

ConvertWire contacts map 1:1 to HubSpot contacts. HubSpot requires an associated company record for most contact properties — contacts without a primary company in ConvertWire land in HubSpot with the company association set to the default or flagged for manual resolution.

ConvertWire companies map to HubSpot companies. HubSpot supports N:N contact-to-company associations natively, so any ConvertWire contact with multiple associated companies creates multiple HubSpot company associations per contact. This approach also ensures that the primary company is flagged appropriately, and secondary associations retain their original labels for reporting purposes.

ConvertWire deals map to HubSpot deals. The pipeline and stage fields from ConvertWire translate to HubSpot deal-stage pick-list values. If ConvertWire uses multiple pipelines, each pipeline becomes a distinct deal-stage pick-list scoped to a deal-pipeline property in HubSpot. We also preserve any stage probability percentages and forecast categories by mapping them to HubSpot's deal-stage properties, ensuring forecasting reports reflect the original deal progress.

ConvertWire stores pipeline name and stage name as deal fields. In HubSpot, a deal pipeline is a pick-list property on the deal object, and each stage within that pipeline is a stage-name pick-list value. We create a deal-pipeline property in HubSpot and map each ConvertWire pipeline accordingly.

HubSpot has no native lifecycle_stage equivalent in the contact object without a HubSpot Sales Hub or Service Hub subscription. We create a lifecycle_stage custom property on the contact object and populate it from ConvertWire's lead-status or lifecycle-stage field. Stage-transition timestamps become custom datetime fields for audit continuity.

ConvertWire activity logs (calls, emails, meetings) map to HubSpot's engagement timeline. Each activity type is stored as an engagement record with the original timestamp, owner, and linked contact or company preserved. The engagement type (call, email, meeting) maps to HubSpot's engagement sub-type.

ConvertWire notes map to HubSpot CRM notes attached to the corresponding contact or company record. Rich-text formatting in ConvertWire notes is preserved as HTML-formatted note content in HubSpot. Additionally, any ConvertWire note timestamps are kept to preserve the original creation date for audit trails.

ConvertWire file attachments are re-uploaded to HubSpot Files and attached to the corresponding CRM record. File size limits per attachment apply (HubSpot default 25MB per file; larger files require chunked upload or alternative storage link). We also verify that file metadata such as original upload date and owner are preserved in HubSpot Files, maintaining the original context for each attachment.

ConvertWire custom objects map 1:1 to HubSpot custom objects. Custom-object associations that use a many-to-many model in ConvertWire need HubSpot custom junction objects to preserve the relationship semantics in the destination. We also ensure that any junction object relationships are represented as HubSpot custom association definitions, preserving the many-to-many semantics in the new environment.

ConvertWire owner IDs are resolved against HubSpot users by email address match. Unmatched owners are flagged before migration — teams either invite those users to HubSpot or reassign their records to a fallback owner. No record lands in HubSpot without a valid owner.

Every ConvertWire custom field becomes a HubSpot custom property. We create the custom property in HubSpot using the source field's data type (text, number, date, pick-list) before loading data. Pick-list custom fields in ConvertWire require explicit value-by-value mapping to HubSpot pick-list options.