Migrate from FIVE CRM to HubSpot

Five CRM contacts map 1:1 to HubSpot contacts. The primary company association resolves via HubSpot's associations API after companies are migrated. Five CRM contacts without a company link land in HubSpot without an associated company — you can merge or relink post-migration.

Five CRM companies map to HubSpot companies. Parent-child company hierarchies in Five CRM map to the parent_company_id field in HubSpot. The parent company must be migrated first; circular references are flagged and resolved by your team before the full run.

Five CRM deals map to HubSpot deals. The deal's associated pipeline in Five CRM determines which HubSpot deal pipeline receives the record. If Five CRM uses one pipeline with multiple stages, those stages map to the corresponding HubSpot pipeline stages.

Five CRM pipelines are represented as stage labels on deal records. HubSpot pipelines are first-class objects. We extract unique pipeline names from Five CRM deal records and create matching HubSpot pipelines with corresponding stage names, probability weights, and display order.

Five CRM deal stages map to HubSpot deal stages per pipeline. Each stage name in Five CRM is mapped to the equivalent HubSpot stage within the target pipeline. Probability and forecast category are applied based on HubSpot's stage defaults unless your team specifies custom weights.

Five CRM custom fields migrate as HubSpot custom properties. We create the property in HubSpot (snake_case naming) before migration, set the field type to match Five CRM's data type (text, number, date, picklist), and preserve any pick-list values as HubSpot pick-list options.

Five CRM activity logs map to HubSpot engagements. Calls and emails become HubSpot tasks of type 'CALL' or 'EMAIL'. Meetings become HubSpot meetings with original start/end times preserved. Notes become HubSpot notes with rich-text content intact where supported. Each engagement is timestamped with the original Five CRM creation date.

Five CRM file attachments are downloaded and re-uploaded to HubSpot Files, then linked to the target record. HubSpot's file size limit is 25MB per file. Inline images in notes are extracted and rehosted as HubSpot-hosted assets. File association is maintained via HubSpot's file associations API to preserve document relationships.

Five CRM owners are matched to HubSpot users by email address. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a fallback owner. Owner names, not IDs, are preserved in a custom field for reference.

Five CRM tags and labels that don't map to HubSpot's standard association model are preserved as a custom multi-select pick-list property (five_crm_tags__c) for reporting and segmentation. You can map these to HubSpot lists or workflows post-migration. The multi-select format allows flexible segmentation without losing tag granularity.

Five CRM custom objects map 1:1 to HubSpot custom objects. Custom-object associations in Five CRM that use an N:N relationship model require a HubSpot custom junction object to preserve the relationship. We surface this requirement in the pre-migration schema plan for your approval before creation.