Migrate from Cirrus CRM to HubSpot

Direct map. HubSpot stores the contact record with all standard properties (name, email, phone, jobtitle). Original create date and last-modified date from Cirrus CRM preserved as custom datetime fields since HubSpot overwrites CreatedAt at import time. Owner resolved by email match to HubSpot users.

Direct map. HubSpot Company object receives the Cirrus organization name, domain, industry, employee count, and annual revenue. Parent-company hierarchy in Cirrus CRM maps to HubSpot's subsidiary company association model. Multi-org contacts in Cirrus CRM link to the primary HubSpot company via the company_id association.

Direct map. Cirrus CRM deal name, amount, stage, and close date migrate to HubSpot Deal properties. HubSpot's deal pipeline stage pick-list is populated from Cirrus CRM stage names. If Cirrus CRM uses multiple pipelines, each pipeline maps to a separate HubSpot deal pipeline with its own stage set.

Each Cirrus CRM deal pipeline maps to its own HubSpot deal pipeline. The pipeline's stage names, associated win probabilities, and display order are transferred directly. HubSpot supports multiple simultaneous pipelines natively — no structural changes required beyond creating the pipeline shell in HubSpot settings. Each stage in HubSpot is populated with matching labels and probability values from Cirrus CRM, preserving your original pipeline logic in the new system.

Cirrus CRM activity logs (call duration, email subject, meeting start/end time) migrate as HubSpot engagements. Call activities attach as HubSpot call engagement records with duration and outcome. Emails migrate as email engagements with subject and timestamp. Meetings become HubSpot meetings linked to the contact record.

Cirrus CRM notes migrate as HubSpot engagement notes on the associated contact or company record. The original note body and its creation timestamp are preserved in the migration. Rich-text formatting within notes is flattened to plain text to prevent any display inconsistencies or rendering issues in HubSpot's note component, ensuring readability across all devices and browsers.

Cirrus CRM quote and order data linked from ERP systems does not have a native HubSpot equivalent. We surface ERP-linked fields from Cirrus CRM as custom properties on HubSpot Deals (e.g., ERP_Order_ID__c, ERP_Quote_Status__c). Your team decides whether to rebuild order management in HubSpot or keep ERP as the system of record.

Cirrus CRM custom fields on contacts, organizations, or deals migrate to HubSpot custom properties. Field type is preserved where possible (text → string, number → number, date → datetime, picklist → select). Multi-select fields in Cirrus CRM map to HubSpot multi-select properties. Field label and description copied for admin reference.

Cirrus CRM owner IDs are resolved against HubSpot users by email address match. Unmatched owners are flagged in the migration report — you either invite them to HubSpot first or reassign their records to a designated fallback user before the migration runs.

Files attached to Cirrus CRM contacts, organizations, or deals are downloaded and re-uploaded to HubSpot's file manager, then linked to the destination record. Original file metadata including create date and file type are preserved during the transfer. File size limits follow HubSpot's file storage constraints — files exceeding limits are flagged for manual handling. Each file re-upload is logged in the migration audit trail for traceability and reconciliation purposes.

Cirrus CRM campaign tracking data has no direct equivalent in HubSpot's standard CRM objects. HubSpot's Campaign object is specifically a Marketing Hub artifact for organizing marketing assets and tracking campaign performance. We preserve all campaign attribution data as custom contact properties (e.g., Original_Campaign_Source__c, Original_Campaign_Name__c) rather than creating empty or unlinked Campaign records. Your HubSpot admin can populate the HubSpot Campaign object manually if Marketing Hub is active.